speckit-orchestrator

## Table of Contents - [Overview](#overview) - [Persistent Presence Lens](#persistent-presence-lens) - [When to Use](#when-to-use) - [Core Workflow](#core-workflow) - [Session Initialization](#session-initialization) - [Command-Skill Matrix](#command-skill-matrix) - [Progress Tracking Items](#progress-tracking-items) - [Exit Criteria](#exit-criteria) - [Related Skills](#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 proje...