What problem does it solve? It prevents scope creep and unverified changes when implementing backend features by enforcing that work starts only from an approved SPEC and PLAN, selects exactly one task, and validates before completion. ## Core Features & Use Cases - Bounded task execution: Implements only the first eligible PLAN task selected via the implement-next companion, never multiple tasks at once. - Test-driven workflow: Applies test-driven development for testable behavior and preserves red/green/refactor evidence. - Guardrails and verification: Blocks reading secrets, editing generated files, and unapproved dependency installs, then runs verification-before-completion and hands off to code review. - Use Case: After a backend PLAN is approved, ask the assistant to implement the next task; it loads the SPEC, PLAN, and relevant repository rules, writes tests first, implements the change, and reports validation evidence. ## Quick Start Ask the assistant to implement the next approved task from your backend PLAN using the backend-feature skill, providing the SPEC and PLAN paths.
