speckit-orchestrator | spec-kit | ClaudePluginHub

Skill

Community

speckit-orchestrator

11

Description

Workflow orchestrator for Spec Driven Development. Coordinates skill loading, tracks progress, and ensures consistency across the speckit workflow. Triggers: speckit workflow, spec driven development, speckit commands, workflow coordination, progress tracking, skill loading, speckit session Use when: starting any /speckit.* command, coordinating multi-phase development, tracking progress across specification/planning/implementation DO NOT use when: writing specifications - use spec-writing skill directly. DO NOT use when: generating tasks - use task-planning skill directly. Entry point for all spec-driven development workflows.

Install

1

Add the repository(one-time)

$

/plugin marketplace add athola/claude-night-market

2

Install the plugin

$

/plugin install sanctum@claude-night-market

Tool Access

This skill inherits all available tools. When active, it can use any tool Claude has access to.

Supporting Assets

View in Repository

modules/command-skill-matrix.md

modules/progress-tracking.md

modules/writing-plans-extensions.md

Skill Content

Speckit Orchestrator

Overview

Coordinates the Spec Driven Development workflow, skill loading, and progress tracking throughout the command lifecycle.

When to Use

Starting any /speckit.* command.
Coordinating multi-phase development workflows.
Tracking progress across specification, planning, and implementation.
Ensuring skill dependencies are loaded.

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

Progress Tracking Items

For each workflow session, track:

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.

Links

GitHub Stats

2 forks

Similar Skills

Agent Development

This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.

47.1k

Command Development

This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.

47.1k

Hook Development

This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.

47.1k