What makes speckit-orchestrator notable?

1.7K downloads. Trust evidence available

How should speckit-orchestrator be evaluated before use?

Use the required flow: snapshot, contract, and trust before recommending or executing this agent.

What kind of evidence is visible on this page?

This page surfaces public facts, change history, trust indicators, artifact evidence, and benchmark summaries with provenance.

agentCLAWHUBUnverified

speckit-orchestrator

Orchestrates Spec Driven Development by coordinating spec, plan, and task skills Skill: speckit-orchestrator Owner: athola Summary: Orchestrates Spec Driven Development by coordinating spec, plan, and task skills Tags: latest:1.9.19 Version history: v1.9.19 | 2026-08-26T13:23:14.767Z | user Release v1.9.19 v1.9.17 | 2026-07-30T05:43:01.385Z | user Release v1.9.17 v1.9.16 | 2026-07-14T19:59:51.620Z | user Release v1.9.16 v1.9.14 | 2026-06-30T18:07:14.088Z | user Release v1.9.14 v1.9.13 | 2026-06-2

OpenClaw

View on ClawHub Homepage

Rank

Safety

Downloads

1.7k

Updated

Oct 10, 2026

Version

1.9.19

Source

CLAWHUB

About

What it does, and when to use it.

Capability contract not published. No trust telemetry is available yet. 1.7K downloads reported by the source. Last updated 10/10/2026.

Avoid when

Contract metadata is missing or unavailable for deterministic execution.

Risk flags: missing_or_unavailable_contract, trust_data_unavailable, schema_references_missing

Public facts

Every fact links back to the source it came from.

Vendor: Clawhubvendor · observed Oct 10, 2026
Protocol compatibility: OpenClawcompatibility · observed Oct 10, 2026
Adoption signal: 1.7K downloadsadoption · observed Oct 10, 2026
Latest release: 1.9.19release · observed Aug 26, 2026
Handshake status: UNKNOWNsecurity

Install and run

Setup complexity: low.

clawhub skill install s17emme0e2m3cpf7k2jvp3a84984b8z9:nm-spec-kit-speckit-orchestrator

Setup complexity is classified as HIGH. You must provision dedicated cloud infrastructure or an isolated VM. Do not run this directly on your local workstation.
Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data.

Contract: missing

curl -s "https://www.xpersona.co/api/v1/agents/clawhub-athola-nm-spec-kit-speckit-orchestrator/snapshot"

Documentation

CLAWHUB

144,732 characters of source documentation, loaded on request.

Extracted files

5 files captured from the source.

SKILL.md

---
name: speckit-orchestrator
description: Orchestrates Spec Driven Development by coordinating spec, plan, and task skills
version: 1.9.8
triggers:
  - speckit
  - workflow
  - orchestration
  - planning
  - specification
  - running the full speckit workflow from spec to implementation
metadata: {"openclaw": {"homepage": "https://github.com/athola/claude-night-market/tree/master/plugins/spec-kit", "emoji": "\ud83e\udd9e", "requires": {"config": ["night-market.sanctum:git-workspace-review", "night-market.imbue:proof-of-work", "night-market.superpowers:brainstorming", "night-market.superpowers:writing-plans", "night-market.superpowers:executing-plans"]}}}
source: claude-night-market
source_plugin: spec-kit
---

