Skip to main content

FOR FOUNDERS & PRODUCT MANAGERS

Founders & PMs

You're steering, not coding line by line. You want to know what's happening, make the calls that matter, and trust that the work gets routed to the right place. claude-kit is built for exactly that.

Start lean, grow into it​

If you're not sure how much structure you need, start with minimal — a PM plus one capable generalist. As the work grows, add roles with /kit-customize, or re-scaffold toward software when you're building a real product.

Building something technical from day one? Pick software and you get the full team — PM, Tech Lead, Designer, DevOps, Backend, Frontend, QA, Security.

The PM is your dashboard​

Every profile includes a PM role. It owns work state, tracked through GitHub:

  • "What's the state?" — it gives you a grounded read: what's in progress, what's blocked, what's next.
  • New scope — describe a feature in plain language and it drafts the issues.
  • Plans and issues stay linked — it keeps the plan and the tracked work pointing at each other, and surfaces blockers before they bite.

There's a morning-briefing skill, too: a quick start-of-day snapshot of where things stand.

You make the calls; the team does the work​

The coordinator at the top doesn't make domain decisions itself — it routes them to the role that has the depth, then synthesizes the result back to you. So a security question is answered by security, a design call by the designer. You see one coherent answer and the next steps, without having to manage who-does-what.

It remembers, so you don't repeat yourself​

Turn on memory at setup and the team keeps a per-project record of decisions, plans, and rationale. Come back next week, start a fresh session, and the context is still there. See Memory.

Running several projects​

If you're juggling more than one product or client, the kit is per-project by design, and you can set shared defaults once across a whole folder. See Multiple projects.

Where to go next​