modscape-spec-archive

Merge work-scoped YAML into the main model and archive completed data specs.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Finalizing a data modeling change requires manually merging work-scoped YAML back into the main model, updating permanent table documentation, and archiving the work folder — a tedious, error-prone process that this Skill automates end to end. ## Core Features & Use Cases - Merge Preview & Confirmation: Shows a dry-run diff of tables to add, update, or remove, plus lineage replacements, before touching the main YAML. - Permanent Spec Sync: Creates or updates per-table spec files in .modscape/specs/<MODEL_SLUG>/ with business context, rules, usage guides, and changelogs. - Knowledge Consolidation: Merges curated Q&A, glossary terms, and architectural decisions into _questions.yaml, _glossary.yaml, and _context.yaml. - Use Case: After finishing a spec-driven design change with modscape, run the archive step to merge spec-model.yaml into the master model, sync documentation, enforce coverage gates, and move the work folder to .modscape/archives/. ## Quick Start Run the modscape-spec-archive skill with my spec name to merge the work YAML into the main model and archive the change.

Frequently Asked Questions about modscape-spec-archive

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

FAQPage Schema
How do I merge a spec YAML back into the main modscape model?▼

Run the archive skill with your spec name. It shows a merge preview of tables to add, update, or remove, waits for confirmation, then runs modscape merge with --patch and --replace-owned-lineage, followed by validation.

What happens if no main YAML exists when archiving a modscape spec?▼

The skill detects this as a greenfield project. It skips the merge steps and copies spec-model.yaml directly to a path you choose (default model.yaml), treating all tables as Direct Impact.

Does modscape spec archive update permanent table documentation?▼

Yes. It performs a full spec sync for Direct Impact and Downstream Implement tables in .modscape/specs/<MODEL_SLUG>/, and appends changelog-only entries for Context Only tables.

Can I enforce a documentation coverage threshold before archiving?▼

Yes. If modscape-spec.custom.md contains a Coverage Policy section with a minimum percentage, the skill runs modscape coverage and prompts for confirmation when actual coverage falls below the threshold.

What happens to questions and glossary entries after archiving?▼

Answered or assumed questions are curated into _questions.yaml and glossary terms into _glossary.yaml, filtered to include only data analysis knowledge. The work folder is then moved to .modscape/archives/ with the phase set to done.