implement-feature

Feature implementation using TDD requires writing failing tests first, then making minimal code changes to pass them. This skill automates that stepwise delivery by loading story context, confirming acceptance criteria, and verifying each step before committing progress.

Acceptance-criteria-driven development keeps requirements aligned with implementation by updating plan status sidecars after each completed step. This ensures traceable progress from the initial story ticket through every committed code change to the final working feature.

Test-first delivery loads feature context directly from project cards, requires failing tests before any code is written, and commits each verified step. This creates a reviewable sequence with clear evidence of completion tied to the original card requirements.

Acceptance criteria guide stepwise implementation by requiring confirmation before development begins, enforcing failing tests first, and verifying per-step progress. Each step is reviewed and committed only when it meets the confirmed criteria, ensuring the final code matches requirements.

Story-driven implementation requires failing tests before any code changes are made. This test-first approach ensures minimal modifications, per-step verification, and traceable commits that align with the story's acceptance criteria and overall feature delivery.

Per-step review and commits during feature implementation ensure traceable progress and maintain quality throughout development. By verifying each step against acceptance criteria before committing, the workflow prevents drift from requirements and produces clear evidence of completion.