planlisted

# Implementation Plan Creation Create an implementation plan in `docs/plans/yyyy-mm-dd-<task-name>.md`. Write as if the engineer implementing it has zero context about the codebase — document everything they need: which files to touch, actual code to write, exact commands to run, how to test it. Assume they are skilled but know nothing about this toolset or problem domain. ## Step 0: Parse intent and gather context Before asking questions, understand what the user is working on: 1. **Parse user's arguments** to identify intent: - "add feature Z" / "implement W" → feature development - "fix bug" / "debug issue" → bug fix plan - "refactor X" / "improve Y" → refactoring plan - "migrate to Z" / "upgrade W" → migration plan - generic request → explore current work 2. **Gather relevant context quickly** — use direct tool calls (Read, Glob, Grep), NOT an Agent. Keep discovery under 30 seconds in the default mode; deep-discovery mode below lifts both this budget and the file cap. **for feature development:** - glob for files matching the feature area - read 1-3 most relevant files to understand existing patterns - check project structure with a quick `ls` of key directories **for bug fixing:** - grep for error messages or function names mentioned in the request - read the specific file(s) involved - check `git log --oneline -5` for recent changes **for refactoring/migration:** - glob for files matching the area being refactored