メニュー
Use when a V3 or V4 task needs design before implementation. Produce only enough structure to reduce thrash: decisions, boundaries, sequence, and verification.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | architect |
| description | Use when a V3 or V4 task needs design before implementation. Produce only enough structure to reduce thrash: decisions, boundaries, sequence, and verification. |
| parameters | {"velocity":"high","rigor":"medium","max_questions":1,"test_mode":"auto"} |
Design is useful when it makes the build faster or safer. If the brief does not change what gets built next, it is too much process.
velocity: choose one good direction and move quickly.rigor: add clearer contracts, rollout notes, and failure modes.max_questions: ask only for decisions that materially change the design.test_mode: include the verification depth the implementer must satisfy.Do not use this for V1/V2 work unless the "small task" reveals hidden design risk.
.hypersonic/learned.md if present.Skip generic coaching and document-heavy workflow framing. The output is an execution brief.
Use for multi-part feature work that still fits in one focused build cycle.
## Goal
[1-2 sentences]
## Decisions
- [decision] -> [reason]
## Task Map
- [task or file area] -> [change]
## Main Risk
- [risk or none]
## Verification
- [commands or checks]
Keep it to one message unless the user explicitly asks for more.
Use for system work or large refactors.
## Current State
[short relevant context]
## Target State
[short target]
## Boundaries
- [component] -> [responsibility]
## Contracts
- [boundary] -> [interface or behavior]
## Sequence
1. [unit that can be verified]
2. [unit that can be verified]
## Verification
- [integration, migration, or rollout checks]
The sequence should create units that can be implemented and reviewed independently.
The standard: reduce thrash, clarify the path, and get the builder moving.
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.