fixflow

# 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`](./references/delivery-base.md) ### 2. Build Complete Plan Before Editing > See shared delivery base: [`references/delivery-base.md`](./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: 1. **RED** — Write a failing test first - Extract testable behavior from requirements - Write minimal test case asserting expected behavior - Run test, confirm it fails (red) - If test passes unexpectedly -> requirement already met or test is wrong 2. **GREEN** — Write minimal implementation - Write just enough code to make the test pass - No extra improvements, no "while I'm here" change...