Menรผ
Use after PRD is ready but before implementation. Locks architecture, data flow, edge cases, and test plan so scope cannot silently creep during build.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fรผgen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prรผfen und installieren.
Basierend auf der SOC-Berufsklassifikation
| name | plan-eng-review |
| description | Use after PRD is ready but before implementation. Locks architecture, data flow, edge cases, and test plan so scope cannot silently creep during build. |
๊ตฌํ ์์ ์ ์ architecture / data flow / edge cases / test plan ์ ์ ๊ทธ๋ skill. Scope freeze ์ง์ ๋จ๊ณ.
/office-hours ๋ก ๋์๊ฐ๊ธฐPlan.md ๋ฅผ ์ ๋์ ์ผ๋ก ์ฝ๊ณ ๋ค์์ ์ ๊ทผ๋ค.
๋ช ์์ ์ผ๋ก ๋ค์์ ์ ๊ฒ:
size_check.py ๋ก ์์ tier / complexity ํ์ธ# Plan-Eng Review โ <๋ ์ง>
## Architecture verdict
- Accept / Revise
- Issues found: <list>
## Data flow verdict
- Accept / Revise
- Missing boundaries: <list>
## Edge cases checklist
- [x] empty input
- [x] large input
- [x] concurrency
- [ ] <ํญ๋ชฉ> โ NOT covered in plan
## Test plan verdict
- Accept / Revise
- AC โ test mapping: <table>
- Risky test modifications: <list>
## Tier confirmation
- Classified: <tier> / <complexity>
- Plan says: <tier>
- Match: yes / no
## Blocking issues (must fix before scope_lock)
1. ...
## Non-blocking suggestions
1. ...
## Next gate
If Accept โ `runtime_gate.py lock-scope` + `runtime_gate.py review-plan`
<INSUFFICIENT_OBJECTIONS>.lock-scope / review-plan gate flag ๋ฅผ flip.planner ์ required_reviewers ์ญํ ์ ์ํ.Plan.mdPRD.mdCLAUDE.md, AGENTS.md.claude/sealed-prompts/plan-redteam.mdExplicit GPT-5.6 native-first router for auditing, designing, installing, or validating Codex skill combinations, global skill setup, routing fixtures, and harness behavior. Use when the user explicitly invokes $codex-skill-router or asks to change or inspect Codex skills, routing, AGENTS guidance, or global harness configuration. Do not use for ordinary coding, review, debugging, research, or UI work merely because the task is complex.
Use when work introduces or changes shared nouns, states, IDs, ownership, authority, or customer-facing vocabulary.
Use when changing harness gates, routing rules, skills, or automation behavior and benchmark/eval evidence is needed to avoid slowing normal coding performance. Do not use for ordinary app code changes.
Use when a request is early, ambiguous, or lacks a codebase-backed shared language; interview the user to expose assumptions before planning.
Use when a codebase, docs, ADRs, tests, prior reviews, or team traces exist; align new work with existing shared language before implementation.
Use first for normal or high-risk natural-language work to choose task mode, tier, grill path, spec layers, team-rule scan, and required gates before implementation.