Skill map

Pin this. Print it. Keep it open in a tab. It's the single-page reference for plsBuild OS once you're set up.

18 skills, organized by the phase you're in

Six of these you'll reach for every week — marked ★. The rest are for specific moments. Don't try to learn them all at once. Notice when you're in a phase and pull the matching skill.

🌱 Before you build

• spec ★. Write or update what you're building. The memory between sessions.
• research. Talk to users without leading them. Turn feedback into real signal.
• audit. After any big decision, before you commit to it.
• pitch. Position, frame, and name a product or feature clearly.

🔨 While you build

• build ★. Before shipping a feature you want to do right.
• voice ★. Before writing any marketing copy, landing page, email, or bio.
• design ★. When a visual decision feels off and you want a second pair of eyes.
• unblock. When you're stuck mid-build and don't know why.

🚀 Almost done

• ship ★. When the product mostly works but you can't get it out the door.
• go-live. The day before you launch anything. Pre-launch checklist.

📣 After it's live

• launch. When the product is ready and you want to tell people it exists. Builds the channel list, phase plan, post drafts, attributed links, and execution board in one session.
• growth. When figuring out how to get users and where they already are.
• support. When replying to users, handling bug reports, complaints, or refund requests.
• retro ★. At the end of a sprint, release, or experiment. Learn from what just happened.

⚙️ The system itself

• learning-log. When you want Claude to remember a correction for next time.
• pull-in. Load a focused skill on demand without loading every skill every session.
• learn-codebase. Importing an existing product — Claude reads it and drafts your profile + project skill.
• agents. Specific reviewer lenses: Engineer, Designer, User, Skeptical Investor, Risk Checker, Editor, Honest Mirror.

★ The core six. If you use plsBuild OS weekly, these are the ones that carry the load: spec, build, voice, design, ship, retro. Learn these first. The rest you discover when the moment comes.

How to summon a skill

Just ask for it by name. Claude pulls the skill in automatically.

"Use the voice skill to write three subject lines for my launch email."

"Run an audit on this pricing decision."

"Do a retro on what we shipped today."

"Run the Honest Mirror on whether I should start this new feature."

You can also let Claude pick. "Write me three subject lines for my launch email" will often invoke voice automatically. Asking by name is just more reliable when you want a specific lens.

The one rule

Keep the project spec updated. At the end of every meaningful session, ask Claude:

"Update the spec with what we did today."

Claude drafts the update based on the session. You review it, paste into the spec, done. Under two minutes.

Skip this and Claude will see an old spec next session and repeat advice you've already moved past. Keep it up and you stay weeks ahead of where you'd be without it.

When in doubt

• Lost in the weeds? Run the Honest Mirror agent.
• Stuck for more than 20 minutes? Run unblock.
• About to make a decision that feels loaded? Run audit.
• About to ship something public? Run go-live.
• A user said something that stung? Run support before replying.
• Wondering if anyone will actually use this? Run research, then the User agent.

Daily rhythm

You don't need all 15 skills every day. Most days you'll use two or three. Here's a rough rhythm:

• Mornings. Open your product Project, ask Claude to summarize where things stand from the spec. Decide what to work on.
• During the work. Invoke skills as the work calls for them. Don't force it.
• End of session. Update the spec with what you did. Commit if you're using git.
• End of week. Open templates/weekly-review.md and do the 30-minute review.

If you forget everything else

• Your profile and skills live across all your Claude conversations automatically (in claude.ai and Cowork). You set them up once.
• Your product context (brief + spec) lives per-product. One per thing you're building.
• Ask Claude to update the spec at the end of every meaningful session. That's the whole ritual.

You bought this because you didn't want to figure it out the hard way. Use it. Don't let it sit in a folder on your desktop.