Tooluck logoTooluck
SKILL.md

product-manager

Agent skill fromcoreyhaines31/makerskills

When you want to plan, build, or check an app from idea through launch readiness — web, Apple, mobile, or extensions. Writes the brief, picks the stack (Next.js + TypeScript + Prisma by default, Swift on Apple), designs complete UX states, defines roles and agent access, measures performance before optimizing, and produces a readiness report where missing evidence is never a pass. Four modes: spec (plan v1), check (launch readiness), audit (ranked improvements, including what a new model changes), fleet (a named list of apps). Triggers on \"/product-manager,\" \"act as my product manager,\" \"PM this app,\" \"build me an app,\" \"plan v1,\" \"spec this app,\" \"is this app ready to launch,\" \"launch readiness,\" \"audit my apps,\" \"what's missing before we ship,\" \"do a comprehensive audit,\" \"how could we improve my app,\" \"a new model just came out.\" Not for launch marketing or growth (see launch), integration plumbing (see toolify), CI cost (see ci-audit), or managing a projec

How to install product-manager

install product-manager
# install the makerskills pack with the skills CLI
npx skills add coreyhaines31/makerskills

# or add only this skill to Claude Code: copy the folder

skills/product-manager/

# into

~/.claude/skills/product-manager/ (all projects)

.claude/skills/product-manager/ (one project)

skills/product-manager/SKILL.md

MITFull file
1# /product-manager — Take an app from idea to launch-ready
2
3Most apps that fail at launch don't fail on the main feature. They fail on what nobody specced: a client who can download another client's files, an invite button that sends twice on a slow network, a backup nobody ever restored, a cache keyed on project ID that leaks internal notes. This skill makes you decide those things up front, and then proves them before calling anything ready.
4
5It ends at **launch-ready**, not launched. Promotion, SEO, launch posts and growth go to the marketing skills.
6
7## Mental model
8
9- **Applicability, not parity.** A local macOS timer doesn't need organizations. A collaborative SaaS does. Choose a platform profile, then check what applies.
10- **Evidence, not vibes.** Every requirement ends up as pass, gap, not assessed, or justified N/A. Missing evidence isn't a pass.
11- **Measure, then fix.** Broken before slow. Baseline before cache.
12- **Complement the model.** Build what gets *more* useful as models improve.
13
14## Step 0 — Pick the mode
15
16| Mode | When | Output |
17|---|---|---|
18| **spec** | New app or v1 plan | Brief, stack, UX states, access model, test plan |
19| **check** | Existing app, "are we ready?" | Readiness report (read-only by default) |
20| **audit** | Existing app, "how could this be better?", or a new model just shipped | Ranked findings, model lens, comparison with the last audit (read-only) |
21| **fleet** | A named list of apps | One short report per app + a cross-app summary |
22…

Excerpt shown under the repository's MIT license.

More skills in makerskills

Keep exploring

Similar skill repositories

Newsletter

Join the Community

Subscribe to our newsletter for the latest news and updates