speckit-orchestrator
npx machina-cli add skill athola/claude-night-market/speckit-orchestrator --openclawTable 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
-
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.
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.
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
Source
git clone https://github.com/athola/claude-night-market/blob/master/plugins/spec-kit/skills/speckit-orchestrator/SKILL.mdView on GitHub Overview
The Speckit Orchestrator coordinates the Spec Driven Development workflow, handling skill loading and progress tracking across the command lifecycle. It ensures dependencies are loaded and artifacts stay aligned as work progresses.
How This Skill Works
On session start, it validates the repository context and loads the persistent state from .specify and the spec/plan/tasks context. It then matches the current command to required skills, loads complementary superpowers, and initializes TodoWrite-based progress tracking to monitor workflow phases.
When to Use It
- Starting any /speckit-* command.
- Coordinating multi-phase development workflows.
- Tracking progress across specification, planning, and implementation.
- Ensuring skill dependencies are loaded before execution.
- Running a full spec-driven cycle from spec through tasks to implementation.
Quick Start
- Step 1: Verify Repository Context and presence of .specify/.
- Step 2: Load persistent state and current spec/plan/tasks.
- Step 3: Load command dependencies and initialize progress tracking.
Best Practices
- Verify repository context before orchestration.
- Validate the presence of .specify/memory/constitution.md.
- Load required skills and complementary superpowers for the command.
- Use TodoWrite items to track each workflow phase.
- Regularly review exit criteria and blockers to adjust flow.
Example Use Cases
- Example 1: Run /speckit-specify to draft spec.md, then /speckit-plan to generate plan.md.
- Example 2: Run /speckit-plan and /speckit-tasks in sequence to prepare implementation.
- Example 3: Load dependencies for a command like /speckit-implement which relies on executing-plans and systematic-debugging.
- Example 4: Initialize progress tracking for a session and create TodoWrite items for workflow phases.
- Example 5: Verify repository context and presence of .specify before starting speckit-* commands.