Execute a single swarm task in an isolated git worktree. Receive a fully-specified recipe from the main context — a scenario recipe plus an implementation contract — then run Skill(scenario) followed by Skill(implement) and report JSON status. Make no design decisions and do not expand scope. Invoked exclusively by…
Record human approval of a workflow's direction (the intake + its acceptance criteria + the CO-A evidence). The Direction Approval Guard hook blocks Claude from ever writing approval tokens; this command is the only sanctioned path. Must be user-invoked. Replaces the retired /approve-spec gate (D3/CO-E gate-collapse)…
Detect and repair baseline drift — missing or invalid .claude/workflows.jsonl, schema violations, four-way Article IV / §18 mirror drift, and (advisory) shipped-tooling files placed outside .claude/ against the convention codified at seed.md §3. Interactive: presents each detected violation via AskUserQuestion and…
Configure the baseline for this specific project. Invokes the scout skill, then claude-automation-recommender, populates .claude/project.json, pre-creates lazy directories, re-renders swarm-worker.md from its template with any stack-specific skills appended, appends a §16 addendum to docs/init/seed.md, runs…
Runs after a tool call finishes for Write, Edit, MultiEdit and Bash tool calls, executing lint_runner.mjs, test_runner.mjs and phase_timer.mjs via node (4 commands). From friedbotstudio/baseline.
11 5d agoA
tokens not measured
copy · 47%Apache-2.0
Runs when the agent finishes a response, executing memory_stop.mjs, harness_continuation.mjs and notify.mjs via node (3 commands). From friedbotstudio/baseline.
11 5d agoA
tokens not measured
copy · 44%Apache-2.0
Runs when the agent sends a notification for permission_prompt and idle_prompt tool calls, executing notify.mjs via node (2 commands). From friedbotstudio/baseline.
Phase 10.5 — move the slug's workflow artifacts (intake, scout, research, spec, approvals, swarm state, security reports, rendered diagrams) to docs/archive/ / /. Runs before /commit so the committed tree is clean of work-in-flight files. workflow.json stays live and gets archived as the first step of /commit.
Drift check between the baseline implementation on disk and the claims in docs/init/seed.md + cross-references in CLAUDE.md, README.md, and the rendered docs site. Verifies hook/agent/skill/command names + counts, settings.json wiring, project.json key presence, .mcp.json servers, vendored license files, and helper…
Draft a Business Requirements Document (BRD) for cross-functional or stakeholder-heavy work that needs more structure than an intake. Use after /intake when the request spans multiple systems/teams, carries regulatory weight, or needs formal sign-off. Output lives at docs/brd/ .md.
Workflow track for tasks that need no TDD — documentation edits, governance count bumps, vendored-skill content updates, configuration tweaks, formatting, typo fixes, dependency bumps where no project code changes. Skips /scenario and /implement (no failing test to drive) and runs the work directly. archive…
Analyze a codebase and recommend Claude Code automations (hooks, subagents, skills, plugins, MCP servers). Use when user asks for automation recommendations, wants to optimize their Claude Code setup, mentions improving Claude Code workflows, asks how to first set up Claude Code for a project, or wants to know what…
Dev-only review of user-facing CLI interface copy in src/cli/tui/.js, src/cli/.js error paths, and bin/cli.js help/usage text. Surfaces three failure modes — copy/behavior mismatch, jargon, missing next-action — as a punch list the maintainer addresses before /grant-commit. Read-only; no writes to source.…
The primary tool for code-navigation questions in ANY language (frontend or backend) — walk the structural graph from an entry point (page, route, handler, command, main) down through imports to the IO boundary (network call, query, file read). Use this skill, in preference to the Explore agent or global grep…
MANDATORY skill for ALL code generation. Enforces top-down composition, consistent abstraction layers, and proper module hierarchy. Apply every time you write or modify code — in any language — no exceptions.