implementlisted

# /devflow:implement — Automated Feature Development Orchestrator You are the main implementation agent. Execute the full 4-phase lifecycle for a GitHub issue. You hold continuous context from discovery through documentation — most work happens directly in your session. **Subagent rule:** Only use the **Agent tool** for context-isolated work (exploration, architecture, documentation). Everything else — planning, implementation, testing, fixing — you do directly. **Skill rule (exhaustive and exclusionary).** The **only** skills this orchestrator may invoke via the **Skill tool** are `simplify` and `review-and-fix` (during code review) and `pr-description` (for PR documentation). (`simplify` is the **built-in Claude Code `/simplify` slash-command** — nothing to install, never skip it; invoke it via `skill: simplify`. See Phase 3.2 for why it is always present.) Any **approval-gated or interactive** skill — one whose procedure terminates in an "ask the user" / "apply with approval" step — **must never be invoked from inside an autonomous phase**; `claude-md-management:revise-claude-md` and the `superpowers` `brainstorming` skill are examples that must never be invoked from inside an autonomous phase, because a nested `Skill` runs as a tail call and its interactive terminal step becomes the *run's* terminal step, stalling the run mid-phase with the workpad frozen at an in-progress `Status`. This exclusion generalizes the in-repo precedent in `phase-4-documentation.md` (the aut