Skip to content
cccskills
FreePublished on GitHub

speckit-orchestrator

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

The English summary is being prepared. Showing the original description.

Run score Not tested

See how to install

Files included (5)

  • SKILL.md3.9 KB
  • modules/artifact-structure.md7.4 KB
  • modules/command-skill-matrix.md4.2 KB
  • modules/progress-tracking.md5.6 KB
  • modules/writing-plans-extensions.md8.6 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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

  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:

CommandPrimary SkillComplementary Skills
/speckit-specifyspec-writingbrainstorming
/speckit-clarifyspec-writingbrainstorming
/speckit-plantask-planningwriting-plans
/speckit-taskstask-planningexecuting-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.

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.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Shapes turns action-first: action leads, steps numbered, state restated. Use for ADHD-friendly output. Do not use to trim tokens; use response-compression.

The English summary is being prepared. Showing the original description.

athola/claude-night-market343Updated Oct 24, 2026

Inverts burden of proof for code additions. Use when reviewing PRs, planning refactors, or running unbloat to challenge every addition's necessity.

The English summary is being prepared. Showing the original description.

athola/claude-night-market343Updated Oct 24, 2026

Tracks per-agent token usage and flags waste in parallel dispatch. Use when evaluating parallel agent efficiency or after a multi-agent run.

The English summary is being prepared. Showing the original description.

athola/claude-night-market343Updated Oct 24, 2026

Coordinates Claude agent teams via filesystem protocol. Use when orchestrating parallel agents with task dependencies. Do not use for single-agent tasks.

The English summary is being prepared. Showing the original description.

athola/claude-night-market343Updated Oct 24, 2026

Evaluates API surface design, consistency, and exemplar alignment. Use when reviewing public API changes or before releasing a new API surface.

The English summary is being prepared. Showing the original description.

athola/claude-night-market343Updated Oct 24, 2026

Selects architecture paradigm via research before scaffolding. Use when architecture is undecided and the choice needs justification and documentation.

The English summary is being prepared. Showing the original description.

athola/claude-night-market343Updated Oct 24, 2026

See all skills by athola

Report a problem with this skill