What problem does it solve? Design reasoning behind a module's code disappears when a work session ends, leaving future maintainers unable to tell deliberate constraints from accidental ones. This Skill captures that durable knowledge in a per-module CONTEXT.md file so decisions, invariants, and cross-module relationships survive across sessions. ## Core Features & Use Cases - Decision Capture: Records architectural decisions with their reasoning, including rejected alternatives, at the moment the decision is made. - Pre-Modification Reading: Requires reading the CONTEXT.md of every module before changing it, and flags conflicts instead of silently overriding deliberate design. - Lifecycle Maintenance: Creates CONTEXT.md only when the first durable decision lands, and updates or removes superseded entries to prevent stale guidance. - Use Case: Before modifying an Intent Architect module's template, you read its CONTEXT.md and discover the template must stay transport-agnostic; after introducing a new setting-driven wiring change, you record the decision and the alternative you rejected. ## Quick Start Read the CONTEXT.md of the module I am about to modify, then record the design decision we just made along with the alternatives we rejected.
