name: speckit-orchestrator role: entrypoint description: 'Workflow orchestrator for Spec Driven Development. Coordinates skills and tracks progress.

speckit workflow, spec driven development, speckit commands.' version: 1.9.3 alwaysApply: false category: workflow-orchestration tags:

• speckit
• workflow
• orchestration
• planning
• specification dependencies:
• sanctum:git-workspace-review
• imbue:proof-of-work
• superpowers:brainstorming
• superpowers:writing-plans
• superpowers:executing-plans tools: [] modules:
• command-skill-matrix
• progress-tracking
• artifact-structure progressive_loading: true usage_patterns:
• workflow-coordination
• progress-tracking
• skill-loading complexity: intermediate model_hint: standard 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.

When NOT To Use

• Single-phase work (just specify, or just plan)
• Non-spec-driven projects

Core Workflow

Session Initialization

1. Verify Repository Context

   • Confirm working directory is a speckit-enabled project.
   • Check for .specify/ directory structure.
   • Validate required scripts exist.

2. Load Persistent State ("presence")

   • Read .specify/memory/constitution.md for constraints/principles.
   • Load current spec.md / plan.md / tasks.md context if present.

3. Load Command Dependencies

   • Match current command to required skills.
   • Load complementary superpowers skills.

4. Initialize Progress Tracking

   • Create TodoWrite items for workflow phases.
   • Track completion status.

Command-Skill Matrix

Quick reference for command-to-skill mappings:

For detailed patterns: See modules/command-skill-matrix.md for complete mappings and loading rules.

See modules/writing-plans-extensions.md for plan authoring patterns.

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.