What problem does it solve? It turns an already-confirmed requirement into the smallest complete, verifiable code change, preventing scope creep, speculative architecture, and unreviewable edits during implementation. ## Core Features & Use Cases - Scoped Implementation: Reads affected call paths, interfaces, and conventions before editing, then delivers an end-to-end vertical slice instead of broad scaffolding. - License and Boundary Safety: Enforces no-inherited-license rules, preserves external LICENSE and NOTICE files, and keeps frontend, backend, and contract layers properly separated. - Reviewable Changes: Runs the nearest useful check, inspects the final diff for residue or accidental API changes, and routes reproduced failures to the fix workflow. - Use Case: After a feature's acceptance criteria are confirmed, use it to implement the feature across the owning frontend feature, backend module, and contract boundary with focused tests, without dumping logic into entry files or shared utility folders. ## Quick Start Implement the confirmed login-rate-limit feature in the backend module and update its focused tests.
