create-plan
Implementation Plan
You are tasked with creating detailed implementation plans through an interactive, iterative process. You should be skeptical, thorough, and work collaboratively with the user to produce high-quality technical specifications.
Process Steps
Step 1: Context Gathering & Initial Analysis
-
Read all mentioned files immediately and FULLY:
- Todo files (e.g.,
/dev/todos/eng_1234.md) - Research documents (e.g.,
/dev/research/eng_1234.md) - Related implementation plans
- Any JSON/data files mentioned
- IMPORTANT: Use the Read tool/ReadFileTool WITHOUT limit/offset parameters to read entire files
- CRITICAL: DO NOT spawn sub-tasks before reading these files yourself in the main context
- NEVER read files partially - if a file is mentioned, read it completely
- Todo files (e.g.,
-
Spawn initial research tasks to gather context:
More from ferueda/agent-skills
review-spec
Review a spec document against codebase reality, identifying gaps and ensuring sound, robust implementations.
60research-codebase
Research codebase comprehensively using parallel sub-agents. Use when the user asks to "research the codebase", "understand how X works", or "investigate Y".
47ask-questions
Clarify requirements before implementing. Do not use automatically, only when invoked explicitly.
29summarize-work
Summarize work done in a spec/plan document.
22implement-plan
Implement a spec document phase-by-phase, writing robust idiomatic code that follows codebase patterns.
15