By bhpascal
Fieldwork: multi-session project tracking for knowledge work — consulting, research, writing, and beyond.
View or regenerate the session briefing. Use when user says "show briefing", "what's the briefing", or "regenerate briefing".
Initialize a new Fieldwork project with templates, deliverable tracking, and session continuity. Use when starting a new project, setting up a workspace, or when the user says "fieldwork init", "set up this project", or "new project".
Read this file when generating the HTML for `/fieldwork:todo`. Do not improvise the visual design — this system was carefully audited to avoid generic AI aesthetics.
View or update the deliverable/milestone status table. Use when user says "fieldwork status", "check status", "what's the status", or wants a quick project overview.
Generate a printable, interactive HTML checklist from the project's deliverables and tasks. Use when user says "create todo list", "make a checklist", "print tasks", or "fieldwork todo".
Modifies files
Hook triggers on file write and edit operations
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Claude Code for more than code.
You're using Claude Code for consulting, research, writing, or analysis — and every session starts from scratch. You re-explain the project, re-read the status, re-orient Claude to where you left off. Fieldwork fixes that.
It gives your knowledge work the same continuity that developers get from codebases: session briefings that load instantly, deliverable tracking that persists across sessions, and structured wrap-ups that prepare the next session before you close the current one.
git clone https://github.com/bhpascal/fieldwork.git ~/.claude/plugins/fieldwork
/fieldwork:init # Set up a new project
# ... do your work ...
/fieldwork:wrap-up # End of session — commit, update status, generate briefing
# ... next session starts with instant context ...
That's the core loop. init scaffolds a project with deliverable tracking. wrap-up commits your work, updates the status table, and pre-computes a briefing. Next time you open Claude Code, the briefing loads instantly — no AI needed, no re-explaining.
| Command | What It Does |
|---|---|
/fieldwork:init | Initialize a new project from a template or conversational setup |
/fieldwork:wrap-up | End-of-session ritual: sync status, commit, generate briefing |
/fieldwork:status | View deliverable/milestone status table |
/fieldwork:briefing | View or regenerate the session briefing |
/fieldwork:todo | Generate a printable, interactive HTML checklist |
Start with a template or go custom:
| Template | Best For |
|---|---|
| Consulting | Client engagements with contracts, SOWs, defined deliverables |
| Research | Academic, policy, or market research with sources and methodology |
| Writing | Long-form writing with drafts, editorial process, audience awareness |
| General | Anything else — events, curricula, grants, planning |
| Custom | Conversational setup — 3-6 adaptive questions, then scaffold from answers |
Three layers of persistence, zero cloud dependency:
| Layer | What It Captures |
|---|---|
| Status table (CLAUDE.md) | Current state of each deliverable — the cross-session source of truth |
| Commit log (local git) | What was done, when, in what order — invisible infrastructure |
| Project memory (.claude/memory/) | Decisions, lessons, non-obvious context |
The pre-computed briefing is the trick: it's generated at session end (when Claude has full context), then loaded at session start (as a plain file read — zero AI cost, instant load).
Fieldwork also embeds AI fluency patterns from Anthropic's research: iteration prompts in briefings, honest status assessment in the deliverable table, and rules that discourage over-polishing early work.
Works alongside other Claude Code plugins (personality-roulette, superpowers, etc.). See CLAUDE.md for architecture details.
MIT
npx claudepluginhub bhpascal/whatdoyoudo-plugins --plugin fieldworkRandomly assigns Claude a distinct personality on session start. Eight characters: Sea Captain, Starship Computer, Hyperintelligence, Archduke of Hell, Noir Detective, Nature Narrator, Mission Control, and JARVIS.
Multi-project context management: switch projects, save/load sessions. Designed for non-CLI interfaces (Cowork desktop, Telegram).
Folder structure + collaboration protocol so AI sessions can resume project context after compaction or window switch. One brain/ folder, 5 core files (PROJECT/MAP/STATUS/DECISIONS/HANDOFF), and a topic taxonomy.
Save a structured session summary so you can pick up where you left off next time. Captures objectives, files changed, decisions, and generates a continuation prompt.
Multi-model consensus engine integrating OpenAI Codex CLI, Gemini CLI, and Claude CLI for collaborative code review and problem-solving.
Easily create hooks to prevent unwanted behaviors by analyzing conversation patterns