What is speckit-orchestrate?

A command workflow that turns a brief into a written specification, technical plan, task list, and implemented change.

It helps optionally refine a brief, create Spec Kit documents, implement the planned work, and summarize the resulting files and checks.

It gives a software change a defined sequence from requirements through implementation, so important decisions and work items are recorded.

How jmanhype/speckit configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to jmanhype/speckit. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/jmanhype/speckit/main/.claude/commands/speckit-orchestrate.md

Clone the repo

git clone --depth 1 https://github.com/jmanhype/speckit

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/commands/jmanhype/speckit/speckit-orchestrate/github.svg)](https://agentmods.dev/commands/jmanhype/speckit/speckit-orchestrate)

Your own site

<a href="https://agentmods.dev/commands/jmanhype/speckit/speckit-orchestrate"><img src="https://agentmods.dev/badge/commands/jmanhype/speckit/speckit-orchestrate/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/commands/jmanhype/speckit/speckit-orchestrate"><img src="https://agentmods.dev/badge/commands/jmanhype/speckit/speckit-orchestrate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 45 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 745 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00045	$0.00745
Opus 5.5	$0.00018	$0.00298
Sonnet 5.5	$0.00009	$0.00149
Haiku 4.5	$0.00005	$0.00075

Measured 1mo ago against content hash 6f9a0cb3f85e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

speckit-orchestrate scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/commands/speckit-orchestrate.md · 86 lines

How it starts

The opening of the file, as written. The whole thing — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Speckit Orchestrate (Basic)

Purpose

Guide the agent to (optionally) refine the brief via TCHES' metaprompt, then run Spec Kit's passes end-to-end via SlashCommand.

Objective

Turn "$ARGUMENTS" into an executed, spec-driven change:

(if --meta present and available) run TCHES' /create-meta-prompt
run the Spec Kit passes: specify → plan → tasks → implement
summarize artifacts, diffs, and verification status

Inputs

$ARGUMENTS = brief + optional flags:
- --meta Use TCHES metaprompt to refine the brief before starting
- --parallel Prefer parallel execution during implement where deps allow

Flow

1. Optional Meta-Prompting (if --meta flag present)

Check if /create-meta-prompt command exists
If exists and --meta flag present:
- Run: /create-meta-prompt $ARGUMENTS
- Use its outputs (users, outcomes, constraints) to enrich the spec phase
If not exists, skip and proceed to Specify

2. Specify (WHAT/WHY)

Run:
- /speckit.specify $ARGUMENTS
- (fallback if not found) /specify $ARGUMENTS
Keep tech decisions out of the spec

3. Plan (HOW)

Run:
- /speckit.plan Draft a technical plan aligned to the spec: architecture, data model, interfaces, testing, observability, performance budgets, risks.
- (fallback) /plan

4. Tasks (make it executable)

Run:
- /speckit.tasks
- (fallback) /tasks
Require small, verifiable tasks with dependencies, Definition of Done, and verification steps
Note: In this streamlined workflow, analyze phase is skipped. For consistency validation, use /speckit-workflow-v2 or run /speckit.analyze manually before implementation.

5. Implement (do the work)

Run:
- /speckit.implement
- (fallback) /implement
If --parallel present, request parallelization where dependencies allow

6. Report

Emit a concise summary:
- Phases executed
- Artifacts created/changed
- Outstanding TODOs
- Verification status

Notes

Read the full file on GitHub · 86 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

1mo ago First seen · 86 lines · 45 tokens per session scan A 6f9a0cb3f85e

Subscribe to this mod's changes

speckit-orchestrate is a command published in the GitHub repository jmanhype/speckit (26 stars, last pushed 7mo ago), licensed MIT. It adds 45 tokens to every session and 745 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-01.

Claude Code Planning Project management ai-assisted-development beads development-framework specification-driven-development

speckit: Command for Claude Code