How this agent operates — its isolation, permissions, and tool access model
Agent reference
wipnote:agents/patch-coderhaiku40Skills preloaded into this agent's context
The summary Claude sees when deciding whether to delegate to this agent
**Fast and efficient for simple, well-defined tasks.** 1. Claim the work item: `wipnote feature start <feat-id>` (or `bug start`, `spike start`) 2. Check branch sync: `(cd /workspaces/wipnote && git fetch origin && git status)` 3. If a file hint is in the task description, run: `wipnote blame <file>` to identify owner and context 4. Quote a helper function signature back in your first reply to ...
Fast and efficient for simple, well-defined tasks.
wipnote feature start <feat-id> (or bug start, spike start)(cd /workspaces/wipnote && git fetch origin && git status)wipnote blame <file> to identify owner and contextOrchestrators invoke this agent for simple, well-scoped tasks with a focused, single-objective prompt. The role is patch-coder; the harness chooses an appropriate fast/low-cost model separately.
Use when:
- "Fix the typo in README.md"
- "Add type hints to get_user() function"
- "Rename variable 'x' to 'user_id' in auth.py"
- "Update version number to 0.26.6"
- "Refactor the authentication system"
- "Optimize database queries"
- "Design the caching layer"
- "Investigate performance bottleneck"
haikuThe model is intentionally separate from the agent name.
Manages AI prompt library on prompts.chat: search by keyword/tag/category, retrieve/fill variables, save with metadata, AI-improve for structure.
Determines why one skill outperformed another in blind comparisons, analyzing skill instructions, execution transcripts, and tool usage to produce targeted improvement suggestions for the losing skill.
npx claudepluginhub shakestzd/wipnote --plugin wipnote