speckit-plan

Coordinate multi-repo planning workflows to generate tasks, checklists, and design artifacts.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/datamonsterr/mycoai_projects --skill speckit-plan-datamonsterr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-plan
Source: https://github.com/datamonsterr/mycoai_projects/tree/main/.agents/skills/speckit-plan
Command: npx skills add https://github.com/datamonsterr/mycoai_projects --skill speckit-plan-datamonsterr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

speckit-plan coordinates a multi-repo planning workflow to prepare implementation projects across related repositories, enabling coordinated design and task generation.

Core Features & Use Cases

  • Orchestrates an end-to-end planning workflow across multiple repositories
  • Generates tasks, checklists, and design artifacts from a plan template
  • Discovers and analyzes affected repositories to scope work and branches

Quick Start

Run speckit-plan at the project root to generate a multi-repo implementation plan and artifacts.

Frequently Asked Questions about speckit-plan

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

FAQPage Schema
How do I automate multi-repo planning across related repositories?▼

Multi-repo planning is automated by orchestrating an end-to-end workflow that auto-discovers affected child repositories, scopes branches, and generates coordinated design artifacts and tasks from a plan template.

What is Spec-kit-style planning for large codebases?▼

Spec-kit-style planning coordinates implementation projects across related repositories by applying template-driven execution to generate checklists, design artifacts, and affected-repo analysis for large codebases.

How do I generate design artifacts like research.md and data-model.md for implementation projects?▼

Generate design artifacts by running a template-driven plan execution at the project root, which automatically produces research.md, data-model.md, contracts/, and quickstart.md files alongside task checklists.

Can I auto-discover child repositories when planning codebase changes?▼

Auto-discovery of child repositories is supported natively, allowing the planning workflow to automatically identify, analyze, and scope affected downstream repos within a large codebase before generating implementation tasks.

Does multi-repo planning work without external dependencies?▼

Multi-repo planning runs without external dependencies, relying on internal guardrails and hooks processing to execute template-driven workflows and update agent-context across discovered repositories.

What's the best way to coordinate tasks and checklists across multiple repositories?▼

Coordinate tasks by running a centralized planning workflow that applies template-driven execution to generate synchronized checklists and design artifacts across all auto-discovered affected repositories simultaneously.