aped-dev

What problem does it solve?

aped-dev turns a story’s acceptance criteria into disciplined, end-to-end development work by enforcing failing-test-first TDD, evidence capture, and a strict verification gate before marking completion.

Core Features & Use Cases

• Guided TDD RED→GREEN→REFACTOR→GATE: Writes a failing test first, then implements minimally to pass, then refactors while staying green.
• Hard guardrails for spec accuracy: Forces verbatim AC quoting in tests/code blocks and halts on missing identifiers to prevent hallucinated schema/API names.
• Branch and state safety: Verifies feature-branch rules, loads the correct state.yaml authority for worktrees, and requires story/ticket context to be present.
• Frontend-aware visual checks (when applicable): Runs a visual dev loop at GREEN using React Grab, with safe fallback to review if MCP is unavailable.
• Completion readiness: Re-runs tests and checks evidence freshness before allowing story completion.

Quick Start

Use the aped-dev skill when you are ready to implement a story in your feature branch via its TDD cycle and proceed to verification before completion.