implement-epic
implement-epic
Implement: $ARGUMENTS
Finish the epic so that every acceptance criterion is proven from a real execution path, then hand off at IN_REVIEW. review-epic alone certifies DONE. Explicit user instructions override anything below.
Scope
Resolve the PRD path and epic ID. Without an epic ID, take the first epic with TODO, IN_PROGRESS, or BLOCKED stories. Work the incomplete stories in dependency order; skip DONE, IN_REVIEW, and CANCELLED stories unless reimplementation was requested. Read what you need to locate integration points, nothing more.
Carry every incomplete story in one run. Between stories, keep going and put progress notes in the same message as the next action; the only early stops are the BLOCKED conditions under Boundaries. The status file is the run's checklist: set each story IN_PROGRESS when you start it, so progress survives context compaction and anyone reading the file sees where the run stands.
Before editing, name the execution roots the epic must plug into: route table, command registry, rendered component tree, dependency container, migration list, scheduler, event subscriptions, config readers, public package exports. Missing wiring never appears in a diff, so it must be planned up front.
External evidence (docs, web) is worth fetching only when a current or version-sensitive fact can change the implementation or a test. State the question, use one route, record the fact and its source. Evidence may amend the technical plan; it never rewrites outcome, non-goals, or acceptance criteria without the user. If it contradicts the product contract, report the contradiction.