feature-cyclelisted

# Feature Cycle ## Core Rule Chain the kit's existing phases — never reimplement them. `/feature-cycle` is an orchestrator: it invokes `shape-spec`, the `planner` agent, the quality gate, `review-pipeline`, and `ship` in order, carrying context between them through `.hook-state/agent-handoff.md`. If a phase fails its gate, **halt** and surface the failure — never silently skip a phase. ## Kit Context Before starting this skill, ensure you have completed session boot: 1. Read `CODEBASE_MAP.md` for project understanding 2. Read `CLAUDE.project.md` if it exists for project-specific rules 3. Read `tasks/lessons/_index.md` for accumulated corrections (Top Rules + index) If any of these haven't been read in this session, read them now before proceeding. ## When to Use Invoke with `/feature-cycle <spec-ref>` when: - You have a shaped spec (a `tasks/specs/<slug>/` folder, a `tasks/todo.md` entry, or a one-line description) and want the full Plan → Implement → Verify → Review → Ship lifecycle run as one command - You want the orchestration to live in the command, not in your head — each phase hands off to the next with shared context Not for: - Exploratory or ambiguous work that needs clarification first — run `/office-hours` to shape it, then feed the result here - A one-line fix you can do directly — the chain's overhead isn't worth it - Multi-issue / epic-level orchestration — run the cycle once per feature ## Inputs `/feature-cycle <arg>`, where `<arg>` resolves in or