Solo founder

Skills (8)

• ceo-reviewDecide the scope of a feature or product version as the founder-CEO. Use after office-hours or when a plan, issue, or PR description needs a scope call. Picks one of four modes (expand, selective expand, hold, reduce), cuts or adds items with cost and value, and sets kill criteria. Writes docs/founder/scope/<slug>.md.
• design-shotgunExplore 4 to 6 clearly different design directions for one screen or flow in under an hour, then pick one. Use when a solo founder has agreed scope but no settled look, layout, or interaction model. Produces throwaway static HTML mockups and a comparison board in docs/founder/design/, plus a running taste log.
• founder-planTurn an idea into a buildable plan in one pass by chaining office-hours, ceo-review, and optionally design-shotgun, then slicing the work into day-sized vertical slices. Use when a solo founder wants to go from \"idea\" to \"what I build today\" without a full engineering review. Writes docs/founder/plans/<slug>.md.
• landMerge an approved pull request, follow the deploy, and verify production before calling it done. Use after ship when CI is green and the founder wants the change live. On first use it detects the deploy setup and records it in .founder/deploy.md, and it does a dry run before the first real merge.
• office-hoursPressure-test a product idea before any code is written. Use when a solo founder brings a new product, feature, or pivot and needs forcing questions that expose real demand, a specific first user, and the narrowest version worth building. Writes a one-page brief to docs/founder/briefs/.
• session-learningsCapture, search, prune, and export what a solo founder learns across sessions, stored in the repo at .founder/learnings.jsonl. Use at the end of a working session to record insights, at the start of a task to look up past lessons, or when the file needs cleanup. Keeps product, technical, process, and taste lessons with evidence.
• shipTake a finished change from a local branch to an open pull request with the repo's existing checks passing. Use when a solo founder says the work is done and wants it ready to merge. Syncs with the default branch, runs existing lint, type, and test commands, checks the diff for leaks, writes the PR description, and logs the ship in .founder/ship-log.md.
• weekly-retroRun a short weekly retrospective for a solo founder based on what actually shipped, not what was planned. Use at the end of a week or before planning the next one. Reads git history, merged PRs, the ship log, and plans, then writes docs/founder/retros/YYYY-Www.md with one bet for next week.