Claude-night-market speckit-orchestrator
'Workflow orchestrator for Spec Driven Development. Coordinates skills
install
source · Clone the upstream repo
git clone https://github.com/athola/claude-night-market
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/athola/claude-night-market "$T" && mkdir -p ~/.claude/skills && cp -r "$T/plugins/spec-kit/skills/speckit-orchestrator" ~/.claude/skills/athola-claude-night-market-speckit-orchestrator && rm -rf "$T"
manifest:
plugins/spec-kit/skills/speckit-orchestrator/SKILL.mdsource content
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
) + progress state.specify/memory/constitution.md
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
command./speckit-* - 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
directory structure..specify/ - Validate required scripts exist.
-
Load Persistent State ("presence")
- Read
for constraints/principles..specify/memory/constitution.md - Load current
/spec.md
/plan.md
context if present.tasks.md
- 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 |
|---|---|---|
| spec-writing | brainstorming |
| spec-writing | brainstorming |
| task-planning | writing-plans |
| task-planning | executing-plans |
| - | executing-plans, systematic-debugging |
| - | systematic-debugging, verification |
| - | 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
: Specification creation and refinement.spec-writing
: Task generation and planning.task-planning
: Idea refinement.superpowers:brainstorming
: Implementation planning.superpowers:writing-plans
: Task execution.superpowers:executing-plans