Blueprint Kit — Start Here
What This Is
The blueprint is the client-facing progress dashboard for a specific initiative. It shows the client where they are, where they're going, what's being built, and what's needed from them — in language that respects their intelligence without exposing internal advisor mechanics.
Audience: The client. This is their document. Format: Single-file HTML. Self-contained with embedded CSS, no external dependencies. Lifecycle: Living document. Updated only when something changes what the client sees.
What It Produces
One HTML blueprint per active initiative, named:
[client-first]-blueprint-[initiative-slug].htmlExample: ruben-blueprint-accounting-mgr-os.html
Relationship to Other Documents
| Document | Relationship |
|---|---|
| Project Plan | Blueprint mirrors the project plan's build structure — simplified for client consumption |
| CPM | Constraint data flows through the project plan into the blueprint's opening frame |
| Master Plan | Master plan context informs the blueprint but is never exposed to the client |
| Builds | Blueprint references builds by name; builds/ folder holds the actual deliverables |
Document flow: CPM → Master Plan → Project Plan → Blueprint → Builds
Operating Modes
Mode 1: Create New Blueprint
When: New initiative has an approved project plan. Inputs: Approved project plan, reference data, latest CPM. Process: Build all 9 sections from scratch following the output skill template.
Mode 2: Update After Session
When: Only when something changes that affects what the client sees. Inputs: Updated project plan, session transcript, reference data. What triggers an update:
- Build status changed (queued → active, active → review, etc.)
- New build added or build scope changed
- Prework received or new prework needed
- Questions resolved or new questions surfaced
- Timeline shifted What does NOT trigger an update:
- Internal constraint reclassification
- Stakeholder card updates (internal)
- Evidence/quotes added (internal)
- Advisor notes changes (internal)
File Inventory
| File | Purpose |
|---|---|
00-blueprint-start-here.md | This file — orientation and modes |
01-blueprint-context.md | Input types, content filtering rules, validation |
02-blueprint-terminology.md | Client-facing vocabulary — what terms mean to THEM |
03-blueprint-golden-example.html | Fully populated reference showing target quality |
04-blueprint-quality.md | 100-point QC checklist with tone and jargon checks |
05-blueprint-output-skill.md | Production skill — template, components, content rules |
What This Kit Does NOT Do
- Does not expose internal constraint analysis (that stays in the project plan)
- Does not include stakeholder cards, evidence quotes, or advisor notes
- Does not tell the client what their problem is — frames the work around observable situations
- Does not replace the project plan (blueprint is derived FROM the project plan)
- Does not produce individual build deliverables
Critical Rule
The blueprint is the client's document. Every word, every section, every design choice must pass this test: "Would this make sense and feel respectful if the client read it cold?" If the answer is no, it belongs in the project plan, not here.