What problem does it solve? Large refactors such as schema migrations, concept renames, and structural reorganizations touch many files and accumulate stale assumptions that compound into costly mistakes. This Skill enforces a disciplined workflow: write a specification first, run two independent review gates (pre-implementation consistency and post-implementation quality), then implement against the verified spec. ## Core Features & Use Cases - Spec-first workflow: Analyze all affected contracts (schemas, scripts, tests, docs), write a markdown spec with design decisions, phased implementation order, and risks, then fix review findings before coding. - Dual review gates: A spec review sub-agent checks logical gaps and naming consistency, while a second consistency check verifies the spec's claims against the actual filesystem using terminal ground truth. - Post-implementation verification: Validate schemas, run the project's scaffold tool end-to-end, sweep for stale file references, and update the issue tracker. - Use Case: When renaming a concept across 20+ files including JSON schemas, build scripts, and tests, use this Skill to produce a spec, catch mismatched enum orderings and orphaned test files, and merge safely via sequential PRs. ## Quick Start Ask the agent to refactor the codebase by renaming a core concept across schemas, scripts, tests, and docs using the spec-driven refactoring workflow.
