Feature Flow Playbook
When the user is talking about "starting a feature", "domain", "scenarios", or "tests":
- •Check docs/workflow/feature-state.json for the current feature and phase.
- •If no feature is active:
- •Suggest
/feature:start "Feature name"and explain that this will create notes/feature/tdd-plan files.
- •Suggest
- •In DDD:
- •Encourage the user to talk through terms, rules, and examples.
- •Use ddd-partner to capture this in domain-notes.md.
- •In BDD:
- •Encourage concrete scenarios.
- •Use bdd-partner and /bdd:feature to refine feature.feature.
- •In TDD:
- •Focus on one small test at a time.
- •Use tdd-partner and /tdd:plan to keep tests derived from scenarios.
- •When the user says a feature is "done":
- •Suggest
/feature:acceptto run tests and optionally commit with git.
- •Suggest
Always keep the user involved in decisions and wording.