Add yolo to community workflow catalog

[clintcparker]

Workflow Submission

Workflow Name: Full SDD Cycle - no gates
Workflow ID: yolo
Version: 0.1.0
Repository: https://github.com/clintcparker/speckit-addons
Raw YAML: https://raw.githubusercontent.com/clintcparker/speckit-addons/yolo-v0.1.0/workflows/yolo/workflow.yml
Release: https://github.com/clintcparker/speckit-addons/releases/tag/yolo-v0.1.0

yolo is the built-in speckit workflow with the two review gates removed: specify → plan → tasks → implement, straight through. It exists for the case where you already trust the shape of the change and would rather review the finished branch than approve two intermediate artifacts — the safety net being source control rather than a gate.

On the missing gates

The publishing guide recommends gates at decision points, so to be explicit: their absence here is the feature, not an oversight. The README says so plainly and tells users to run it on a branch. The built-in gated speckit workflow remains the right default for most people; this is the deliberate opposite trade, and it's marked as such in the name, the description, and the no-gates tag.

Security surface

No shell steps. All four steps are command steps invoking core Spec Kit commands, so there is no arbitrary-command execution to audit and nothing that needs the run-field scrutiny the guide calls for.

Checklist

• Valid workflow.yml (passes specify workflow info)
• README.md with description, inputs, and step graph
• LICENSE file included (MIT, at the repository root)
• GitHub release created with raw YAML URL
• Workflow tested end-to-end with specify workflow run
• All gate steps have clear review messages — n/a, this workflow has no gate steps by design
• Input prompts are descriptive
• Added to workflows/catalog.community.json (alphabetical order — inserted after pipeline)

Notes

• requires.speckit_version is >=0.8.5, the first release that resolves integration: "auto" engine-side rather than treating it as a literal integration key.
• requires.integrations.any: ["claude"] is an advisory compatibility hint. All four commands are core commands provided by every integration, so the workflow runs against whatever the project was initialized with.
• Verified end to end against the published catalog before submitting: specify workflow catalog add → specify workflow add yolo → specify workflow info yolo reports v0.1.0 with four command steps and no gates. Prior real-project usage is described in this write-up.
• The repository is a monorepo intended to host further add-ons, so the workflow lives at workflows/yolo/ rather than at the repository root. The catalog url is pinned to the per-add-on tag yolo-v0.1.0.

[Copilot]

Pull request overview

Adds the gate-free yolo workflow to the community catalog.

Changes:

• Adds pinned workflow metadata, documentation, and tags.
• Refreshes the catalog timestamp.

Show a summary per file

File	Description
workflows/catalog.community.json	Registers the yolo workflow.

Review details

Tip

Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

• Files reviewed: 1/1 changed files
• Comments generated: 1
• Review effort level: Medium

[mnriem]

Please address Copilot feedback

[Copilot]

Review details

Comments suppressed due to low confidence (1)

workflows/catalog.community.json:38

• This updates only the catalog metadata, while the tagged yolo-v0.1.0 artifact at line 32 still declares speckit_version: ">=0.8.5"; its README, changelog, and release notes also advertise that range. The installer downloads that artifact, so users on 0.8.5–0.8.11 still receive a workflow claiming compatibility even though integration: "auto" fails there. Publish a corrected workflow release with >=0.8.12, then point this entry's version and pinned URLs at that release so the catalog and installed definition agree.

        "speckit_version": ">=0.8.12"

• Files reviewed: 1/1 changed files
• Comments generated: 0 new
• Review effort level: Medium

[mnriem]

Thank you!