Keeps AI coding agents on the intended goal and stops them skipping steps. It records confirmed requirements in the current spec, and applies firm checks like design alignment, debugging and review only when a risky change is at stake.
@chipfighterUse before coding when requirements have multiple reasonable interpretations, approaches require tradeoffs, or mistakes would be…
@chipfighterUse when changes affect interactions across multiple modules, involve high-risk areas (authorization/authentication,…
@chipfighterUse when starting a project, reading project documentation or history, or resolving conflicts between documents. For current…
@chipfighterUse when creating a branch, using worktrees for parallel work, committing, or wrapping up. Covers branch naming, conventional…
@chipfighterUse in cross-session work when user-confirmed outcomes, non-goals, hard constraints, or acceptance criteria have not been written…
@chipfighterUse before proposing a permanent fix for bugs, test failures, or unexpected behavior with an unknown root cause—mandatory when…
@chipfighterUse before implementation when behavior can be verified by automated tests and regression coverage has clear value. For bugs with…
@chipfighterUse before claiming "done", "fixed", "tested", or "it runs", and before committing or opening a PR or MR—no task is exempt.…
@chipfighterIs this you? Claim your profilePut a plugin at the top of Plugins, from $9
