modscape-spec-check

Validates specification consistency and implementation readiness against a chosen SSOT artifact.

Updated Feb 25, 2026
One-click install
npx skills add https://github.com/yujikawa/modscape --skill modscape-spec-check-yujikawa
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: modscape-spec-check
Source: https://github.com/yujikawa/modscape/tree/main/src/templates/gemini/modscape-spec-check
Command: npx skills add https://github.com/yujikawa/modscape --skill modscape-spec-check-yujikawa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Before writing code, teams need confidence that their spec, design, tasks, and data model agree with each other. This Skill performs a pre-implementation quality check that detects inconsistencies across change artifacts and produces a go/no-go readiness verdict. ## Core Features & Use Cases - SSOT-Driven Consistency Checks: Cross-checks spec-model.yaml, design.md, spec.md, tasks.md, and questions.md against a selectable single source of truth, with a concrete fix suggestion for every issue found. - Readiness Report: Counts unresolved questions and assumptions, classifies acceptance criteria coverage, and optionally runs documentation coverage via the modscape CLI. - Clear Verdicts: Outputs a structured report ending in one of three verdicts: ready to implement, review warnings, or blocking issues. - Use Case: After drafting a design for a new data model change, run the check against spec-model.yaml to confirm every table is classified, every impacted table has tasks, and every open question has an assumption before implementation begins. ## Quick Start Ask the AI to run a spec check on your current change, for example by saying: run modscape-spec-check on my change using spec-model.yaml as the source of truth.

Frequently Asked Questions about modscape-spec-check

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check if my spec is ready for implementation?▼

Run the spec check with a change name and an optional SSOT artifact. It cross-checks spec.md, design.md, tasks.md, and spec-model.yaml, then reports a verdict: ready, warnings, or blocking issues with fix suggestions.

What does SSOT mean in a spec consistency check?▼

SSOT means single source of truth, the artifact treated as authoritative during the check. You can choose spec-model.yaml, design.md, or spec.md with the --from flag, and the consistency rules adapt to that choice.

Which files does the spec check read?▼

It reads spec.md, design.md, tasks.md, questions.md, and spec-model.yaml from the change directory under .modscape/changes. Missing files are skipped silently and noted in the output.

Can the spec check verify acceptance criteria coverage?▼

Yes. It classifies each acceptance criterion as covered by a test, requiring manual verification, or uncovered. Uncovered criteria block a clean verdict and prompt you to add a task or mark them manual.

What happens when unresolved questions are found?▼

Open Q-NNN questions are counted and listed in the readiness section. If they lack an Assumption block in design.md, the check flags a warning and suggests running the answer workflow before implementing.