Templates
These are the seven templates inside the templates/ folder. They are not part of Day One setup. You do not need to open any of them to install plsBuild OS or to run your first session.
Think of them as the folder you walk back to when a specific moment in your work comes up. The day you need to write a launch checklist. The day you're trying to name your target user. The day you finish a sprint and want to run a real weekly review.
Two kinds of templates live here. Some are for Claude (you paste them into a Project or keep them alongside your spec so Claude uses them as context). Others are for you (you open them and work through them yourself, in your own notes).
Templates Claude uses
These give Claude more context about how you work, how you think about your product, and who you're building for. Paste them into Project Instructions (alongside your product brief) or save them as files Claude Code reads from your repo.
build-process.md
What it is: how you build things. The loop you follow from idea to ship, plus the rules you try not to break.
Where it goes: Project Instructions in claude.ai (alongside your brief), or a file in your repo that Claude Code reads.
When to use it: once, when you want Claude to know your actual build rhythm and push back when you break it.
product-vision.md
What it is: a structured way to sharpen what you're building and why.
Where it goes: fill it in once per product. Paste into Project Instructions below the brief, or upload as a file to the Project.
When to use it: early in a product, when you need to pressure-test whether you actually know what you're making.
who-is-this-for.md
What it is: a template for defining your actual target user, not a generic persona.
Where it goes: fill it in once per product. Paste into Project Instructions or upload as a file.
When to use it: when you catch yourself building for "everyone" and want to pick a real, specific person instead.
Templates for you
These are for you, not Claude. Open them, work through them in your own notes, and come back to them on a cadence. They don't live inside any Claude product, though you can paste parts of them into Claude when you want help with one specific piece.
weekly-review.md
What it is: a 30-minute structured weekly reflection.
Where it goes: your own notes. Notion, Apple Notes, a local file, whatever you use for personal journaling.
When to use it: once a week, ideally on the same day every week. End of Friday afternoons tends to work.
launch-checklist.md
What it is: everything to verify before a product goes public.
Where it goes: open it the day before launch and check off items as you go.
When to use it: the night before every real launch. You can also paste it into Claude and ask the /go-live skill to walk through it with you.
user-interview.md
What it is: a script and structure for running real user interviews without leading the witness.
Where it goes: open it before a scheduled interview. Use it as your question prompt and your notes doc.
When to use it: every time you talk to a user about your product. You can also paste your interview notes into Claude afterwards and ask the /research skill to pull patterns out of them.
gtm.md
What it is: first-pass go-to-market thinking. Channels, audience, launch sequence.
Where it goes: fill it in once when you're starting to think about distribution. Keep it in your notes, or paste it into Claude when you want growth advice anchored in your actual plan.
When to use it: when the product is close to shippable and you need to stop avoiding the "how do I get users" question.
Nothing in this folder is a hard requirement. These are the structured rituals I've found useful, pulled out into reusable templates so you do not have to rebuild the structure every time. Use what works. Leave what does not.