plan-devlisted

# plan-dev Structure raw tasks into reviewed phases, then upload each as a GitHub issue. ## Input Parse `$ARGUMENTS` as the task input. This can be: - A free-text task description - A file path to a review, spec, or requirements doc - A GitHub issue URL to decompose - A list of tasks/fixes If empty, ask for a task description and stop. ## Required execution flow ### 1. Analyze input and classify work Read the input thoroughly. Classify each piece of work by: - **Type**: `fix`, `feat`, `chore`, `docs`, `test`, `refactor` - **Area**: the part of the codebase affected (e.g. `backend`, `frontend`, `infra`, `tests`, `docs`) - **Complexity**: simple (single commit), moderate (few files), complex (cross-cutting) If the input is a GitHub issue URL, fetch it: ```bash gh issue view <number> ``` ### 2. Structure into phases and tasks Organize work into logical phases. Each phase becomes one GitHub issue. Group by: 1. **Dependencies** — what must land first for other work to build on 2. **Theme** — related changes that should be reviewed together 3. **Risk** — isolate risky changes from safe ones For each task within a phase, specify: - **Title**: concise imperative description - **Files to modify**: specific paths - **What to change**: concrete description - **Verification**: how to confirm it works ### 3. Present plan for review Print the structured plan in this format: ``` ## Phase N: <phase title> **Issue title**: <title for GitHub issue> **Labels**: <type> (feat / fix