Plan ceo review
Curated skills and configurations for AI-assisted development
npx -y skills add ChristopherAlphonse/calphonse-skills --skill plan-ceo-reviewAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Founder-mode product review. Rethinks the problem, challenges scope, searches for stronger product opportunities, and chooses one of four review modes: SCOPE EXPANSION, SELECTIVE EXPANSION, HOLD SCOPE, or SCOPE REDUCTION.
SKILL.md
3.4 KB, as published. Nobody here has run it
Plan CEO Review
Review the plan from a founder/product strategy perspective before execution. Do not implement. Keep the user in control of every scope change.
Guardrails
- Challenge assumptions directly and write down unresolved ambiguity.
- Prefer focus over expansion unless the user explicitly chooses an expansion mode.
- Treat each opportunity as optional until accepted. Do not smuggle rejected ideas into scope.
- Define success in observable product or business terms, not vague quality claims.
Skill Chain
For a full founder/product review, run these local skills in order:
/plan-review-intake- find the plan and local.planning/*context./interrogate-me- stress-test the problem, user, scope, assumptions, risks, and tradeoffs./plan-review-scope- establish what already exists, what is in scope, and what is out of scope./plan-ceo-strategy- select the review mode and challenge the product direction./plan-ceo-opportunities- surface expansion, simplification, positioning, and trust opportunities one at a time./plan-ceo-wrapup- write the.planning/reviews/plan-ceo-review.mdartifact.
If a named skill is unavailable, inline that section using the same instructions from the corresponding skill file name above.
Review Modes
SCOPE EXPANSION: dream bigger and propose high-leverage improvements. Every expansion requires explicit opt-in.SELECTIVE EXPANSION: preserve baseline scope while offering optional improvements one by one.HOLD SCOPE: make the accepted scope sharper, more coherent, and safer without expanding or reducing it.SCOPE REDUCTION: find the smallest version that still achieves the core outcome.
Once the user chooses a mode, do not drift modes.
Product Review Principles
- Start with the user problem, not the proposed implementation.
- Separate reversible decisions from one-way decisions.
- Prefer focus: fewer things, better.
- Challenge proxy metrics that do not prove user value.
- Look for trust, safety, onboarding, and retention consequences.
- Ask what would make the plan fail, then remove or expose those failure paths.
- Prefer complete, bounded work over shortcuts that leave avoidable quality gaps.
- Write all durable outputs under
.planning/*.
Required Output
Write or update .planning/reviews/plan-ceo-review.md with:
Status:CLEAR,CLEAR_WITH_CONCERNS,NEEDS_DECISION, orBLOCKEDReview modePlan reviewedProblem framingTarget users and use casesScope decisionsAccepted opportunitiesRejected opportunitiesNOT in scopeRisks and reversibilitySuccess metricsTODO proposalsUnresolved decisionsCompletion summary
When a larger strategy document is useful, write it under:
.planning/strategy/{feature-slug}.md
Do not write durable workflow artifacts outside .planning/*.
Install:
npx skills add ChristopherAlphonse/calphonse-skills --skill plan-ceo-review