speckit-plan

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

Repositório: elsa-workflows/elsa-core
Última atividade na origem: 2 de maio de 2026 às 17:27
Idioma detectado do SKILL.md: inglês
Estrelas: 7.858
Forks: 1.522

Opções de instalação

Por padrão, está selecionado o prompt que primeiro revisa a origem. Você pode mudar para um comando direto ou baixar uma cópia local.

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.

npx skills add https://github.com/elsa-workflows/elsa-core --skill speckit-plan

O comando permanece em uma só linha. Role horizontalmente para revisá-lo antes de copiar.

Prefere uma cópia local? Baixe os arquivos disponíveis atualmente no SkillsMP.

Revise os arquivos de origem

Leia o SKILL.md e os arquivos complementares exibidos pelo SkillsMP antes de decidir se vai instalar.

SKILL.md

Instruções da origem · Visualização somente leitura

Voltar à pesquisa Voltar à instalação

condition

For each executable hook, output the following based on its optional flag:

Optional hook (optional: true):

## Extension Hooks

**Optional Pre-Hook**: {extension}
Command: `/{command}`
Description: {description}

Prompt: {prompt}
To execute: `/{command}`

Mandatory hook (optional: false):

## Extension Hooks

**Automatic Pre-Hook**: {extension}
Executing: `/{command}`
EXECUTE_COMMAND: {command}

Wait for the result of the hook command before proceeding to the Outline.

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").
Load context: Read FEATURE_SPEC and .specify/memory/constitution.md. Load IMPL_PLAN template (already copied).
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
Stop and report: Command ends after Phase 2 planning. Report branch, IMPL_PLAN path, and generated artifacts.
Check for extension hooks: After reporting, check if .specify/extensions.yml exists in the project root.
- If it exists, read it and look for entries under the hooks.after_plan key
- If the YAML cannot be parsed or is invalid, skip hook checking silently and continue normally
- Filter out hooks where enabled is explicitly false. Treat hooks without an enabled field as enabled by default.
- For each remaining hook, do not attempt to interpret or evaluate hook condition expressions:
  - If the hook has no condition field, or it is null/empty, treat the hook as executable
  - If the hook defines a non-empty condition, skip the hook and leave condition evaluation to the HookExecutor implementation
- For each executable hook, output the following based on its optional flag:
  - Optional hook (optional: true):
```
## Extension Hooks

**Optional Hook**: {extension}
Command: `/{command}`
Description: {description}

Prompt: {prompt}
To execute: `/{command}`
```
  - Mandatory hook (optional: false):
```
## Extension Hooks

**Automatic Hook**: {extension}
Executing: `/{command}`
EXECUTE_COMMAND: {command}
```
- If no hooks are registered or .specify/extensions.yml does not exist, skip silently

Extract unknowns from Technical Context above:
- For each NEEDS CLARIFICATION → research task
- For each dependency → best practices task
- For each integration → patterns task

Generate and dispatch research agents:

For each unknown in Technical Context:
  Task: "Research {unknown} for {feature context}"
For each technology choice:
  Task: "Find best practices for {tech} in {domain}"

Consolidate findings in research.md using format:
- Decision: [what was chosen]
- Rationale: [why chosen]
- Alternatives considered: [what else evaluated]

name	speckit-plan
description	Execute the implementation planning workflow using the plan template to generate design artifacts.
compatibility	Requires spec-kit project structure with .specify/ directory
metadata	{"author":"github-spec-kit","source":"templates/commands/plan.md"}
disable-model-invocation	true

name	speckit-plan
description	Execute the implementation planning workflow using the plan template to generate design artifacts.
compatibility	Requires spec-kit project structure with .specify/ directory
metadata	{"author":"github-spec-kit","source":"templates/commands/plan.md"}
disable-model-invocation	true

speckit-plan

Opções de instalação

Revise os arquivos de origem

User Input

Pre-Execution Checks

User Input

Pre-Execution Checks

Outline

Phases

Phase 0: Outline & Research

Phase 1: Design & Contracts

Key rules

speckit-plan

Informações da origem

Opções de instalação

Revise os arquivos de origem

Mais deste repositório

Mais deste repositório

User Input

Pre-Execution Checks

User Input

Pre-Execution Checks

Outline

Phases

Phase 0: Outline & Research

Phase 1: Design & Contracts

Key rules