Audit AC-to-test traceability — find untested ACs, orphaned test prefixes, and coverage gaps
Write a feature card — capture who needs what, why, and expected behaviours as scenarios
Explore a vague idea through Q&A — capture what good looks like as an interview record for /orb:spec
Extract capability cards from source material — files, directories, or a whole project
Drive a card or spec through the orbit pipeline — promote → review-spec → implement → review-pr — at a declared autonomy level
Drive a single spec from claim to close — pre-flight check, AC tracking, gate enforcement, detour escalation, close-out
Socratic requirements interviewer — ask questions to clarify vague ideas into actionable requirements
Quickly jot a rough idea and file it in `.orbit/memos/`