1_implement

To turn a project spec into a phased implementation plan, you provide the spec name stored in .claude/specs. The skill generates a structured plan, creates a git checkpoint, and begins test-driven execution with artifact tracking and safety verifications.

The best way to decompose large features into manageable sub-specs is by automating spec translation into staged execution. This approach divides work into phases and provides a rollback mechanism via git checkpoints to ensure safety.

Yes, automated spec implementation requires your project to follow CLAUDE.md guidelines. The skill enforces a stepwise approach by verifying directives, creating phase manifests, tests, and blockers against these established guidelines.

To enforce safety checkpoints during multi-phase feature implementation, the skill automates plan gating and git checkpoint creation at each phase. It tracks artifacts and verifies tests against CLAUDE.md directives before proceeding.

Yes, you can use git checkpoints to rollback a test-driven implementation plan if a phase fails. The skill creates robust branching and checkpoint mechanisms to safely revert work when blockers or verification failures occur.