What problem does it solve? Legacy or ungoverned code often works correctly but has no written specification, making it risky to change and impossible to review against intent. This Skill brings existing code under a documented convention by deriving acceptance criteria from observed behavior, without modifying the code itself. ## Core Features & Use Cases - Behavior-Derived Specs: Reads existing tests, source code, and docs to draft SPEC.md, CONTEXT.md, and CLAUDE.md that describe what the code observably does today. - Deterministic Linting: Runs the speccle oracle CLI to lint the derived spec until clean, enforcing fixed rules like malformed-id, weasel-wording, and compound-criterion. - Criterion Claiming: Tags existing tests with [KEY-n] criterion ids, moves tests beside the code they defend, and writes new tests only for unclaimed criteria. - Findings Workflow: Suspicious behavior is recorded as findings for a human to rule intended-or-bug at the spec summary, never silently fixed. - Use Case: You inherit a working checkout module with no documentation. Ask the agent to carve it into a governed feature folder, and it produces a linted spec, a glossary, tagged tests, and a summary of questionable behaviors for your ruling. ## Quick Start Carve the existing checkout module into a governed feature folder by deriving its spec from observed behavior and tagging the tests that already defend each criterion.
