Skip to content

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.

assets/plan-template.ko.md

View on GitHub
# <slug> - Work Plan

## TL;DR

- What you get: <결과를 한 줄로>
- Why this approach: <근거에 기반한 이유>
- What it will not do: <거부하는 추가 항목>
- Effort: <Quick | Short | Medium | Large | XL>
- Risk: <구체적 위험. 작업 트리가 더러우면 그 사실 포함>
- Decisions made for you: <채택한 기본값과 되돌릴 수 있는지>

## Scope

### Affected user and ideal state

Affected user: <누구>, 오늘은 <어떻게 쓰는지>, 실행 뒤에는 <어떻게 쓰는지>.

| ID | Property or gap | Why it matters |
|---|---|---|
| IS-1 | <걸리거나 퇴행하는 것이 없는 상태의 속성> | <이유> |
| GAP-1 | <그 상태와 오늘의 차이> | <이유> |

### Must have

- <필요한 결과>

### Must NOT have

- <계획이 거부하는 추가 항목>

## Verification strategy

<테스트 수준, 정확한 명령, 실제 표면 점검, 적용되는 적대적 범주>

## Execution strategy

### Wave 1

- Todo <번호>

| Todo | Depends on | Wave | Write scope |
|---|---|---|---|
| 1 | none | 1 | <경로> |

## Todos

- [ ] 1. <제목>
  Wave: 1
  Depends on: none
  Write scope: <정확한 경로나 글롭>
  References: <줄 앵커가 붙은 경로, 문서 URL>
  Acceptance: <실제 명령과 기대 결과>
  QA happy: <도구, 정확한 실행, 이분법 관찰값>; evidence: <경로>
  QA failure: <도구, 정확한 실행, 이분법 관찰값>; evidence: <경로>
  Commit: <저장소 관례의 메시지>
  Tier: <low | medium | high> - <한 줄 이유>

## 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

<todo마다 커밋 하나, 메시지 관례, 근거 파일 처리, wave 착지 방식>

## Success criteria

| IS row | Delivering todo(s) | Proving QA | Evidence path |
|---|---|---|---|
| IS-1 | 1 | <점검> | <경로> |

## Handoff

- Auto-execute: <yes | no (reason)>
- Delivery: <local | make-pr | ship>
- Plan-only requested: <yes | no>

<!-- .hyper/plans/<slug>.md로 복사하고 모든 <placeholder>를 바꿉니다. 제목은 적힌 그대로 유지합니다. -->
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: 470kUpdated Claude CodeCodexVerifiedInstall
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: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
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 availableStars: 322kUpdated Claude CodeCodexVerifiedInstall