athola/speckit-orchestrator
plugins/spec-kit/skills/speckit-orchestrator/SKILL.md
Orchestrates Spec Driven Development by coordinating spec, plan, and task skills. Use when running the full speckit workflow from spec to implementation.
$ install --global
skillsauthnpx skillsauth add athola/claude-night-market speckit-orchestratorInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 30, 2026, 4:14 AM187.0s5 files scanned
SKILL.md
- name:
- speckit-orchestrator
- role:
- entrypoint
- description:
- Orchestrates Spec Driven Development by coordinating spec, plan, and task skills. Use when running the full speckit workflow from spec to implementation.
- alwaysApply:
- false
- category:
- workflow-orchestration
- - sanctum:
- git-workspace-review
- - imbue:
- proof-of-work
- - superpowers:
- executing-plans
- tools:
- []
- progressive_loading:
- true
- complexity:
- intermediate
- model_hint:
- standard
- estimated_tokens:
- 1500
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
.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.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.
Related Skills
athola/friction-detector
tools
VerifiedTrustedCommunity
Detect friction signals; graduate patterns into rules. Use for session retrospectives.
300SKILL.mdUpdated Apr 23, 2026
athola/validate-mr
testing
VerifiedTrustedCommunity
Use when you need a diff-derived test plan for an MR — reads the diff, groups changes by area, runs targeted verifications, and proves revert-tests are genuine guards, not dead assertions.
294SKILL.mdUpdated May 30, 2026
athola/palace-index-curator
development
VerifiedTrustedCommunity
Curate the web-capture index. Use when the capture backlog grows, captures sit unprocessed at seedling/pending, or to surface stored research during work.
294SKILL.mdUpdated May 30, 2026
athola/memory-clarity-probe
testing
VerifiedTrustedCommunity
Probe memory/summary clarity via dual anchor questions: task progress, info gaps. Use when verifying session state or summary before handoff or compression.
294SKILL.mdUpdated May 30, 2026