ChristopherAlphonse Plan CEO Wrapup
Write the product review artifact.
Guardrails
- Preserve accepted scope exactly. Do not reintroduce rejected opportunities.
- Separate decisions, assumptions, non-goals, and follow-ups.
- Keep the artifact concise and action-oriented.
- Put useful but out-of-scope work in TODOs only with user approval.
Artifact
Write or update:
.planning/reviews/plan-ceo-review.md
Include:
- Status
- Review mode
- Plan reviewed
- Problem framing
- Target users and use cases
- Scope decisions
- Accepted opportunities
- Rejected opportunities
- NOT in scope
- Risks and reversibility
- Success metrics
- TODO proposals
- Unresolved decisions
- Completion summary
If a long-form strategy note is needed, write:
.planning/strategy/{feature-slug}.md
TODO Handling
For useful rejected opportunities, ask whether to:
- A) Add to
.planning/tasks/TODOS.md - B) Skip
- C) Put back into the current plan
Do not write to any non-.planning/* project path.
Install:
npx skills add ChristopherAlphonse/calphonse-skills --skill plan-ceo-wrapup