| name | fixflow |
| description | Execute coding tasks with a strict delivery workflow: build a full plan, implement one step at a time, run tests continuously, and commit by default after each step (`per_step`). Support explicit commit policy overrides (`final_only`, `milestone`) and optional BDD (Given/When/Then) when users ask for behavior-driven delivery or requirements are unclear. |
Fixflow
Overview
Use this skill to deliver end-to-end engineering work in one run:
- Plan fully.
- Execute in strict sequence.
- Validate continuously.
- Use explicit commit policy (
per_step default; final_only/milestone when requested).
- Add BDD behavior specs when requested or when requirements are ambiguous.
Trigger Cues
Trigger this skill when the user asks for one or more of:
- Full plan + sequential execution.
- No backward compatibility.
- Test everything before handoff.
- Commit after completion or commit before each next step.
- Behavior-driven delivery (BDD) or acceptance scenarios.
Workflow
1. Define Ready Criteria (DoR)
See shared delivery base: references/delivery-base.md
2. Build Complete Plan Before Editing
See shared delivery base: references/delivery-base.md
3. Add BDD/TDD Layer When Needed
Use BDD if user requests it, or if requirements are unclear.
3.0 TDD Mode (RED -> GREEN -> IMPROVE)
When user requests TDD or test-driven delivery:
-
RED — Write a failing test first
