Community workflows compose Spec Kit steps into independently maintained, repeatable processes.
Note
Maintainers check catalog entry form and completeness, not workflow code, scripts, or dependencies. A listing is not an audit, endorsement, or support commitment. Review source, required integrations, side effects, and review gates before installation and use.
Entries in the community workflow catalog:
| Workflow | Version | Description |
|---|---|---|
ADO story lifecycle (ado-lifecycle) |
0.3.1 | Takes an Azure DevOps story to an open pull request with a preview, a human gate and an apply for every Azure Boards or PR change |
Guided SDD Pipeline (pipeline) |
1.1.0 | Chains specify, clarify, plan, tasks, analyze, implement, and converge, with a clarify gate and post-implementation convergence loop |
Full SDD Cycle - no gates (yolo) |
0.1.0 | Runs specify, plan, tasks, and implement without review gates |
These are community definitions, distinct from the workflows bundled with Spec Kit. Inspect active sources and advertised releases:
specify workflow catalog list
specify workflow search
specify workflow info <id> --versionsSearch uses all active workflow catalogs. The built-in community source is
discovery-only: a listing does not make specify workflow add <id> installable
through that source. After vetting a release, install its pinned URL explicitly
or use a separately configured catalog you trust and allow for installation.
Publish a versioned workflow definition or complete package and submit a focused
PR editing workflows/catalog.community.json. Include release metadata,
documentation, required integrations and side effects, and end-to-end testing
evidence, including applicable gate and resume behavior.
Workflow definitions do not use a submission issue form. The Workflow Step Type Submission form is for executable custom step packages, not workflows. The publishing guide owns the catalog entry format and release-update procedure.