Nm Spec Kit Speckit Orchestrator

Workflow orchestrator for Spec Driven Development. Coordinates skills and tracks progress. speckit workflow, spec driven development, speckit commands.

Security Scan

The skill's declared purpose (orchestrating a spec-driven workflow) matches its instructions and requirements; it is an instruction-only orchestrator that reads and coordinates repository artifacts and other 'night-market' skills but does not request credentials or install code.

Purpose & Capability

The name/description (Speckit Orchestrator for Spec Driven Development) aligns with the actual content: verifying repo context, loading spec/plan/tasks artifacts, coordinating complementary skills, and tracking progress. The declared config-path dependencies point to other night-market skills and are consistent with an orchestrator that coordinates skill loading.

Instruction Scope

Runtime instructions explicitly read repository files (.specify/memory/constitution.md, spec.md, plan.md, tasks.md), generate and update artifacts, and coordinate other skills. This is appropriate for an orchestrator, but the 'implement' phase states it will 'execute tasks in dependency order'—that could imply running build/test/deploy commands (side-effects). Users should review tasks.md and the executing-plans skill before allowing implementation to run autonomously.

Install Mechanism

No install spec, no downloads, and no code files to write or execute. Instruction-only skills present the lowest install risk; nothing is fetched or installed by the skill itself.

Credentials

The skill requests no environment variables or credentials. It does declare several config paths under the night-market namespace (e.g., night-market.superpowers:*), which are coherent for an orchestrator but should be validated to ensure they map to expected local skill configs and not to unrelated or privileged configuration stores.

Persistence & Privilege

always:false and default autonomous invocation are set. The skill does coordinate state persistence in repository artifacts (frontmatter, TodoWrite items) which is expected. It does not request elevated platform-wide privileges or modify other skills' configs beyond coordinating their loading.

Assessment

This skill appears coherent with its stated purpose. Before installing or allowing it to run, review the repository's .specify/ artifacts (especially tasks.md and any scripts referenced) and verify the referenced night-market skills (brainstorming, writing-plans, executing-plans) are trusted. If you plan to use the /speckit-implement command, inspect tasks.md for any shell/command execution and, if possible, run implementation steps manually or in a sandbox first. Confirm the meaning and location of the declared config paths so they don't point to unexpected or sensitive config stores.

Night Market Skill — ported from claude-night-market/spec-kit. For the full experience with agents, hooks, and commands, install the Claude Code plugin.

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 + 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:

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.

Troubleshooting

Common Issues

Command not found Ensure all dependencies are installed and in PATH

Permission errors Check file permissions and run with appropriate privileges

Unexpected behavior Enable verbose logging with --verbose flag