plan-ceo-wrapup

Creates a CEO wrap-up artifact and optional strategy note in the .planning folder.

1|Updated May 7, 2026

Search Tags:#planning #documentation #generate #artifact #product-management #ceo-wrapup

Ready to run

npx skills add https://github.com/ChristopherAlphonse/calphonse-skills --skill plan-ceo-wrapup

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plan-ceo-wrapup
Source: https://github.com/ChristopherAlphonse/calphonse-skills/tree/main/plan-ceo-wrapup
Command: npx skills add https://github.com/ChristopherAlphonse/calphonse-skills --skill plan-ceo-wrapup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writes structured founder/product review artifacts and optional strategy notes to the project planning directory (.planning), ensuring decisions, assumptions, and next steps are captured for future reference.

Core Features & Use Cases

Writes the CEO wrap-up artifact to .planning/reviews/plan-ceo-review.md for archival and review continuity.
Optionally creates a strategy note under .planning/strategy/{feature-slug}.md to accompany the review.
Preserves scope, decisions, assumptions, risks, and follow-ups, enabling repeatable and auditable product reviews.
Keeps artifacts aligned with the project commit and planning structure for easy traceability.

Quick Start

Run the plan-ceo-wrapup skill to generate the CEO wrap-up artifact for the current project.

Frequently Asked Questions about plan-ceo-wrapup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I generate a CEO wrap-up artifact for product review documentation?▼

To generate a CEO wrap-up artifact, you run the skill to create a structured markdown file at .planning/reviews/plan-ceo-review.md. This document preserves decisions, assumptions, risks, and follow-ups for repeatable product leadership workflows.

What is the best way to capture product decisions and risks in a planning folder?▼

The best way to capture product decisions and risks is using a structured review artifact written to the project's .planning directory. This ensures assumptions and next steps are auditable and aligned with the project commit structure.

Can I create a strategy note alongside a product review artifact?▼

Yes, you can create a strategy note alongside the product review artifact. The skill optionally generates a feature-specific strategy note under .planning/strategy/{feature-slug}.md to accompany the main CEO review.

Does generating a CEO wrap-up require any external dependencies?▼

Generating a CEO wrap-up does not require external dependencies. It operates independently to write structured founder product review artifacts to the local .planning directory using deterministic output paths.

Why should I use a structured artifact for product leadership reviews?▼

You should use a structured artifact for product leadership reviews to ensure decisions, assumptions, and risks are captured repeatably and auditably. This enables future reference and keeps artifacts aligned with the project commit structure.