thewoolleyman

Get unstuck by showing what workflow steps come next or answering questions about what to do

Fast-track trivial changes through the implement-close workflow.

Convert BMAD stories to Beads issues with bidirectional tracking.

Execute the full TDD-enforced implementation workflow.

Reload context from a previous session.

Load codebase context into the current session.

Run the full local quality gate across all configured tools.

bmad-master agent

Detect specification-to-implementation gaps, then file a gap-tied work-item per gap with per-gap user consent. Use when the user wants detected gaps turned into tracked work. Mutating: it writes one record per consented gap.

Detect implementation-to-specification drift and hand each finding off to the propose-change operation with user consent. Use when the implementation has moved ahead of the spec and the spec must catch up. Mutating: it files proposed changes the user approves.

File an implementation-side work item directly from free-form user intent — a bug, a refactor, a tactical task. Use when the user wants something recorded in the work-items store that no gap or drift detection produced. Mutating: it writes a record after the…

Execute exactly one operator action id against the target repository — a dispatch action, a human valve or policy action, or a config action. Use when the user has selected an action id from the attention surface and wants it executed. Mutating: it drives…

Drive one work-item from a failing test to a passing implementation, verifying gap closure by re-running detection when the item is gap-tied. Use when the user asks to implement a specific work-item. Mutating: it edits code and closes the record.

Open or resume a durable plan, route scoped work to the spec side or to ledger children, and archive only after the disposition and completeness evidence gates pass. Use when the user starts, resumes, or closes a plan. Mutating: it writes plan state and…

Detect specification-to-implementation gaps mechanically via the Spec Reader and emit the current gap-id set. Use when the user asks which spec rules have no implementation, or as the detection step a capture operation composes. Pure read-and-emit — never…

Regroom an oversized or non-converging work-item into ready, dependency-layered slices. Use when an item keeps failing to converge or is too large to dispatch. Drafting is read-only; the maintainer owns the cut and nothing is filed until they approve it.

Thin compatibility pointer for the /overseer operator contract.

Watch caam-managed Claude Max account usage and rotate safely. Invoked as livespec-overseer:caam-anthropic-loop.

Watch caam-managed Claude Max account usage and rotate safely.

Watch caam-managed Claude Max account usage and rotate safely. Invoke as /livespec-overseer:caam-anthropic-loop.

Run the bounded livespec grooming drain pass. Invoked as livespec-overseer:grooming.

Run the bounded livespec grooming drain pass for the current repository.

Run the bounded livespec grooming drain pass for the current repository. Invoke as /livespec-overseer:grooming.

Run the bounded livespec foreman operator loop for the current repository.

Run a Kilroy pipeline for this repo.

Generate or regenerate the Kilroy pipeline DOT file from YAML config. Runs deterministic compilation, verifies correctness, and validates structure.

Build the Kilroy binary, verify CXDB is reachable on the central server via Tailscale, and verify all prerequisites for running Kilroy pipelines.

Check status of Kilroy runs, resume an interrupted run, or stop a running pipeline.

Query CXDB to show pipeline context status, detect stuck agents, error loops, and suggest fixes.

Land a completed Kilroy pipeline run — merge the worktree branch back into this repo, run smoke tests, and push.

Run the CXDB Graph UI holdout scenarios using Playwright MCP browser automation

Critique the CXDB Graph UI spec against its goals and invariants

Critique an existing livespec specification or a pending proposed change, surfacing ambiguities, contradictions, and missing rules as findings the user can act on. Invoked by /livespec:critique, "critique the livespec spec", or "find issues in the spec".

Run the doctor checks against a livespec spec tree — the static phase (structural failures) plus the LLM-driven objective and subjective phases — surfacing findings as JSON or as a per-finding user dialogue. Invoked by /livespec:doctor, "run livespec doctor",…

Explain what livespec does and route the user to the right sub-command (seed, propose-change, critique, revise, doctor, prune-history). Invoked by /livespec:help, "what can livespec do", or when the user asks for an overview of livespec capabilities.

Rank the next spec-side action (revise, propose-change, critique, prune-history, or none) over the current `<spec-target>/proposed_changes/` and `<spec-target>/history/` state, emitting structured JSON. Invoked by /livespec:next, "what should I work on next…

File a proposed change against an existing livespec specification, landing it under <spec-root>/proposed_changes/<topic>.md. Invoked by /livespec:propose-change, "propose a change to the spec", or when the user wants to record a spec amendment that the next…

Destructively prune old vNNN/ snapshots from <spec-root>/history/ to bound history size. Requires explicit user invocation (model-driven invocation is disabled). Invoked only via /livespec:prune-history or an explicit "prune the livespec history" request from…

Walk the user through accepting or rejecting pending proposed changes in <spec-root>/proposed_changes/, then snapshot the result as a new <spec-root>/history/vNNN/ revision. Covers every pending proposal by default, or ONE named proposal via --only-topic…

Author the initial natural-language specification for a new project, populating the chosen template's spec_root layout. Invoked by /livespec:seed, "seed a livespec spec", "set up a livespec", or when starting a brand-new spec in an empty SPECIFICATION/ tree.

Walk the user through accepting or rejecting pending proposed changes in <spec-root>/proposed_changes/, then snapshot the result as a new <spec-root>/history/vNNN/ revision. Covers every pending proposal by default, or ONE named proposal via --only-topic…

Critique an existing livespec specification or a pending proposed change, surfacing ambiguities, contradictions, and missing rules as findings the user can act on. Invoked by livespec:critique, "critique the livespec spec", or "find issues in the spec".

