Source: frameworks/kit-intensive-concept-brief/05-intensive-concept-brief-output-skill.md

Intensive Concept Brief Kit — Production Workflow

How to Use This Skill

Follow this workflow in order. The concept brief validates direction before anyone builds session content, skills, the Field Guide, or the Groundwork scripts.

Step 1: Gather Inputs

Open 01-intensive-concept-brief-context.md and fill in the template.

Load before writing anything:

business-aos/reference/core/voice.md — tone, cadence, vocabulary
business-aos/reference/core/audience.md — who they are, their language
business-aos/reference/core/ip-inventory.md — full IP landscape
03-intensive-concept-brief-golden-example.md — structural patterns to match
The golden example: content/business/marketing/content-pipeline/concept-briefs/intensive-concept-brief-practice-growth-os.md
The current state doc: business-aos/research/2026-03-25-current-state-practice-command-center.html

Validation gate: Do not proceed until:

The 3-session arc is defined (themes, skills, narrative)
Each session has a skill with clear input and output
The Groundwork design is documented
The promise is specific (names what they build, not vague outcomes)

Step 2: Source IP for Each Session

Search these locations in priority order for each session's skill:

Priority	Location	What to Look For
1	`ip-library/` GPT assistant .txt files	Deep methodology — discovery frameworks, diagnostics, scoring, output formats
2	`ip-library/micromagnet-archive-2026-3-15/` .docx files	Concept-level IP not documented in GPTs
3	`campaigns/practice-command-center/` skill files	Existing handraiser skills serving the same job
4	`content-pipeline/concept-briefs/`	Existing concept briefs with relevant IP sourcing
5	`content/frameworks/` kit files	Adjacent methodology in framework kits
6	`business-aos/reference/proof/angles/`	Angle files — thin framing only
7	`business-aos/reference/core/`	Audience, voice, IP inventory — context
8	`ip-library/` implementation workbooks (.docx)	5 system workbooks with build methodology

For each source found, document:

What it contributes to the session
Exact file path
Methodology depth: Deep / Partial / Needs Review / Gap / Reference
What adaptation is needed (input modality, Practice Brain integration, etc.)

Flag gaps explicitly:

Gap: [What's missing]. Content interview required: [Specific questions to ask Kathryn].

Step 3: Map Handraiser → Intensive Skills

For each session, identify the handraiser skill that serves the same job (if one exists).

Job	Handraiser Skill	Intensive Skill	What Makes It More Powerful
[Job]	[Name — free, standalone, paste input]	[Name — paid, Practice Brain, structured input]	[The upgrade]

Rules:

The handraiser skill's methodology transfers — the input modality changes
Intensive skills read from the Practice Brain (structured data), not pasted emails
Intensive skills can chain (Session 3's skill uses Session 2's output)
Not every handraiser skill maps to an Intensive skill — note which ones live in monthly Practice Builders builds instead

Step 4: Check Design Constraints

Verify the Intensive meets all 5 constraints:

Constraint	Question to Answer
Can't fail	What safety nets exist? What if they don't do the Groundwork? What if they fall behind in a session?
Sustainable	Can this run monthly with different topics? Does the format scale?
Win fast	Does every session produce a usable artifact? Can they act on it TODAY?
Non-technical	Can someone who's never used Claude complete the Groundwork and all 3 sessions? Where's the friction?
10-100x value	Does $97 feel like $1,000+? List every component.

Step 5: Document the Build Order

List every asset that needs to be built. For each:

Status (Not built / In progress / Built)
Blocking? (Yes / No — what depends on it?)

Then draw the dependency tree:

[Foundation asset]
  → [What depends on it]
    → [What depends on THAT]

The Practice Brain architecture is almost always the root dependency — every skill reads from it.

Step 6: Identify Teaching Stories

One teaching story per session + Email 1.

Session	What the Story Needs to Prove	How to Get It
1	The skill finds something surprising in real data	Kathryn runs the skill on her own practice data
2	The skill produces something publishable from past work	Kathryn runs the skill on a completed engagement
3	The skill produces a sendable proposal in minutes	Kathryn runs the skill on a real prospect conversation

Rule: Teaching stories cannot be fabricated. They require running the Intensive skills on real data. If the skills aren't built yet, flag the story as a blocker.

Step 7: Write the Concept Brief

Produces: intensive-concept-brief-[topic-slug].md in content-pipeline/concept-briefs/

Follow the section order from the golden example:

Header
The Promise
Who's In The Room
The Arc
The Groundwork
Session Design (3 sections with minute-by-minute beats)
IP Direction (one table per session + Groundwork)
Design Constraint Check
Cohesion Check — Handraiser → Intensive
What Needs To Be Built (with dependency tree)
Dual Conversion
Teaching Stories Needed
Open Questions
Next Steps

Step 8: QC the Concept Brief

Run 04-intensive-concept-brief-quality.md against the brief.

Blocking checks:

All 3 sessions have skills with clear input/output
IP sourced for every session with methodology depth ratings
IP gaps flagged with content interview requirements
Design constraints pass (all 5)
Build order documented with dependencies
Teaching story blockers flagged

Fix all failures before handing off to the Intensive Build Kit.

Step 9: Deliver

Final file goes to concept briefs:

content/business/marketing/content-pipeline/concept-briefs/intensive-concept-brief-[topic-slug].md

What happens next:

Kathryn validates the brief
Resolve open questions (especially those that affect build order)
Review flagged IP sources ("Needs Review" items)
Content interviews for IP gaps
Build Practice Brain architecture
Build each Intensive skill through the Skill Concept Brief Kit → Skill Build Kit pipeline
Build the Field Guide and Groundwork scripts through the Intensive Build Kit (future kit)