Skip to content

feat(extensions): add pipeline extension for end-to-end SDD workflow#1977

Closed
RchrdHndrcks wants to merge 1 commit intogithub:mainfrom
RchrdHndrcks:feat/pipeline-extension
Closed

feat(extensions): add pipeline extension for end-to-end SDD workflow#1977
RchrdHndrcks wants to merge 1 commit intogithub:mainfrom
RchrdHndrcks:feat/pipeline-extension

Conversation

@RchrdHndrcks
Copy link

Summary

  • Adds a pipeline extension under extensions/pipeline/ that orchestrates the full SDD workflow: specifyclarifyplantasksanalyzeimplement
  • Auto-progresses between steps without returning control to the user, pausing only when genuine user input is needed
  • Follows the extension format (extension.yml manifest + commands/ directory) as requested in feat(commands): add pipeline command for end-to-end workflow auto-progression #1967 review feedback

Closes #1966
Supersedes #1967

Design Decisions

  • Extension, not a core command: Moved from templates/commands/ to extensions/pipeline/ per maintainer feedback
  • Declares dependencies: requires.commands lists all 6 core speckit commands it orchestrates
  • Single command: speckit.pipeline.run (alias: speckit.pipeline) — keeps the extension minimal and focused

Test plan

  • Run /speckit.pipeline.run <feature description> and verify it progresses through all 6 steps automatically
  • Verify it pauses during /speckit.clarify for user input and resumes after
  • Verify it pauses when /speckit.analyze finds CRITICAL issues
  • Verify it stops and reports errors when a step fails
  • Test with empty $ARGUMENTS — should ask for feature description

AI 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

Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.yml manifest defining the pipeline extension and its command entrypoint.
  • Added extensions/pipeline/commands/pipeline.md command template to auto-run specify → clarify → plan → tasks → analyze → implement with 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.

Comment on lines +22 to +29
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

Copy link

Copilot AI Mar 26, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copilot uses AI. Check for mistakes.
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>
@RchrdHndrcks RchrdHndrcks force-pushed the feat/pipeline-extension branch from 616555c to de7d9db Compare March 26, 2026 01:46
@RchrdHndrcks RchrdHndrcks deleted the feat/pipeline-extension branch March 26, 2026 01:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

feat: Add pipeline command for automated end-to-end workflow execution

2 participants