modscape-spec-tasks

Generates a phased implementation task list from a spec-model.yaml lineage graph.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a data model specification into an ordered, dependency-aware implementation plan is manual and error-prone. This Skill reads spec-model.yaml, builds a dependency graph from lineage entries, and writes a phased tasks.md checklist so teams know exactly which tables to build and in what order. ## Core Features & Use Cases - Dependency-Based Phasing: Builds a graph from lineage entries and groups tables into ordered phases (e.g., Staging, Core, Mart) so upstream tables are implemented first. - Context-Only Exclusion: Reads design.md to skip tables marked as "Downstream — Context Only", keeping the task list focused on real implementation targets. - Incremental Merge: When tasks.md already has completed items, it presents a diff and merges changes instead of overwriting completed work. - Use Case: After designing a star schema in Modscape, run this Skill to produce a tasks.md checklist grouped by layer, then hand it to the implementation step. ## Quick Start Ask the AI to run @modscape-spec-tasks with your spec name to generate the implementation task list from spec-model.yaml.

Frequently Asked Questions about modscape-spec-tasks

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

FAQPage Schema
How do I generate an implementation task list from a data model spec?▼

Run @modscape-spec-tasks with your spec name. It reads spec-model.yaml, builds a dependency graph from lineage entries, groups tables into phases, and writes the result to .modscape/changes/<name>/tasks.md.

How are tables ordered into phases in the generated tasks?▼

Tables are grouped by their position in the lineage dependency graph, with upstream tables placed first. Phase names reflect each group's role, such as Staging, Core, or Mart, and can be overridden by rules in modscape-spec.custom.md.

What happens if tasks.md already has completed tasks?▼

The Skill performs a merge instead of overwriting. It shows a diff of additions, keeps, and removals for confirmation, preserves completed [x] items still in the spec, adds new tables as unchecked, and deletes removed tables.

Why does task generation stop with a lineage error?▼

The Skill requires lineage entries in spec-model.yaml to build the dependency graph. If lineage is missing or empty, it stops and instructs you to run @modscape-spec-design first to define table relationships.

Can I exclude downstream tables from the implementation task list?▼

Yes. Tables marked as "Downstream — Context Only" in the Affected Tables section of design.md are added to a skip list and excluded from all phases in the generated tasks.md.