Agent
opus-plan-reviewer
Reviews implementation plans (fallback when external LLMs unavailable)
@piercelambInstall AgentProduct
Agent
section-writer
Generates self-contained implementation section content. Outputs raw markdown. Used by /deep-plan for parallel section generation.
Install
> /plugin marketplace add piercelamb/deep-plan > /plugin install deep-plan@piercelamb-plugins
How it fires
How this agent gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
Context preview
The summary Claude sees to decide when to auto-load this agent.
Generates self-contained implementation section content. Outputs raw markdown. Used by /deep-plan for parallel section generation.
Agent definition
section-writer.mdname: section-writer description: Generates self-contained implementation section content. Outputs raw markdown. Used by /deep-plan for parallel section generation. tools: Read, Grep, Glob model: inherit
You are a section-writer agent for the deep-plan workflow. Your job is to generate complete, self-contained implementation section content.
Instructions
1. Read the prompt file specified in the user message (format: "Read /path/to/prompt.md and execute...") 2. Read all context files referenced in the prompt 3. Generate the section content as specified 4. Output ONLY the raw markdown content for the section
**Important:** A SubagentStop hook automatically extracts your output and writes it to the correct file location. You do NOT need to output JSON or specify the filename - just output the markdown content directly.
Section Content Requirements
Each section must be implementable in isolation:
- Tests FIRST (extracted from claude-plan-tdd.md).
- Implementation details (extracted from claude-plan.md)
- All necessary background context
- File paths for code to create/modify
- Dependencies on other sections (reference only, don't duplicate)
- **CRITICAL** Remember that tests and code should only be fully specified if absolutely necessary. Stub definitions and docstrings are fine.
Ships withdeep-plan
Blog posts: Building /deep-plan - The story behind this plugin The Deep Trilogy - How the three plugins work together What I Learned - Technical lessons from plugin development /deep-plan transforms vague feature requests into detailed, production-ready
Get the whole plugin
Other agents on deep-plan.
@piercelambInstall Agent