Skip to content

Workflow

Jump to bottom
Samy K. Abushanab edited this page Nov 6, 2026 · 1 revision

Published from docs/extensions/workflow.md at 835522e. Edit the source in the repository, not this page.

Purpose: run one GitHub issue from scope to a verified pull request through a resumable dispatcher. Workflow coordinates the other extensions and can resume in a new session.
Lifecycle phase All of them, as sixteen stages
Hooks None of its own; it disables the hooks it owns and runs them as stages (hooks)
Commands 13, including init, scope, clarify, continue, finalize, status, doctor (reference)
Requires Python 3.11 or later, Git, gh; installs Scope, Project, PR, Illustrate and selected Assure and User Manual
Standalone Yes; it is the managed level
License MIT

Setup

Follow the managed-workflow scenario.

Example

/speckit-workflow-scope 412 Assess refund approval and continue through implementation under project policy.
/speckit-workflow-clarify Reread issue 412's answers and resume the bound feature.
/speckit-workflow-continue Resume specs/412-refund-approval from its checkpoint.
/speckit-workflow-finalize Finish current checks and documentation; create or update the refund feature's PR.

How it runs

Workflow sequence: you run workflow.scope on an issue (a Scope panel lists workflow.scope-run, workflow.scope-plan and the five workflow.scope-* hooks); the dispatcher then runs Scope, Specify and Clarify (pausing for questions), Plan and Tasks, Analysis and Implement, Verify and Review with recorded check evidence, and the selected QA and manual documents; you run workflow.finalize to hand off the PR, which is blocked if evidence is stale.

You use four entry points: Scope, Clarify, Continue and Finalize. The dispatcher owns every stage between them. With profiles enabled, small features run a shorter chain: Tasks merges into Plan and Analyze becomes a deterministic lint; the lite tier runs seven stages, folding Analyze into Plan and Review and Ready into Verify, with no task sub-issues and no QA or manual stages. With Memory installed, the claim also runs Memory's session check and can return memory_blocked or memory_dispatch instead of a stage. The dispatcher skill is named speckit-workflow. Editable diagram.

Limits

  • Merge and deployment need separate authorization.
  • Utilities such as verify-affected do not claim or complete a stage. Their local results do not count as remote CI evidence.
  • A schema pass is not acceptance. Runtime checks also enforce identity, freshness and stage order.

Guide: Workflow README. Reference: stages, state files, schemas, runner policy, utilities, delegation, development.

Published from samykabu/sanduq at 835522e. The pages live in the repository's docs/ folder; edit them there. MIT licensed.

Home

Start

Choose how much to use

Managed delivery

Checks and pull requests

Documentation

Tracking and context

Reference

Portable skills wiki

Clone this wiki locally