modscape-spec-design

Designs YAML data models from spec.md and updates work-scoped spec-model.yaml iteratively.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Translating a written requirements spec into a concrete data model is error-prone and hard to iterate on, especially when changes must not touch the main model file. This Skill turns a spec.md into a validated, work-scoped YAML data model that can be refined table by table. ## Core Features & Use Cases - Spec-driven model design: Reads spec.md and business context, then creates or updates tables, lineage, and relationships in changes/<name>/spec-model.yaml via the modscape CLI. - Incremental one-table-per-invocation workflow: Tracks design progress in design.md, generates stub design docs for all affected tables, and details one table per run. - Impact and traceability management: Classifies downstream impact, records open questions and assumptions in questions.md, detects tacit-knowledge risks, and maintains a project glossary. - Use Case: A data engineer runs the skill against a new feature spec to extract relevant tables from the main YAML, design a new fact table with lineage and FK relationships, validate the model, and produce review-ready design documentation. ## Quick Start Ask the AI to run @modscape-spec-design with your spec name to design the next pending table in your data model.

Frequently Asked Questions about modscape-spec-design

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

FAQPage Schema
How do I design a data model from a spec file?▼

Run @modscape-spec-design with your spec name after creating spec.md via the requirements step. The skill reads the spec, extracts relevant tables from the main YAML, and designs tables one per invocation into a work-scoped spec-model.yaml.

How do I iterate on a data model design without changing the main YAML?▼

All changes go to changes/<name>/spec-model.yaml, never the main model file. Re-run the skill repeatedly; it tracks progress in design.md and picks up the next pending table each invocation.

Does modscape-spec-design modify the main model.yaml directly?▼

No. It only updates the work-scoped spec-model.yaml under changes/<name>/. The main YAML is read via the modscape CLI for extraction and downstream impact analysis but never edited.

What happens if spec.md is missing when running the design skill?▼

The skill stops and instructs you to run @modscape-spec-requirements first to create spec.md. It also stops if no spec exists, prompting you to run modscape spec new <name>.

How are unresolved design questions and assumptions tracked?▼

Questions are appended to questions.md with status answered, assumed, or open, including AI-detected tacit-knowledge risks with PII-safe investigation queries. Unresolved items are surfaced in the review checkpoint after each run.