apply

You can drive implementation from Gherkin features by interpreting specification artifacts to simulate a disciplined TDD workflow. This approach validates code changes against feature files, ensuring feature-driven tests guide the development process.

Proposal-driven TDD enables testing when Gherkin is skipped, using proposal artifacts to validate changes. You need this approach when your workflow lacks Gherkin feature files but still requires a test-first methodology guided by proposal specifications.

Managing tasks during a TDD workflow involves iterative task completion with status updates via artifacts like tasks.md, design.md, and status.yaml. Mode-aware execution supports planner or executor strategies, ensuring artifact-driven scoping and status tracking for each change.

Yes, the workflow includes worktree isolation checks to ensure safe code changes and configuration-driven test framework selection. These features guarantee that your TDD-driven implementation operates in an isolated environment with your preferred testing framework.

The best way to align design decisions with concrete tests is using an artifact-driven specification approach. By enforcing a disciplined test-first methodology, this approach ensures design choices are validated through Gherkin features or proposal artifacts during implementation.

Yes, you can use planner or executor strategies based on tasks.md and features for artifact-driven code changes. Mode-aware execution supports these strategies, allowing scoped implementation and status tracking for each individual change.