speckit-plan

Generate design artifacts from a feature spec through spec-kit planning phases.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you turn a feature spec into an actionable implementation plan by generating required design artifacts, resolving clarifications, and enforcing planning gates so the workflow doesn’t stall or proceed with missing decisions.

Core Features & Use Cases

  • Executes a structured planning workflow from outline and research through data modeling, contracts, and quickstart generation.
  • Resolves NEEDS CLARIFICATION by dispatching research tasks and consolidating outcomes into research.md before advancing phases.
  • Integrates optional extension hooks before and after planning, while skipping invalid or disabled hooks safely.
  • Uses deterministic repo scripts for setup and agent-context updates to keep generated artifacts consistent with the spec-kit structure.

Quick Start

Run speckit-plan from the repository root to generate research.md, data-model.md, contracts, quickstart.md, and the agent-context updates required for Phase 1 planning.

Frequently Asked Questions about speckit-plan

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

FAQPage Schema
How do I generate design artifacts from a feature spec using spec-kit?▼

Generate design artifacts from a spec by running the planning workflow through outline, research, data-model, contracts, and quickstart phases to produce research.md, data-model.md, contracts, and quickstart.md files.

How does workflow automation handle NEEDS CLARIFICATION items during implementation planning?▼

Workflow automation resolves NEEDS CLARIFICATION items by dispatching research agent tasks and consolidating outcomes into research.md before advancing to subsequent planning phases.

Can I use planning guardrails with repositories that lack a .specify directory?▼

No, planning guardrails require a repository following the spec-kit structure with a .specify directory to run setup scripts, read templates, update memory, and enforce gate rules.

What is the best way to automate the spec-kit planning workflow through data modeling and contracts?▼

Automate the spec-kit planning workflow by executing deterministic repo scripts for setup and agent-context updates, progressing sequentially through data-model and contracts phases while enforcing clarification gates.

Why does implementation planning stall when unknowns are unresolved in feature specs?▼

Implementation planning stalls because planning gates enforce resolution of unknowns, requiring clarifications to be dispatched and consolidated into research.md before the workflow can advance safely.

Does spec-kit planning support custom extension hooks before and after plan generation?▼

Spec-kit planning integrates optional before_plan and after_plan extension hooks, executing valid configured hooks while safely skipping invalid or disabled ones during the planning workflow.