What problem does it solve? Codebases drift away from their documentation, and design decisions get lost. This Skill produces canonical design specifications that describe exactly what exists in the current branch, keeping architecture, domain models, and contracts documented in a consistent, cross-linked structure. ## Core Features & Use Cases - Canonical spec authoring: Investigates the actual code, then writes numbered, layered markdown spec pages (global and per-package) with a JSON Schema sidecar for typed entities. - Change spec lifecycle: Drafts single-document change specs under .specs/changes/ with a Proposed → Accepted → Implemented → Merged lifecycle, then merges them back into the canonical spec when code ships. - Companion skill orchestration: Delegates development-guidelines and design-guidelines pages to companion skills and enforces a mandatory cross-linking and checklist pass before handoff. - Use Case: Ask it to spec out a new app in a monorepo using an existing app's specs as a template; it reads the code, writes the numbered spec set, and updates the .specs/README.md index. ## Quick Start Ask the agent to create a spec for the app at apps/web using the existing specs in .specs/ as a template.
