requirement-workflow

Automating a TDD workflow involves orchestrating four phases: Specification, Test Design, Implementation, and Summary. This skill coordinates these phases with explicit user approvals and progress tracking, reading requirements from a default file like docs/feature_requirement_mvp1.md.

A REQ-driven development workflow uses requirement files to coordinate structured feature delivery across specification, test design, and implementation phases. Progress tracking is maintained through automatically generated artifacts and documentation updates aligned with phase gatekeeping approvals.

Yes, you can configure file paths, command defaults, and retry behavior for the automated development workflow. Settings are defined within the .claude/agent-config.yaml file, allowing you to tune file locations and workflow commands to match your project structure.

The four-phase TDD workflow supports frontend, backend, agent, and CLI projects requiring structured feature delivery. It adapts to various project types by generating phase-specific artifacts like specifications, test plans, and progress documentation.

To start the specification phase, provide a REQ ID and the path to your requirements file. The workflow then initiates Phase 1 and guides you through subsequent test design and implementation phases via on-screen prompts.

The best way to ensure acceptance criteria are met is using a coordinated four-phase workflow with gatekeeping approvals between phases. This approach separates specification and test design from minimal implementation, preventing misaligned scope and stalled progress.