What problem does it solve? Turning a user request directly into code often skips planning, review, and traceability, producing unreviewable or misaligned changes. This Skill enforces a disciplined step-file workflow that converts any intent—feature, bug fix, refactor, or story—into a hardened, reviewable artifact with a persistent spec file. ## Core Features & Use Cases - Step-file workflow: Sequential clarify → plan → implement → review → present steps with mandatory human checkpoints and no step skipping. - Spec-driven development: Generates a token-bounded spec (900–1600 tokens) with frozen intent, code map, tasks, and Given/When/Then acceptance criteria. - Adversarial review loop: Runs blind, edge-case, and acceptance-auditor subagent reviews, classifying findings into intent_gap, bad_spec, patch, defer, or reject with loopback handling. - Sprint status sync: Updates sprint-status.yaml for epic stories and compiles focused epic context files from planning artifacts. - Use Case: A developer asks to add a FlowField pathfinding tweak to the MingGoRTS gameplay layer; the Skill drafts a spec, gets approval, implements via subagent, runs three review passes, and commits with a suggested review order. ## Quick Start Ask the agent to implement a specific feature or bug fix, for example: implement a small change to the battle planner and walk me through the review.
