modscape-spec-help

Displays the SDD workflow overview and answers questions about spec-driven development commands.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When working with a Spec-Driven Development (SDD) workflow for data pipelines, it is hard to remember which command to run next, what each command produces, or where decisions and artifacts are stored. This Skill provides an on-demand guide to the entire workflow. ## Core Features & Use Cases - Workflow Overview: Shows the full SDD pipeline from requirements through design, tasks, implementation, and archiving. - Command Summaries: Explains any specific command (requirements, design, tasks, implement, archive, status, check, search, answer, generate, note) in human-friendly terms by reading its definition. - Conceptual Q&A: Answers common questions such as the difference between requirements and design, or where Q&A and glossary data live after archiving. - Use Case: You are mid-way through designing a data pipeline and forgot whether to run tasks or check next — invoke this Skill to see exactly where you are in the workflow and what each command does. ## Quick Start Ask the assistant to show the modscape SDD workflow overview or explain what the design command does.

Frequently Asked Questions about modscape-spec-help

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

FAQPage Schema
How do I get started with spec-driven development for data pipelines?▼

Start by running the requirements command to create a spec.md capturing business goals, then run design to model tables and lineage, tasks to generate an implementation list, implement to execute tasks, and archive to merge results into the main model.

What is the difference between requirements and design in SDD?▼

Requirements captures the business goal in plain language — who needs it, what it solves, and what done looks like. Design translates those requirements into an actual data model with tables, columns, lineage, and relationships.

Can I run the design command multiple times?▼

Yes, running design multiple times is the intended workflow. Each re-run resumes the session from the current state, so you can iterate on the data model until you are satisfied before generating tasks.

What is the difference between spec-model.yaml and model.yaml?▼

spec-model.yaml is a work-scoped copy containing only tables relevant to the current pipeline, while model.yaml is the full project model. The archive command merges the work copy back into the main model when work is complete.

Where do decisions and Q&A go after archiving a spec workflow?▼

Table specs go to .modscape/specs/<table-id>/spec.md, Q&A history to _questions.yaml, business terms to _glossary.yaml, and architectural decisions to _context.yaml. Modeling and workflow conventions are stored in rules.custom.md and modscape-spec.custom.md.