Vibe Index
🎯

speckit-plan

🎯Skill

from dceoy/speckit-agent-skills

VibeIndex|
What it does

Generates a comprehensive implementation plan for a feature by researching unknowns, defining data models, and creating technical design artifacts.

πŸ“¦

Part of

dceoy/speckit-agent-skills(10 items)

speckit-plan

Installation

git cloneClone repository
git clone https://github.com/github/speckit-agent-skills.git
πŸ“– Extracted from docs: dceoy/speckit-agent-skills
Need more details? View full documentation on GitHub β†’
4Installs
-
AddedFeb 4, 2026
View on GitHubBack to Skills

Skill Details

SKILL.md

Execute the implementation planning workflow using the plan template to generate design artifacts.

Overview

# Spec Kit Plan Skill

When to Use

  • The feature spec is ready and you need a technical implementation plan.

Inputs

  • specs//spec.md
  • Repo context and .specify/ templates
  • User-provided constraints or tech preferences (if any)

If the spec is missing, ask the user to run speckit-specify first.

Workflow

  1. Setup: Run .specify/scripts/bash/setup-plan.sh --json from repo root and parse JSON for FEATURE_SPEC, IMPL_PLAN, SPECS_DIR, BRANCH. For single quotes in args like "I'm Groot", use escape syntax: e.g 'I'\''m Groot' (or double-quote if possible: "I'm Groot").
  1. Load context: Read FEATURE_SPEC and .specify/memory/constitution.md. Load IMPL_PLAN template (already copied).
  1. Execute plan workflow: Follow the structure in IMPL_PLAN template to:

- Fill Technical Context (mark unknowns as "NEEDS CLARIFICATION")

- Fill Constitution Check section from constitution

- Evaluate gates (ERROR if violations unjustified)

- Phase 0: Generate research.md (resolve all NEEDS CLARIFICATION)

- Phase 1: Generate data-model.md, contracts/, quickstart.md

- Phase 1: Update agent context by running the agent script

- Re-evaluate Constitution Check post-design

  1. Stop and report: Command ends after Phase 2 planning. Report branch, IMPL_PLAN path, and generated artifacts.

Phases

Phase 0: Outline & Research

  1. Extract unknowns from Technical Context above:

- For each NEEDS CLARIFICATION β†’ research task

- For each dependency β†’ best practices task

- For each integration β†’ patterns task

  1. Generate and dispatch research agents:

```text

For each unknown in Technical Context:

Task: "Research {unknown} for {feature context}"

For each technology choice:

Task: "Find best practices for {tech} in {domain}"

```

  1. Consolidate findings in research.md using format:

- Decision: [what was chosen]

- Rationale: [why chosen]

- Alternatives considered: [what else evaluated]

Output: research.md with all NEEDS CLARIFICATION resolved

Phase 1: Design & Contracts

Prerequisites: research.md complete

  1. Extract entities from feature spec β†’ data-model.md:

- Entity name, fields, relationships

- Validation rules from requirements

- State transitions if applicable

  1. Generate API contracts from functional requirements:

- For each user action β†’ endpoint

- Use standard REST/GraphQL patterns

- Output OpenAPI/GraphQL schema to /contracts/

  1. Agent context update:

- Run .specify/scripts/bash/update-agent-context.sh

- Use the current runtime agent type (e.g., claude, codex, copilot, gemini). Leave empty to update all existing agent files.

- Update the appropriate agent-specific context file

- Add only new technology from current plan

- Preserve manual additions between markers

Output: data-model.md, /contracts/\*, quickstart.md, agent-specific file

Key rules

  • Use absolute paths
  • ERROR on gate failures or unresolved clarifications

Outputs

  • specs//plan.md (filled implementation plan)
  • specs//research.md
  • specs//data-model.md
  • specs//contracts/ (API schemas)
  • specs//quickstart.md
  • Updated agent context file (runtime-specific)

Next Steps

After planning:

  • Generate tasks with speckit-tasks.
  • Create a checklist with speckit-checklist when a quality gate is needed.

More from this repository9

🎯
speckit-tasks🎯Skill

Generates a dependency-ordered, actionable task list for a feature based on design artifacts and user stories.

🎯
speckit-constitution🎯Skill

Generates and synchronizes project constitution templates by interactively collecting principles and automatically updating dependent artifacts.

🎯
speckit-specify🎯Skill

Generates a concise feature specification and branch name from a natural language description, ensuring unique naming and context preservation.

🎯
speckit-implement🎯Skill

Implements feature tasks from tasks.md by executing a comprehensive implementation workflow with prerequisite and checklist validation.

🎯
speckit-analyze🎯Skill

Analyzes spectral data files, extracting key features and generating comprehensive statistical summaries for scientific research.

🎯
speckit-taskstoissues🎯Skill

Converts tasks from a markdown file into dependency-ordered, actionable GitHub issues for a specific feature.

🎯
speckit-baseline🎯Skill

Automatically generates feature specifications by analyzing existing source code, extracting key functionality, and creating standardized documentation.

🎯
speckit-checklist🎯Skill

Generates tailored, domain-specific checklists that validate requirements quality by identifying completeness, clarity, and potential gaps.

🎯
speckit-clarify🎯Skill

Identifies and resolves underspecified areas in a feature specification by asking targeted clarification questions and updating the spec accordingly.