meridian-online/orbit

audit

Audit AC-to-test traceability — find untested ACs, orphaned test prefixes, and coverage gaps

card

Write a feature card — capture who needs what, why, and expected behaviours as scenarios

discovery

Explore a vague idea through Q&A — capture what good looks like as an interview record for /orb:spec

distill

Extract capability cards from source material — files, directories, or a whole project

drive

Drive a card or spec through the orbit pipeline — promote → review-spec → implement → review-pr — at a declared autonomy level

implement

Drive a single spec from claim to close — pre-flight check, AC tracking, gate enforcement, detour escalation, close-out

interviewer

Socratic requirements interviewer — ask questions to clarify vague ideas into actionable requirements

memo

Quickly jot a rough idea and file it in `.orbit/memos/`

prioritise

Name the next move live from workflow conformance, the session-prime envelope, and recent memories. One verb, one sentence on why now, a deferred count. Read-only — the author runs the verb.

rally

Coordinate multiple cards through the orbit pipeline as one delivery — proposal → design → implementation → review

release

Release a new orbit plugin version — bump, commit, push, and reload into Claude Code so /reload-plugins picks up changes.

review-pr

Verify an implementation before merge — runs tests, checks AC coverage, reads diff cold

review-spec

Progressive spec review — depth scales with findings, not upfront classification

setup

Set up a project for the orbit workflow — creates .orbit/ directory with artefact subdirs on greenfield, or interactively migrates bare-layout or wrapped-undotted repos to the .orbit/ folder on brownfield

spec-architect

Transform interview conversations into structured YAML specifications with numbered ACs

spec

Generate a structured YAML specification with numbered ACs from interview results

tabletop

Front-loaded pre-spec thinking — walk values, trade-offs, halt conditions and kill conditions across a card or cluster to produce aligned specs

topology

Scaffold, read, and audit subsystem topology entries — pointer-only yaml linking each subsystem's canonical code, decision record, operational doc, and test surface.

code-investigate

Investigate code before changing it — narrow mode for specific queries, broad mode for neighbourhood awareness. Routes to ast-grep, tree-sitter, ripgrep, and rtk-wrapped variants by default.

hacker

Find unconventional workarounds when the "right way" fails or blocks progress

keyword-scan

Keyword search across orbit artifacts (cards, choices, specs, memos, memories) using rg/grep — shared technique.

ontologist

Identify the essential nature of problems using four fundamental ontological questions

researcher

Stop coding and investigate systematically — gather evidence before acting

simplifier

Cut complexity ruthlessly — remove until only the essential remains