Source: frameworks/kit-intensive-concept-brief/01-intensive-concept-brief-context.md
Intensive Concept Brief Kit — Context & Inputs
Concept Brief Template
Complete this before designing session content, skills, or the Field Guide. Every field is required unless marked optional.
The Intensive
| Field | Value |
|---|
| Working title | [e.g., Practice Growth OS Intensive] |
| Topic/system | [e.g., Find → Prove → Close (pipeline growth)] |
| Target dates | [e.g., Apr 21-23, Tue/Wed/Thu] |
| Position | [e.g., "Intensive #1 — first run, founding cohort"] |
The Promise
| Field | Value |
|---|
| One-paragraph promise | [What they build in 3 sessions — specific, outcome-focused] |
| Tagline | [One line — e.g., "By Thursday, your practice has a growth engine that didn't exist on Monday."] |
| What they should feel signing up | [e.g., "I need to block those 3 days immediately."] |
| What they should feel after | [e.g., "I can't believe I built that in 3 sessions. For $97."] |
The Arc
| Field | Value |
|---|
| Session 1 theme | [One word — e.g., "Find"] |
| Session 1 one-sentence version | [What they do + what they walk away with] |
| Session 1 skill | [Skill name — e.g., "Client Expansion"] |
| Session 2 theme | [One word — e.g., "Prove"] |
| Session 2 one-sentence version | [What they do + what they walk away with] |
| Session 2 skill | [Skill name — e.g., "Proof Engine"] |
| Session 3 theme | [One word — e.g., "Close"] |
| Session 3 one-sentence version | [What they do + what they walk away with] |
| Session 3 skill | [Skill name — e.g., "SOW Machine"] |
| The narrative | [How the 3 sessions connect — e.g., "Find the money → Arm yourself with proof → Close with confidence"] |
Session Input/Output
For each session:
| Session | Skill | User Input | Skill Output (Artifact) |
|---|
| 1 | [Name] | [What user provides — e.g., "client roster + services catalog from Practice Brain"] | [What skill produces — e.g., "ranked growth opportunities + 3 outreach messages"] |
| 2 | [Name] | [What user provides] | [What skill produces] |
| 3 | [Name] | [What user provides] | [What skill produces] |
Groundwork Design
| Field | Value |
|---|
| Total time | [e.g., ~40 minutes] |
| Step 1 | [e.g., "Get Claude Running (15 min)"] |
| Step 2 | [e.g., "Practice Profile Conversation (20 min) — produces Practice Profile + structured reference files"] |
| Step 3 | [e.g., "Site Survey (5 min) — produces Build Order"] |
| What participants see | [The readable documents they get — useful even without the Intensive] |
| What's actually produced | [The Practice Brain infrastructure the skills read from] |
| Non-completer plan | [What happens if they don't do the Groundwork] |
Handraiser → Intensive Skill Mapping
| Job | Handraiser Skill (Free, Standalone) | Intensive Skill (Paid, Practice Brain) | What Makes It More Powerful |
|---|
| [Job 1] | [Skill name and input] | [Skill name and input] | [The upgrade — e.g., "roster-wide vs. single-client"] |
| [Job 2] | [Skill name and input] | [Skill name and input] | [The upgrade] |
| [Job 3] | [Skill name and input] | [Skill name and input] | [The upgrade] |
Teaching Stories
| Session | Story Needed | Status |
|---|
| Session 1 Demo | [What story — e.g., "Kathryn runs Client Expansion on own roster. Finds $40K."] | [Captured / Needs capture / Blocker] |
| Session 2 Opener | [What story] | [Status] |
| Session 3 Opener | [What story] | [Status] |
| Email 1 | [What story — often same as Session 1 demo] | [Status] |
Dual Conversion
| What They Say | Path | Offer |
|---|
| [e.g., "I want to keep building"] | Practice Builders | [$97/mo — description] |
| [e.g., "Build it for me"] | Advisory OS | [$1,500-5K/mo — description] |
| Closing line | [e.g., "You built three skills in three sessions. Build one a month with us, or hand us the list."] |
IP Search Locations (Mandatory)
Search these locations in priority order for each session's skill. Every IP source must be documented with methodology depth.
| Priority | Location | What to Look For |
|---|
| 1 | ip-library/ GPT assistant .txt files | Deep methodology — discovery frameworks, diagnostic questions, scoring systems, output formats |
| 2 | ip-library/micromagnet-archive-2026-3-15/ .docx files | Concept-level IP — may have methodology not documented in GPTs |
| 3 | campaigns/practice-command-center/ skill files | Existing handraiser skills that serve the same job at a lower capability level |
| 4 | content-pipeline/concept-briefs/ | Existing concept briefs that may have relevant IP sourcing |
| 5 | content/frameworks/ kit files | Adjacent methodology in kits (constraint identifier, master plan, etc.) |
| 6 | business-aos/reference/proof/angles/ | Angle files — thin framing, not methodology |
| 7 | business-aos/reference/core/ | Audience, voice, IP inventory — context, not methodology |
| 8 | ip-library/ implementation workbooks (.docx) | 5 system workbooks — may have build methodology |
IP Sourcing Rules
- Every IP source gets a methodology depth rating: Deep (documented, needs adaptation), Partial (conditions documented, detection needs enrichment), Needs Review (file exists, haven't confirmed depth), Gap (no documented methodology, content interview required), Reference (examples/framing only).
- Vault IP library is the primary methodology source. GPT assistant .txt files contain the deepest documented methodology. Start there.
- Angle files are thin reference only. They frame the problem; they don't contain build methodology.
- Handraiser skills inform but don't replace. Intensive skills are more powerful (Practice Brain integration). The handraiser skill's methodology transfers; the input modality changes.
- Flag every gap explicitly. If a session's skill needs methodology that doesn't exist anywhere in the vault, say so. These become content interview requirements.
Validation Rules
Do not proceed to the Intensive Build Kit if these are missing:
- [ ] All 3 sessions have a defined skill with clear input and output
- [ ] The arc narrative connects all 3 sessions (each builds on the last)
- [ ] IP sourced for each session with methodology depth ratings
- [ ] IP gaps flagged with content interview requirements
- [ ] Design constraint check passes (can't fail, sustainable, win fast, non-technical, 10-100x value)
- [ ] Build order with dependencies documented
- [ ] Teaching stories identified (even if not yet captured — blockers flagged)
- [ ] Groundwork design produces both readable documents AND Practice Brain infrastructure
- [ ] Handraiser → Intensive skill mapping documented
- [ ] Open questions listed (even if unresolved — they inform the build sequence)
Voice check before any copy:
Load business-aos/reference/core/voice.md and business-aos/reference/core/audience.md before writing the promise, session titles, and teaching story requirements.