Project Plan Kit — Start Here
What This Is
The project plan is the advisor's internal execution document for a specific client initiative. It tracks constraints, builds, stakeholders, prework, evidence, and timelines — everything needed to deliver a scoped engagement.
Audience: Advisor only. Never shared with the client. Format: Single-file HTML. Self-contained with embedded CSS, no external dependencies. Lifecycle: Living document. Updated after every session.
What It Produces
One HTML project plan per active initiative, named:
[client-first]-project-plan-[initiative-slug].htmlExample: ruben-project-plan-accounting-mgr-os.html
Relationship to Other Documents
| Document | Relationship |
|---|---|
| Constraint Priority Matrix | CPM feeds constraint data INTO the project plan |
| Master Plan | Master plan is the strategic overview; project plan is the initiative-level execution detail |
| Blueprint | Blueprint is the CLIENT-FACING mirror of the project plan — simplified, warm, no internal detail |
| Builds | Project plan designs the builds; builds/ folder holds the actual deliverables |
Document flow: CPM → Master Plan → Project Plan → Blueprint → Builds
Operating Modes
Mode 1: Create New Project Plan
When: New initiative identified from CPM/session analysis. Inputs: Latest CPM, session transcript(s), reference data, master plan. Process: Build all 14 sections from scratch following the output skill template.
Mode 2: Update After Session
When: After every client session where this initiative was discussed. Inputs: Session transcript, updated CPM, reference data. Process: Update sections in this order:
- Matrix Validation Banner (new constraint analysis)
- GPS (position/direction/speed changes)
- Current State vs Target State (if situation changed)
- Deployment Plan — build cards (advance deploy chains, update statuses)
- Constraints + Themes (new patterns, reclassifications)
- Prework (items received → move to received; new items needed)
- Evidence (new key quotes from session)
- Actions (new items from session, check off completed)
- Timeline (advance completed weeks, adjust future weeks)
- Header meta (update date, build count if changed)
File Inventory
| File | Purpose |
|---|---|
00-project-plan-start-here.md | This file — orientation and modes |
01-project-plan-context.md | Input types, field definitions, validation rules |
02-project-plan-terminology.md | Locked vocabulary for the project plan system |
03-project-plan-golden-example.html | Fully populated reference showing target quality |
04-project-plan-quality.md | 100-point QC checklist, 90+ to pass |
05-project-plan-output-skill.md | Production skill — template, components, content rules |
What This Kit Does NOT Do
- Does not produce the blueprint (that's a separate kit)
- Does not produce individual build deliverables (those use build-specific skills)
- Does not replace the master plan (master plan is cross-initiative; project plan is per-initiative)
- Does not communicate directly with the client (that's what blueprints and emails do)