hernandor/dev-loop

Use when starting or organizing development work that may involve design decisions, external APIs, typed public surfaces, Python tooling, repeatable commands, verification, or commits.

Use after implementation work is verified and the branch needs a merge, pull request, preservation, cleanup, or discard decision.

Use when making code, documentation, tooling, or skill changes that should be committed, branched, reviewed, merged, reverted, or split into versioned steps.

Use when a project has a Justfile, needs repeatable command recipes, or has multi-step build, test, lint, docs, benchmark, or release workflows.

Use when a TDD ladder has reached green and its tests are about to merge, when a branch diff adds tests that only restate the code they drove, or when the test suite prevents refactoring instead of catching regressions. Triggers on "these tests only repeat the code", "this test fails after every rename", "drop the redundant tests", "the suite blocks every refactor". Do not use it to delete failing tests and make a red suite green.

Use when implementing an accepted ADR through a sequence of red-test-then-implement steps, when a feature must be split into verifiable tasks with explicit failure-fragment prediction, or when previous implementations have skipped the red-test step under deadline pressure.

Use when starting isolated feature work, parallel development, risky experiments, implementation plans, or any task that should not disturb the current working tree.

Use before claiming work is complete, fixed, passing, validated, ready to commit, ready to merge, or safe to hand off.