feat(extensions): add pipeline extension for end-to-end SDD workflow#1977
feat(extensions): add pipeline extension for end-to-end SDD workflow#1977RchrdHndrcks wants to merge 1 commit intogithub:mainfrom
Conversation
There was a problem hiding this comment.
Pull request overview
Adds a new pipeline extension intended to orchestrate the full Spec Kit SDD workflow end-to-end via a single command, aligning with the extension system’s manifest + commands directory structure.
Changes:
- Added
extensions/pipeline/extension.ymlmanifest defining the pipeline extension and its command entrypoint. - Added
extensions/pipeline/commands/pipeline.mdcommand template to auto-runspecify → clarify → plan → tasks → analyze → implementwith minimal pausing.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.
| File | Description |
|---|---|
| extensions/pipeline/extension.yml | Declares the new pipeline extension metadata and the speckit.pipeline.run command (plus alias). |
| extensions/pipeline/commands/pipeline.md | Command instructions for sequential, mostly hands-free orchestration of the 6-step workflow. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| provides: | ||
| commands: | ||
| - name: speckit.pipeline.run | ||
| file: commands/pipeline.md | ||
| description: Run the full speckit workflow end-to-end (specify → clarify → plan → tasks → analyze → implement) with automatic progression between steps. | ||
| aliases: | ||
| - speckit.pipeline | ||
|
|
There was a problem hiding this comment.
As added, this extension is not installable via the default extension catalogs and it’s not bundled into the CLI wheel’s core_pack assets. Unless users manually clone the repo and use specify extension add --dev, they won’t be able to consume it. If the intent is for this to be a usable, shipped extension (and to close #1966), it likely needs a published ZIP artifact (containing extension.yml at the ZIP root) and a catalog entry (core extensions/catalog.json or community catalog.community.json) pointing at that download URL.
Moves the pipeline command from templates/commands/ to extensions/ as requested in PR github#1967 review. Provides automatic progression through specify → clarify → plan → tasks → analyze → implement. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
616555c to
de7d9db
Compare
Summary
extensions/pipeline/that orchestrates the full SDD workflow:specify→clarify→plan→tasks→analyze→implementextension.ymlmanifest +commands/directory) as requested in feat(commands): add pipeline command for end-to-end workflow auto-progression #1967 review feedbackCloses #1966
Supersedes #1967
Design Decisions
templates/commands/toextensions/pipeline/per maintainer feedbackrequires.commandslists all 6 core speckit commands it orchestratesspeckit.pipeline.run(alias:speckit.pipeline) — keeps the extension minimal and focusedTest plan
/speckit.pipeline.run <feature description>and verify it progresses through all 6 steps automatically/speckit.clarifyfor user input and resumes after/speckit.analyzefinds CRITICAL issues$ARGUMENTS— should ask for feature descriptionAI Disclosure
This PR was authored with assistance from Claude Code (Claude Opus 4.6). The concept and workflow design are human-directed. The extension was written by Claude and reviewed by the contributor.
🤖 Generated with Claude Code