القائمة
Use when reviewing a plan, PRD, product direction, or proposal for strategy and assumptions. Triggers on "strategy review", "CEO review", or "is this ambitious enough".
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | v1-strategy-review |
| description | Use when reviewing a plan, PRD, product direction, or proposal for strategy and assumptions. Triggers on "strategy review", "CEO review", or "is this ambitious enough". |
| allowed-tools | ["Bash","Read","Grep","Glob","Edit","AskUserQuestion"] |
Review a plan like a founder who cares whether the work creates real user value, not just whether it is internally consistent.
Use after v1-interview-me when the idea is still fluid. Use before implementation when the plan already exists but scope, ambition, or user value are questionable.
Read the plan, PRD, ticket, or proposal. Then inspect nearby context:
docs/, README.md, CLAUDE.md, or AGENTS.mdDo not review from the title alone.
Choose one posture and state it clearly:
| Posture | Use When |
|---|---|
| Expand | The idea is directionally right but undershoots the user value |
| Selective expansion | The baseline is good, but a few adjacent improvements may be worth adding |
| Hold scope | The scope is right, and the goal is rigor |
| Reduce | The plan is overbuilt, vague, or solving a proxy problem |
If the user gave explicit posture language, follow it. Otherwise default to selective expansion for product features, hold scope for bug fixes and refactors, and reduce for plans that touch many files without clear user impact.
Do not add scope silently. Propose scope changes and get approval before editing a plan to include them.
Answer these before detailed review:
If the plan lacks demand evidence, say so. Interest, taste, or internal excitement is not demand.
Produce at least two implementation or product approaches:
For each approach, include effort, risk, reuse of existing code, what it validates, and what it defers.
Recommend one approach. Tie the recommendation to user value, speed to learning, and reversibility.
Evaluate the plan across these dimensions:
For each material issue, include what would change your mind.
Only for expand or selective expansion posture, look for:
Separate expansion candidates into:
Ask before adding any recommended expansion to the plan.
If the user asks you to update the plan, edit the existing artifact rather than creating a parallel strategy doc.
Preserve the original structure unless it is actively confusing. Add a Strategy Review section only when the plan has no obvious place for the findings.
Record decisions explicitly:
Use this structure:
## Strategy Review
Verdict: [one sentence]
Posture: [Expand / Selective expansion / Hold scope / Reduce]
### Must Fix
- [Issue, why it matters, recommended change]
### Scope Recommendations
- Add now: [...]
- Defer: [...]
- Skip: [...]
### Alternatives
1. [Minimal viable approach]
2. [Current/planned approach]
3. [Ideal approach]
### Open Questions
- [Question, owner if known, why it blocks progress]
### Next Action
[One concrete assignment]
If there are no serious issues, say that clearly, then list residual risks.
Use when explicitly choosing which v1tamins skill fits a task. Triggers on "which v1 skill", "v1 menu", or "/v1-menu".
Use when the user explicitly requests phone-a-friend, a counterpart review, steelman, or peer consult. Triggers on /v1-phone-a-friend or $v1-phone-a-friend only.
Use when explicitly convening several peer agents to review a PR or branch. Triggers on "review board", "multi-agent review", or "fan out a review".
Use when refining working code through a quality pass, deslop, or hindsight rewrite. Triggers on "make this diff simpler", "reduce complexity", or "deslop".
Use when diagnosing a throughput bottleneck in a process, funnel, queue, or WIP system. Triggers on "where is this process stuck?", "find the bottleneck", or "too much WIP".
Use when creating a self-contained HTML page, report, or interactive explainer. Triggers on "one-page dashboard", "shareable page", or "interactive report".