wtf.implement-task

To implement a GitHub Task using test-driven development, the Skill reads the full spec hierarchy, maps acceptance criteria to the codebase, and drives TDD implementation against Gherkin scenarios. It scaffolds a concrete technical approach with explicit file paths to guide coding.

Mapping an Epic-Feature-Task hierarchy to a codebase involves reading the spec hierarchy from the issue and proposing a concrete technical approach with explicit file paths. This ensures the implementation follows the documented contract and reduces interpretation errors.

Yes, you can automate Gherkin scenario testing directly from a GitHub issue by reading the full spec hierarchy and driving a test-first implementation. The Skill extracts acceptance criteria and contracts to update the Task issue with progress and results.

Yes, a defined steering contract model is required to guide decisions and checkpoints during TDD implementation. It ensures the test-first workflow against Gherkin scenarios follows the documented contract and acceptance criteria accurately.

To reduce interpretation errors when implementing features from a spec, read the full Task-Feature-Epic hierarchy and map acceptance criteria to concrete file paths. Driving test-first implementation against Gherkin scenarios ensures the code follows documented contracts and minimizes rework.