featurelisted

# /feature — AI-Assisted Development Lifecycle Activate this skill for non-trivial features or changes to run the full structured development workflow: plan → critique → implement → test → code-review → QA → PR. --- ## Workflow ### Step 1 — Draft, critique, and approve the plan **Preconditions — check the branch first.** The workflow assumes the human started this session on a fresh feature branch: the code review (Step 4) diffs against the default branch (named in `AGENTS.md` → *Commands*) and Step 9 opens a PR targeting it, neither of which works from the default branch itself. If the session is on the default branch, STOP and ask the user to create a feature branch — you may not create or switch branches yourself (Rule 3 in `AGENTS.md`). **Enter plan mode now**, before drafting. Plan mode is a structural commitment: while in plan mode the harness blocks edit tools, so the workflow cannot skip the approval gate even if the agent is tempted to inline the plan and proceed. Stay in plan mode through steps 1a, 1b, and 1c. Exit plan mode only in step 1c, after the user approves. #### Step 1a — Draft the plan Invoke the `planner` sub-agent to draft an implementation plan. Pass the user's prompt verbatim — including any reference to docs or links. The planner will fetch all external specs with its own tools (it has `WebFetch` for URLs) and return the plan as markdown text. Do not use tools directly — always delegate to the planner sub-agent, regardless of which platform y