speckit-plan

Generate design notes, data-model hints, API contracts, and ADRs for GitHub Issues.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/ranvirsingh/speckit --skill speckit-plan-ranvirsingh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-plan
Source: https://github.com/ranvirsingh/speckit/tree/main/skills/speckit-plan
Command: npx skills add https://github.com/ranvirsingh/speckit --skill speckit-plan-ranvirsingh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

Speckit-plan helps teams design architecture and keep a living plan attached to the issue-backed spec, reducing cycle time and misalignment.

Core Features & Use Cases

  • Design-focused planning: generate architecture notes, data-model hints, and API contracts beneath the spec.
  • Living-doc updates: automatically update docs/adr/, docs/data-model.md, docs/contracts/ with the plan artifacts.
  • Governance and orchestration: preserve the canonical spec in the issue while appending the plan and ADRs.

Quick Start

Provide the GitHub Issue number and let Speckit Plan generate the design notes and a task checklist appended to the issue.

Frequently Asked Questions about speckit-plan

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

FAQPage Schema
How do I generate architecture notes and API contracts from a GitHub issue spec?

Generate architecture notes, data-model hints, and API contracts from a GitHub issue spec by providing the issue number to produce design artifacts and append a task checklist directly to the issue.

What is the best way to keep living documentation updated with architecture decisions during feature planning?

Keep living documentation updated by automatically generating and appending ADRs, data models, and API contracts to designated docs directories while preserving the original issue spec as the canonical source.

How do I append a task checklist and design notes to an existing GitHub Issue?

Append a task checklist and design notes to an existing GitHub Issue by processing the issue-backed spec to extract design artifacts and update the issue body with the generated plan.

Can I use issue-backed specs to generate ADRs without manually writing architecture documentation?

Yes, issue-backed specs can generate ADRs automatically by analyzing the feature design to produce architecture notes and saving them directly into the living docs directory structure.

Does preserving the canonical spec require manually separating the original issue text from the generated plan?

No, preserving the canonical spec happens automatically during the planning flow; the original issue text remains the canonical source while the generated design notes and ADRs are appended beneath it.