Run the doctor checks against a livespec spec tree — the static phase (structural failures) plus the LLM-driven objective and subjective phases — surfacing findings as JSON or as a per-finding user dialogue. Invoked by livespec:doctor, "run livespec doctor",…

Rank the next spec-side action (revise, propose-change, critique, prune-history, or none) over the current `<spec-target>/proposed_changes/` and `<spec-target>/history/` state, emitting structured JSON. Invoked by livespec:next, "what should I work on next on…

File a proposed change against an existing livespec specification, landing it under <spec-root>/proposed_changes/<topic>.md. Invoked by livespec:propose-change, "propose a change to the spec", or when the user wants to record a spec amendment that the next…

Destructively prune old vNNN/ snapshots from <spec-root>/history/ to bound history size. Requires explicit user invocation (model-driven invocation is disabled). Invoked only via livespec:prune-history or an explicit "prune the livespec history" request from…

Author the initial natural-language specification for a new project, populating the chosen template's spec_root layout. Invoked by livespec:seed, "seed a livespec spec", "set up a livespec", or when starting a brand-new spec in an empty SPECIFICATION/ tree.

Explain what livespec does and route the user to the right sub-command (seed, propose-change, critique, revise, doctor, prune-history). Invoked by livespec:help, "what can livespec do", or when the user asks for an overview of livespec capabilities.

Walk the user through accepting or rejecting pending proposed changes in <spec-root>/proposed_changes/, then snapshot the result as a new <spec-root>/history/vNNN/ revision. Covers every pending proposal by default, or ONE named proposal via --only-topic…

Critique an existing livespec specification or a pending proposed change, surfacing ambiguities, contradictions, and missing rules as findings the user can act on. Use when the user asks to critique the spec or find issues in it. This mutating operation can…

File a proposed change against an existing livespec specification, landing it under <spec-root>/proposed_changes/<topic>.md. Use when the user wants to record a spec amendment that the next revise pass will accept or reject. This mutating operation writes a…

Destructively prune old vNNN/ snapshots from <spec-root>/history/ to bound history size. Requires explicit user invocation because model-driven invocation is disabled, and a generic mention of history NEVER activates it. Invoked only via…

Author the initial natural-language livespec specification for a new project, populating the chosen template's spec_root layout. Use when starting a brand-new spec in an empty SPECIFICATION/ tree, or when the user asks to "seed a livespec spec" or "set up a…

Run the livespec doctor checks against a spec tree — the static phase (structural failures) plus the LLM-driven objective and subjective phases — surfacing findings as JSON or as a per-finding user dialogue. Use when the user asks to run livespec doctor or…

Explain what livespec does and route the user to the right livespec operation (seed, propose-change, critique, revise, doctor, prune-history, next). Use when the user asks what livespec can do or wants an overview of its capabilities. Read-only.

Rank the next spec-side action (revise, propose-change, critique, prune-history, or none) over the current <spec-target>/proposed_changes/ and <spec-target>/history/ state, emitting structured JSON. Use when the user asks what to work on next on the spec…

Compose spec, implementation, human-valve, and hygiene gather primitives into a Markdown attention list. Invoke as `/livespec-orchestrator-git-jsonl:needs-attention [--project-root <path>]`.

Detect spec→impl gaps by invoking the sibling detect-impl-gaps thin-transport skill, then file gap-tied work-items into the JSONL store with per-gap user consent. Required heavyweight authored skill per livespec/SPECIFICATION/contracts.md. Invoke as…

Detect impl→spec drift heuristically (LLM-driven) and hand off each finding to /livespec:propose-change with user consent. Required heavyweight authored skill per livespec/SPECIFICATION/contracts.md. Invoke as…

Freeform direct filing of an impl-side work item (bugs, refactors, tactical tasks). Required heavyweight authored skill per livespec/SPECIFICATION/contracts.md. Filed records carry `origin: freeform` and `gap_id: null`. Invoke as…

Detect spec→impl gaps mechanically via the Spec Reader and emit the current gap-id set as JSON. Required thin-transport surface per livespec/SPECIFICATION/contracts.md. Pure read-and-emit pass-through — never mutates the work-items JSONL, never prompts the…

Drive Red→Green for a single work-item. For gap-tied items, verify closure by re-running capture-impl-gaps in dry-run mode. Required heavyweight authored skill per livespec/SPECIFICATION/contracts.md. Invoke as `/livespec-orchestrator-git-jsonl:implement…

List work-items from the JSONL work-items store. Required thin-transport surface per livespec/SPECIFICATION/contracts.md. Invoke as `/livespec-orchestrator-git-jsonl:list-work-items [--filter <name>] [--with-gap-id <id>] [--json]`.

Rank the most-ripe impl-side action from the JSONL work-items store. Required thin-transport surface per livespec/SPECIFICATION/contracts.md. Pure function of file state; no LLM in the ranking path. Invoke as `/livespec-orchestrator-git-jsonl:next [--limit…

Compose the livespec-fleet-DEVELOPMENT signals a fleet maintainer must watch but an end user does NOT control — CI red on any fleet repo, fleet-conformance drift, stale cross-repo pins, cross-repo consistency drift, ledger status-conformance drift, a weakened…

Aggregate the whole livespec fleet's attention into ONE flat merged list. It fans out over `.livespec-fleet-manifest.jsonc` (fleet members + adopters), invokes each repo's shipped product `needs-attention --json`, folds in the local `needs-attention-internal`…

Walk the user through executing the livespec bootstrap plan one sub-step at a time, with confirmation gates at every step and persistent state across sessions. Pass `--ff` to fast-forward through the current phase without per-sub-step gates (still halts on…

A no-op fixture skill that exists solely to exercise structural skill discovery in the CLI e2e harness self-test. Not a real plugin skill.