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. ## When to Activate 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. ## Red Flags - Execution starts while requirements, non-goals, or compatibility policy are still ambiguous. - Multiple feature steps are implemented before any mapped test command runs. - Commit policy is implicit, changes mid-run, or ignores user override. ## Checklist - [ ] Pin the commit policy before editing. - [ ] Map each feature step to at least one concrete validation command. - [ ] Complete the current step, run its checks, and record status before starting the next step. ## Delivery Selection Start Fixflow when the user requests implementation and the bounded outcome is clear. Small fixes execute directly; major architecture or migration work may consume a concise existing plan. Clarify only a missing choice that would materially change the result or safety. No routing packet or fixed handoff fields are required. Do not delegate by default. If the...