From 89bf42338399327f94922e8173b0d08fb708d91d Mon Sep 17 00:00:00 2001 From: Yash-Chindam Date: Wed, 2 Sep 2026 04:17:06 +0530 Subject: [PATCH 1/2] fix(workflows): drop the bundled speckit workflow's inert scope input The bundled workflow declared a required-choice scope input that no step referenced. All four steps pass {{ inputs.spec }}, so every choice behaved identically. The value was enum-validated and then discarded, which is worse than being ignored outright: -i scope=bogus errors while -i scope=backend-only is accepted, so the rejection of an invalid value is evidence to the user that the flag does something. Propagating scope instead would need a contract that does not exist -- the steps take a single args string, so a scope could only be appended as prose to the user's own description and left to the agent to interpret. That is a feature with a design question attached, not a bug fix, so this removes the selector and leaves the door open for a real one. workflows/README.md demonstrated multiple inputs using this exact input against the bundled workflow, so that example moves to a declared one. Every declared input is now referenced and every referenced input declared. Fixes #4384 --- workflows/README.md | 2 +- workflows/speckit/workflow.yml | 4 ---- 2 files changed, 1 insertion(+), 5 deletions(-) diff --git a/workflows/README.md b/workflows/README.md index d5569541a2..41a124a2a6 100644 --- a/workflows/README.md +++ b/workflows/README.md @@ -73,7 +73,7 @@ specify workflow run ./my-workflow.yml --input spec="Build a user authentication ```bash specify workflow run speckit \ --input spec="Build a user authentication system with OAuth support" \ - --input scope="backend-only" + --input integration="claude" ``` ## Step Types diff --git a/workflows/speckit/workflow.yml b/workflows/speckit/workflow.yml index 230675b327..a654e83823 100644 --- a/workflows/speckit/workflow.yml +++ b/workflows/speckit/workflow.yml @@ -35,10 +35,6 @@ inputs: type: string default: "auto" prompt: "Integration to use (e.g. claude, copilot, gemini; 'auto' uses the project's initialized integration)" - scope: - type: string - default: "full" - enum: ["full", "backend-only", "frontend-only"] steps: - id: specify From 6948a4231e0fdd07230b91feacaf9484326d0904 Mon Sep 17 00:00:00 2001 From: Yash-Chindam Date: Wed, 2 Sep 2026 04:44:58 +0530 Subject: [PATCH 2/2] docs(workflows): drop scope from the reference copy of the bundled workflow Addresses review feedback. docs/reference/workflows.md reproduces the shipped Full SDD Cycle workflow verbatim, so leaving its scope block in place would have made the documented definition disagree with the workflow this PR changes -- and would have kept advertising the inert selector. Checked the other scope references and left them alone deliberately: workflows/README.md's input-type section and workflows/PUBLISHING.md's authoring skeleton are generic examples of enum inputs, not copies of the bundled workflow, as is the enum row in workflows/ARCHITECTURE.md. --- docs/reference/workflows.md | 4 ---- 1 file changed, 4 deletions(-) diff --git a/docs/reference/workflows.md b/docs/reference/workflows.md index 3b838b7227..26cde5021c 100644 --- a/docs/reference/workflows.md +++ b/docs/reference/workflows.md @@ -415,10 +415,6 @@ inputs: type: string default: "copilot" prompt: "Integration to use (e.g. claude, copilot, gemini)" - scope: - type: string - default: "full" - enum: ["full", "backend-only", "frontend-only"] steps: - id: specify