What problem does it solve? Adding a new rule, clarification, rationale, or pointer to a software architecture guideline requires coordinated edits across many files: the guideline text, the lens catalog, generated review skills, the static checker, docs, and the README. Doing this cascade by hand is error-prone and easy to leave incomplete. ## Core Features & Use Cases - Aspect classification and placement: Classifies the input as a rule, clarification, rationale, or pointer, then decides its shape (section, subsection, paragraph, or sentence) and where it lives in reading order. - Full cascade management: Updates the table of contents via make gen-toc, regenerates review skills via make gen-skills, syncs lens ids and severities in the checker, and touches docs, README, and AGENTS.md when needed. - Release-level reporting: Produces a structured report naming the kind, shape, lenses changed, cascade, release note, and semver level (minor, major, or patch). - Use Case: A maintainer wants to add a "Reference Implementation" pointer at the end of the guideline. The skill writes the section in the guideline's voice, links it from the introduction, runs make check, and reports the change as a patch-level release. ## Quick Start Run the skill in a checkout of the guideline repository with a sentence describing the aspect, such as asking it to add a rationale explaining why the guideline names specific technologies.
