hashgraph-online/awesome-codex-plugins / plugins/alpoxdev/hypercore/skills/hyper-plan
hyper-plan
Verified[Hyper] Use this skill when the user asks to plan a change before implementation - a feature, refactor, migration, fix, or multi-step build - and expects a decision-complete plan file that a worker can execute without another interview. It explores read-only, writes only a draft and a plan under `.hyper/`, reviews the plan for gaps, then continues into execution by default unless the user asked for a plan only. Do not use for PRD, spec, or wireframe packages; for immediate edits that need no plan; or for research reports.
| File | Kind | Size |
|---|---|---|
| SKILL.ko.md | markdown | 19.8 KB |
| SKILL.md | skill md | 17.8 KB |
| assets/evals/hyper-plan-cases.jsonl | other | 18.3 KB |
| assets/plan-template.ko.md | markdown | 2.1 KB |
| assets/plan-template.md | markdown | 2.0 KB |
| references/plan-format.ko.md | markdown | 10.8 KB |
| references/plan-format.md | markdown | 9.8 KB |
| rules/handoff.ko.md | markdown | 8.0 KB |
| rules/handoff.md | markdown | 7.3 KB |
| rules/plan-review.ko.md | markdown | 10.4 KB |
| rules/plan-review.md | markdown | 9.3 KB |
| rules/planning-workflow.ko.md | markdown | 16.1 KB |
| rules/planning-workflow.md | markdown | 14.0 KB |
| rules/stance-calibration.ko.md | markdown | 10.0 KB |
| rules/stance-calibration.md | markdown | 9.0 KB |
assets/plan-template.md
View on GitHub# <slug> - Work Plan
## TL;DR
- What you get: <the outcome in one line>
- Why this approach: <the evidence-backed reason>
- What it will not do: <the refused additions>
- Effort: <Quick | Short | Medium | Large | XL>
- Risk: <concrete risks, including a dirty worktree when present>
- Decisions made for you: <each adopted default and its reversibility>
## Scope
### Affected user and ideal state
Affected user: <who>, today <how they use it>, after <how they use it>.
| ID | Property or gap | Why it matters |
|---|---|---|
| IS-1 | <property of the state where nothing snags or regresses> | <reason> |
| GAP-1 | <difference between that state and today> | <reason> |
### Must have
- <required outcome>
### Must NOT have
- <addition the plan refuses>
## Verification strategy
<test levels, exact commands, real-surface checks, adversarial classes that apply>
## Execution strategy
### Wave 1
- Todos <numbers>
| Todo | Depends on | Wave | Write scope |
|---|---|---|---|
| 1 | none | 1 | <paths> |
## Todos
- [ ] 1. <title>
Wave: 1
Depends on: none
Write scope: <exact paths or globs>
References: <paths with line anchors, documentation URLs>
Acceptance: <literal command and expected result>
QA happy: <tool, exact invocation, binary observable>; evidence: <path>
QA failure: <tool, exact invocation, binary observable>; evidence: <path>
Commit: <message in the repository's convention>
Tier: <low | medium | high> - <one-line reason>
## Final verification wave
- [ ] F1. Plan compliance audit
- [ ] F2. Code quality review
- [ ] F3. Real-surface QA
- [ ] F4. Ideal-state fidelity (every IS row, 1:1)
## Commit strategy
<one commit per todo, message convention, evidence handling, wave landing>
## Success criteria
| IS row | Delivering todo(s) | Proving QA | Evidence path |
|---|---|---|---|
| IS-1 | 1 | <check> | <path> |
## Handoff
- Auto-execute: <yes | no (reason)>
- Delivery: <local | make-pr | ship>
- Plan-only requested: <yes | no>
<!-- Copy to .hyper/plans/<slug>.md, replace every <placeholder>, and keep the headings verbatim. -->
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 469k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |