aped-dev

Implement story tasks via failing-test-first TDD with RED→GREEN→REFACTOR→GATE.

2|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/yabafre/aped-claude --skill aped-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aped-dev
Source: https://github.com/yabafre/aped-claude/tree/main/src/templates/skills/aped-dev
Command: npx skills add https://github.com/yabafre/aped-claude --skill aped-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about aped-dev

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement story tasks using strict TDD with Claude Code?

Story tasks are implemented using disciplined failing-test-first TDD by writing a failing test from the story spec, implementing minimally to pass, refactoring, and running a verification gate before completion.

What is the RED GREEN REFACTOR GATE cycle for story implementation?

The RED GREEN REFACTOR GATE cycle is a TDD workflow where you write a failing test, implement code to pass it, refactor while green, then run a fresh verification re-run before claiming story completion.

Does TDD story implementation require verbatim acceptance criteria in tests?

Yes, TDD story implementation forces verbatim acceptance criteria quoting in tests and code blocks, halting on missing identifiers to prevent hallucinated schema or API names during development.

How do I verify git feature branches before starting TDD work?

Branch and state safety verifies git feature branch rules, loads the correct state.yaml authority for worktrees, and requires story or ticket context to be present before allowing TDD work to proceed.

Can I run visual checks for frontend UI files during the TDD cycle?

Visual checks run at GREEN for frontend UI files using React Grab, with a safe fallback to standard review if the required MCP is unavailable in your development environment.

What limitations exist when completing a story without a verification re-run?

Completion is blocked without a fresh verification re-run; the process re-runs tests and checks evidence freshness from the RED test-run witness capture before allowing any story completion claim.