What problem does it solve? AI-assisted coding sessions often drift into unplanned refactors or break contracts that were never written down. This Skill locks implementation boundaries before planning or coding by recording invariants, non-goals, and forbidden changes on disk, so every later step reads the same constraints instead of guessing. ## Core Features & Use Cases - Boundary Definition: Identifies external behavior, contracts, and data assumptions that must remain unchanged, plus modules that should not be touched. - Scope Guardrails: Records tempting but out-of-scope refactors and forbidden changes to prevent scope creep during implementation. - State Persistence: Writes INVARIANTS_AND_NON_GOALS.md and updates TASK_STATE.md with constraints, risks, and the recommended next command. - Use Case: After impact analysis on a feature touching authentication flows, run this Skill to lock session-handling invariants (logout, backgrounding, force-quit) before any implementation plan is written. ## Quick Start Run the invariants-and-non-goals command on the active task to lock implementation boundaries into INVARIANTS_AND_NON_GOALS.md before planning begins.
