Speckit Orchestrator Skill for Claude

Orchestrates Spec Driven Development by coordinating spec, plan, and task skills. Use when running the full speckit workflow from spec to implementation.

8k tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

324

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/athola/claude-night-market --skill speckit-orchestrator

The instruction itself

12 sections, as written by the author

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 and 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.md for constraints/principles.
Load current spec.md / plan.md / tasks.md context if present.

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-converge | - | executing-plans, verification-before-completion |

| /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.

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.

Other skills for the same job

different authors, same section of the catalogue

Skill Creator

by anthropics

vendor ×10

Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.

Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.

Replace with description of the skill and when Claude should use it.

35 tokens

Dispatching Parallel Agents

by ZhanlinCui

×5

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

This skill should be used when the user wants to "create a skill", "add a skill to plugin", "write a new skill", "improve skill description", "organize skill content", or needs guidance on skill structure, progressive disclosure, or skill development best practices for Claude Code plugins.

Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.

Use when creating new skills, editing existing skills, or verifying skills work before deployment

26k tokens scripts