hypersonic

Use when a V3 or V4 task needs design before implementation. Produce only enough structure to reduce thrash: decisions, boundaries, sequence, and verification.

Use when the user wants the agent to keep working without waiting for input. Autopilot runs continuously: finish the given plan first, then keep making one meaningful verified improvement per iteration until interrupted.

Use after implementation, before shipping, or when the user asks for review. Focus on correctness, regressions, verification gaps, failure handling, security, and performance. Skip style-only noise.

Use after meaningful work to capture confirmed repo-specific knowledge in `.hypersonic/learned.md` and `.hypersonic/history.jsonl`: conventions, gotchas, test patterns, architecture notes, and user preferences.

Classify coding work into Hypersonic V1-V4 tiers, choose the lightest safe workflow, set verification depth, and hand off to focused skills. Use at the start of software tasks or when scope changes.

Use when the user wants to explore, prototype, vibecode, or move fast without heavy process. Build the first useful version quickly, show something real, and iterate from feedback.

Use when work is ready to be committed, pushed, merged, or turned into a PR. Handle final verification, git state, commit shape, branch choice, PR text, and safety checks.

Use when fixing a bug, investigating a failure, or diagnosing unexpected behavior. Evidence first: read the failure, reproduce it, isolate root cause, make the smallest fix, and verify.

Use when writing or updating tests during implementation. Apply risk-calibrated TDD: test-first for risky behavior, test-with for normal tasks, and manual verification for low-risk changes.