Templates

AI Business OS

A template is a file you reuse as a starting point. It fixes the layout and structure of a document, such as the sections of a proposal or the headings of a meeting note, and leaves the content to be filled in. A template does not tell Claude how to behave. Rules and skills do that, and they can point Claude to a template when a task needs one.

Where Templates Live

Location	What it holds
`Documentation/Templates/`	Document templates for the whole workspace, starting with `PRD-TEMPLATE.md`
`references/` inside a skill folder	Templates that one skill uses, such as your own meeting note layout for the `meeting-notes` skill
`Domains/01 Clients/_Templates/`	A folder for client folder templates, empty in a new workspace

Templates in Documentation/Templates/ serve the whole workspace. If a template belongs to one project, keep it in that project’s folder instead.

The PRD Template

Documentation/Templates/PRD-TEMPLATE.md is the one template that ships with AI Business OS. PRD stands for product requirements document, the file that states what a project is for and when it is done. /newproject uses this template to build the PRD.md file in every new project folder.

The template has ten sections.

Section	What it records
1. Problem Statement	The problem the project solves and who it affects
2. Goals	What success looks like
3. Target Users	Who the work is for and what they need
4. Requirements	Must-have, should-have and out-of-scope items, each with acceptance criteria
5. Technical Approach	Key choices and the reasons for them
6. Build Phases	Phases with deliverables and a “done when” outcome for each
7. Constraints	Budget, timeline, dependencies and technical limits
8. Success Criteria	Measurable outcomes
9. Open Questions	Questions to answer before or during the work
10. References	Links to related work

/newproject fills the problem statement, goals, target users, must-have requirements, constraints and build phases from your answers to its questions. It then shows you the draft. If you choose to add detail later, Claude marks the empty sections [TBD — to be filled in] so you can find them.

The PRD template is an engine file, so you can edit it to suit your business. Your change is normally kept when you run /update. If a later version changes the same lines, the update stops and marks the conflict for you to resolve. Keep the file name the same, because /newproject looks for PRD-TEMPLATE.md by name.

Adding Your Own Document Templates

Put any document you reuse in Documentation/Templates/, for example a proposal outline, a meeting agenda, a report layout or an onboarding checklist. Structural files such as templates take an upper-case name without a date, as in PROPOSAL-TEMPLATE.md.

The drafting-documents skill checks Documentation/Templates/ for an existing template before it drafts a proposal, report, brief or memo. Name a template clearly, or tell Claude which one to use, for example “draft the proposal from PROPOSAL-TEMPLATE.md”.

Templates for One Skill

Several built-in skills read a references/ folder inside their own skill folder, which you create when you need it. Put templates there when only that skill uses them.

Skill	Templates its `references/` folder can hold
drafting-documents	Sample documents, boilerplate sections such as disclaimers and signatures, industry document structures
meeting-notes	Note layouts for recurring meeting types and standard agenda structures
status-report	Branded report templates and standard report formats
client-setup	Client templates for your industry and onboarding checklists

To build a new skill, the creating-skills skill uses its own scaffold templates, so a new skill follows the same structure as the ones that ship with the workspace.

The Client Templates Folder

Domains/01 Clients/_Templates/ ships empty. The client-setup skill lists it as a source to read when it creates a client folder. /newclient does not read it, and builds every client folder with the same structure of README.md, Projects/, Communications/ and Reference/.