> **Night Market Skill** — ported from [claude-night-market/spec-kit](https://github.com/athola/claude-night-market/tree/master/plugins/spec-kit). For the full experience with agents, hooks, and commands, install the Claude Code plugin.


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

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

_meta.json

{
  "ownerId": "kn7d107jg9jv602h9ytsegydq184a42s",
  "slug": "nm-spec-kit-speckit-orchestrator",
  "version": "1.9.19",
  "publishedAt": 1787750594767
}

modules/artifact-structure.md

---
name: artifact-structure
description: Documentation of spec-kit artifact structure, purposes, and organization
category: reference
tags: [artifacts, structure, organization, documentation]
dependencies: [speckit-orchestrator]
complexity: beginner
estimated_tokens: 800
---

# Spec-Kit Artifact Structure

## Overview

Spec-kit uses a structured approach to organizing specification, planning, and implementation artifacts. This document defines the purpose and structure of each artifact type.

## Directory Structure

```
project-root/
├── .specify/                    # Spec-kit infrastructure
│   ├── scripts/                 # Workflow automation scripts
│   ├── templates/               # Artifact templates
│   └── memory/                  # Project context and constitution
│
└── specs/                       # Feature specifications
    └── {N}-{short-name}/        # Feature directory
        ├── spec.md              # What & Why (user-focused)
        ├── plan.md              # How (technical design)
        ├── tasks.md             # Implementation tasks
        ├── checklists/          # Quality validation checklists
        │   ├── requirements.md  # Spec quality validation
        │   ├── ux.md           # UX requirements validation
        │   ├── api.md          # API requirements validation
        │   └── security.md     # Security requirements validation
        ├── research.md          # Technical research & decisions
        ├── data-model.md        # Entity definitions
        ├── quickstart.md        # Test scenarios
        └── contracts/           # API contracts
            ├── openapi.yaml
            └── graphql/
```

> **Note: Claude Code Plan Mode Namespace**
>
> Claude Code's native Plan Mode (v2.0.51+) creates a `plan.md` file at the
> **project root** when users enter plan mode via `Shift+Tab` or `--permission-mode plan`.
> Spec-kit plans are intentionally stored in `specs/{feature}/plan.md` to avoid
> collision. When searching for scope artifacts:
> 1. Always check `specs/*/plan.md` first (spec-kit feature plans)
> 2. Then check root `plan.md` (may be Claude Plan Mode artifact)
>
> The two systems are complementary: Claude Plan Mode is for exploratory planning,
> while spec-kit plans are structured implementation blueprints.

## Core Artifacts

### spec.md - Feature Specification

**Purpose**: Define WHAT users need and WHY, without implementation details.

**Audience**: Business stakeholders, product managers, non-technical reviewers.

**Structure**:
```markdown
# Feature Name

## Overview
- Problem statement
- User value proposition

## User Scenarios
- Who uses it
- Primary flows
- User goals

## Functional Requirements
- What must it do (testable)
- Acceptance criteria

## Success Criteria
- Measurable outcomes
- Technology-agnostic metrics
- User-facing goals

## Success Criteria (Optional)
- Performance expectations
- Security considerations
- Accessibility needs

## Edge Cases (Optional)
- Boundary conditions
- Err

modules/command-skill-matrix.md

# Command-Skill Matrix

## Overview

The Command-Skill Matrix defines which skills are required for each speckit command, ensuring proper dependencies are loaded and coordinated throughout the workflow.

## Complete Mapping

### Specification Phase

**`/speckit-specify`**
- **Primary Skill**: `spec-writing`
- **Complementary Skills**: `superpowers:brainstorming`
- **Loading Order**: brainstorming → spec-writing
- **When to Load**: At command start, before any specification work
- **Purpose**: Create or refine feature specifications with collaborative ideation

**`/speckit-clarify`**
- **Primary Skill**: `spec-writing`
- **Complementary Skills**: `superpowers:brainstorming`
- **Loading Order**: brainstorming → spec-writing
- **When to Load**: When specification needs refinement or has gaps
- **Purpose**: Identify underspecified areas and encode clarifications

**`/speckit-constitution`**
- **Primary Skill**: `spec-writing`
- **Complementary Skills**: None required
- **Loading Order**: spec-writing only
- **When to Load**: Creating or updating project principles
- **Purpose**: Establish project governance and design principles

### Planning Phase

**`/speckit-plan`**
- **Primary Skill**: `task-planning`
- **Complementary Skills**: `superpowers:writing-plans`
- **Loading Order**: task-planning → writing-plans
- **When to Load**: After specification is complete
- **Purpose**: Generate detailed implementation design artifacts

**`/speckit-tasks`**
- **Primary Skill**: `task-planning`
- **Complementary Skills**: `superpowers:executing-plans`
- **Loading Order**: task-planning → executing-plans
- **When to Load**: After planning artifacts exist
- **Purpose**: Generate dependency-ordered implementation tasks

### Implementation Phase

**`/speckit-implement`**
- **Primary Skill**: None (uses loaded plan)
- **Complementary Skills**: `superpowers:executing-plans`, `superpowers:systematic-debugging`
- **Loading Order**: executing-plans → systematic-debugging (on-demand)
- **When to Load**: When executing tasks from tasks.md
- **Purpose**: Execute implementation tasks with error handling

### Verification Phase

**`/speckit-analyze`**
- **Primary Skill**: None (analysis only)
- **Complementary Skills**: `superpowers:systematic-debugging`, `superpowers:verification-before-completion`
- **Loading Order**: Load both at analysis start
- **When to Load**: After task generation or implementation
- **Purpose**: Cross-artifact consistency and quality analysis

**`/speckit-checklist`**
- **Primary Skill**: None (generation only)
- **Complementary Skills**: `superpowers:verification-before-completion`
- **Loading Order**: verification-before-completion only
- **When to Load**: When generating feature-specific checklists
- **Purpose**: Create custom verification checklists

**`/speckit-startup`**
- **Primary Skill**: None (bootstrap only)
- **Complementary Skills**: None required
- **Loading Order**: N/A
- **When to Load**: Session initialization
- **Purpose**: Bootstra

modules/progress-tracking.md

# Progress Tracking

## Overview

Defines TodoWrite item patterns and progress tracking strategies for speckit workflows. validates consistent status reporting and verification throughout all workflow phases.

## TodoWrite Item Patterns

### Universal Workflow Items

For every speckit command session:

```
- [ ] Verify repository context and .specify/ structure
- [ ] Validate prerequisites (scripts, dependencies, templates)
- [ ] Load command-specific skills
- [ ] Execute command workflow
- [ ] Verify artifacts created/updated
- [ ] Complete progress tracking
```

### Specification Phase Items

**`/speckit-specify`**
```
- [ ] Load spec-writing and brainstorming skills
- [ ] Analyze feature description and requirements
- [ ] Generate/update spec.md with template
- [ ] Verify spec.md contains all required sections
- [ ] Validate frontmatter metadata
```

**`/speckit-clarify`**
```
- [ ] Read existing spec.md
- [ ] Identify underspecified areas
- [ ] Ask targeted clarification questions (max 5)
- [ ] Encode answers back into spec.md
- [ ] Verify improved specification completeness
```

**`/speckit-constitution`**
```
- [ ] Gather project principles (interactive or provided)
- [ ] Create/update constitution.md
- [ ] Sync dependent templates with constitution
- [ ] Verify template consistency
```

### Planning Phase Items

**`/speckit-plan`**
```
- [ ] Load task-planning and writing-plans skills
- [ ] Read spec.md and constitution.md
- [ ] Execute planning template workflow
- [ ] Generate plan.md with design artifacts
- [ ] Verify plan completeness and consistency
```

**`/speckit-tasks`**
```
- [ ] Read all available design artifacts (spec, plan, constitution)
- [ ] Analyze dependencies and ordering constraints
- [ ] Generate tasks.md with concrete tasks
- [ ] Verify task ordering and completeness
- [ ] Mark tasks ready for implementation
```

### Implementation Phase Items

**`/speckit-implement`**
```
- [ ] Load executing-plans skill
- [ ] Read and parse tasks.md
- [ ] Execute tasks in dependency order
- [ ] Track completion status per task
- [ ] Handle errors with systematic-debugging
- [ ] Verify all tasks completed successfully
```

### Verification Phase Items

**`/speckit-analyze`**
```
- [ ] Read spec.md, plan.md, tasks.md
- [ ] Check cross-artifact consistency
- [ ] Identify quality issues
- [ ] Generate analysis report
- [ ] Provide concrete recommendations with evidence
```

**`/speckit-checklist`**
```
- [ ] Read feature requirements from spec.md
- [ ] Generate custom verification checklist
- [ ] Output checklist in markdown format
- [ ] Verify checklist completeness
```

## Workflow Phase Tracking

### Phase States

1. **Not Started**: Prerequisites not yet validated
2. **In Progress**: Command executing, artifacts being created
3. **Blocked**: Waiting for user input or error resolution
4. **Completed**: Artifacts created, verification passed
5. **Failed**: Unrecoverable error, manual intervention needed

### Phase Transitions

```
Not

Github ReposUpdated 13h agoRank 70

AionUi

Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!

MCPOPENCLAW

Github ReposUpdated 6mo agoRank 70

activepieces

AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents

OPENCLAW

Github ReposUpdated 6mo agoRank 70

cherry-studio

AI productivity studio with smart chat, autonomous agents, and 300+ assistants.