Menu
Synthesize your project journey into a publishable narrative โ tutorial, case study, blog post, or launch story. Pulls from git history, artifacts, and your decision log. Use when you want to write about how you built something.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Design and scaffold your own AI org structure with custom agents, skills, teams, hooks, and MCP servers. Interactive wizard that interviews you, proposes an org, generates a visual chart, and creates all files.
Create design direction, HTML mockups, and UI/UX recommendations for a feature or product. Use when the user needs visual direction, component specifications, or user flow diagrams.
Research and validate product ideas, market opportunities, or feature concepts. Use when the user wants to explore whether an idea is worth pursuing, needs competitive analysis, or wants to understand a market.
Review code, specifications, or designs for quality, bugs, security, and best practices. Use when the user wants feedback on recent work, a pull request, or any artifact.
Execute a batch of backlog tickets in parallel. Use when the user wants to build multiple unblocked tickets simultaneously with integrated QA review.
Break a spec or feature into prioritized, dependency-tracked tickets for implementation. Use when a spec is too large to build at once, or when the user wants to create individual work items with MVP/P1/P2 phasing.
| name | story |
| description | Synthesize your project journey into a publishable narrative โ tutorial, case study, blog post, or launch story. Pulls from git history, artifacts, and your decision log. Use when you want to write about how you built something. |
| argument-hint | optional: format and topic |
| disable-model-invocation | true |
You are synthesizing the CEO's project journey into a publishable narrative.
If $ARGUMENTS specifies a format, use it:
If no format is specified, infer from the content:
If $ARGUMENTS provides a title, topic, or focus area, use it to narrow scope.
Gather material from three sources (in order of storytelling value):
Read .solopreneur/observer-log.md. These entries capture the CEO's actual decisions โ what they chose, what options they rejected, and why. This is the raw material that makes a story authentic. If the log is sparse or empty, that's fine โ the other sources compensate. Also check .solopreneur/observer-archives/ for older entries if a longer history is needed.
git log --oneline --stat
Commit messages show what was accomplished and when. The --stat output shows scope (which files, how much changed). Use this to build the narrative timeline and identify milestones.
Read files from .solopreneur/ directories:
discoveries/ โ What ideas were explored, what was validatedspecs/ โ What was planned, what requirements were setdesigns/ โ What the UX looks like, what design decisions were madeplans/ โ Implementation plans and what was builtreleases/ โ What was shippedThese provide the concrete details that give the story substance.
Gather sources โ Read the decision log, run git log, scan .solopreneur/ for artifacts. Note what's available and what's sparse.
Identify the arc โ Every project has a story: starting point โ challenges โ decisions โ outcome. Map the material to this arc. The CEO's decisions (from the observer log) are the most compelling parts.
Select format โ Choose based on $ARGUMENTS or infer from content (see above). Tell the CEO which format you're using and why.
Delegate to @content-strategist with the gathered material and the format-specific template below.
Save to .solopreneur/stories/{date}-{slug}.md (create the directory if needed).
Present to the CEO for review. Note where they should add real screenshots or personal anecdotes.
Pass the appropriate template to @content-strategist:
# [Title]
## What We're Building
[Context โ what and why, 2-3 paragraphs]
## Prerequisites
- [Tools, knowledge, setup]
## Step N: [Description]
**What we did**: [Action]
**Why**: [Rationale โ pull from decision log entries]
**Code/Commands**:
...
**Result**: [What happened]
[IMAGE: description of what to screenshot]
## Key Takeaways
- [3-5 lessons from the process]
# [Title]
## The Problem
[Starting situation โ what wasn't working]
## The Approach
[Strategy chosen and alternatives considered]
## What We Built
[Solution overview with key decisions]
## Results
[Outcomes, metrics if available, before/after]
## Lessons Learned
- [What worked, what didn't, what we'd do differently]
# [Title]
[Hook โ the most interesting moment, decision, or surprise]
## How It Started
[Origin โ the idea, the motivation]
## The Journey
[Narrative of key decisions, pivots, and surprises. Use the CEO's actual words from the decision log where possible.]
## What I Learned
[Reflections and takeaways]
## What's Next
[Where the project goes from here]
# [Title]
## Why I Built This
[Personal motivation โ what problem the CEO wanted to solve]
## How It Works
[Product overview โ clear, benefit-focused]
## The Building Process
[Brief journey highlights โ most interesting decisions or challenges]
## Try It
[CTA โ how to use it, where to find it]
Tell the @content-strategist:
[IMAGE: description] placeholders where visuals would help