speckit-orchestrator
Workflow orchestrator for Spec Driven Development. Coordinates skills and tracks progress.Triggers: speckit workflow, spec driven development, speckit commandsUse when: starting any /speckit-* command or coordinating multi-phase development
When & Why to Use This Skill
Speckit Orchestrator is a powerful workflow engine designed for Spec Driven Development (SDD). It serves as the central nervous system for AI-driven coding tasks, coordinating specialized skills, managing dependencies, and tracking progress across the entire development lifecycle—from initial specification to final implementation. By maintaining a persistent 'agent model' and repository context, it ensures that complex, multi-phase engineering tasks are executed with high consistency and structural integrity.
Use Cases
- Multi-Phase Software Development: Seamlessly orchestrating the transition between requirement gathering (spec-writing), technical design (writing-plans), and execution (executing-plans).
- Standardized Engineering Workflows: Enforcing project-specific constraints and architectural principles defined in a 'constitution' file across all agent interactions.
- Stateful Progress Tracking: Maintaining a real-time 'world model' of the repository using artifacts like spec.md and tasks.md to ensure the agent never loses context during long-running tasks.
- Dynamic Skill Loading: Optimizing agent performance by automatically loading only the necessary tools and 'superpowers' required for specific commands like /speckit-plan or /speckit-implement.
- Automated Repository Verification: Ensuring the development environment is correctly configured and that all prerequisites are met before initiating complex code modifications.
| name | speckit-orchestrator |
|---|---|
| description | | |
| Triggers | speckit workflow, spec driven development, speckit commands |
| Use when | starting any /speckit-* command or coordinating multi-phase development |
| category | workflow-orchestration |
| tags | [speckit, workflow, orchestration, planning, specification] |
| - spec-kit | shared |
| - sanctum | git-workspace-review |
| - imbue | evidence-logging |
| - superpowers | executing-plans |
| tools | [] |
| progressive_loading | true |
| complexity | intermediate |
| estimated_tokens | 1500 |
Table of Contents
- Overview
- Persistent Presence Lens
- When to Use
- Core Workflow
- Session Initialization
- Command-Skill Matrix
- Progress Tracking Items
- Exit Criteria
- Related Skills
Speckit Orchestrator
Overview
Coordinates the Spec Driven Development workflow, skill loading, and progress tracking throughout the command lifecycle.
Persistent Presence Lens
Treat SDD as a minimal, testable “self-modeling” loop:
- World model: repo + speckit artifacts (
spec.md,plan.md,tasks.md) - Agent model: loaded skills/plugins + constraints (especially
.specify/memory/constitution.md) + progress state
This mirrors patterns from open-ended embodied agents (e.g., Voyager/MineDojo) that compound capability via a curriculum (tasks.md) and a skill library (reusable plugin skills + superpowers methodology skills).
When to Use
- Starting any
/speckit-*command. - Coordinating multi-phase development workflows.
- Tracking progress across specification, planning, and implementation.
- Ensuring skill dependencies are loaded.
Core Workflow
Session Initialization
Verify Repository Context
- Confirm working directory is a speckit-enabled project.
- Check for
.specify/directory structure. - Validate required scripts exist.
Load Persistent State ("presence")
- Read
.specify/memory/constitution.mdfor constraints/principles. - Load current
spec.md/plan.md/tasks.mdcontext if present.
- Read
Load Command Dependencies
- Match current command to required skills.
- Load complementary superpowers skills.
Initialize Progress Tracking
- Create TodoWrite items for workflow phases.
- Track completion status.
Command-Skill Matrix
Quick reference for command-to-skill mappings:
| Command | Primary Skill | Complementary Skills |
|---|---|---|
/speckit-specify |
spec-writing | brainstorming |
/speckit-clarify |
spec-writing | brainstorming |
/speckit-plan |
task-planning | writing-plans |
/speckit-tasks |
task-planning | executing-plans |
/speckit-implement |
- | executing-plans, systematic-debugging |
/speckit-analyze |
- | systematic-debugging, verification |
/speckit-checklist |
- | verification-before-completion |
For detailed patterns: See modules/command-skill-matrix.md for complete mappings and loading rules.
Progress Tracking Items
For each workflow session, track:
- Repository context verified.
- Prerequisites validated.
- Command-specific skills loaded.
- Artifacts created/updated.
- Verification completed.
For detailed patterns: See modules/progress-tracking.md for TodoWrite patterns and metrics.
Exit Criteria
- Active command completed successfully.
- All required artifacts exist and are valid.
- Progress tracking reflects current state.
- No unresolved blockers.
Related Skills
spec-writing: Specification creation and refinement.task-planning: Task generation and planning.superpowers:brainstorming: Idea refinement.superpowers:writing-plans: Implementation planning.superpowers:executing-plans: Task execution.
Troubleshooting
Common Issues
Command not found Ensure all dependencies are installed and in PATH
Permission errors Check file permissions and run with appropriate privileges
Unexpected behavior
Enable verbose logging with --verbose flag