community-pitch

Files (2)

• SKILL.md
• output-schema.json · references/

SKILL.md (first lines)

# Community Pitch

Transform persona extraction output and signal scan data into a complete paid community plan. Produces a structured JSON spec and a human-readable markdown summary with community concept, platform recommendation, membership tiers, content cadence, launch plan, economics, community structure, bundling strategy, and kill criteria -- all grounded in persona data and market signals.

## Step 0: Load Conventions

Before doing ANYTHING, read the shared conventions file:

```
Read ${SKILLS_DIR}/_conventions.md
```

This file defines: canonical vault path, folder-to-type mapping, frontmatter contract, valid statuses, tag hierarchy, cross-reference syntax, and the PipelineEnvelope schema. All output from this skill MUST conform to those conventions. If there is a conflict between this SKILL.md and `_conventions.md`, the conventions file wins.

## Pipeline Position

```
signal-scan -> decision-log -> persona-extract -> **community-pitch** -> hunter-log
                                                   (sibling of offer-scope)
```

This skill consumes the output of `persona-extract` and `signal-scan`, and feeds into `hunter-log` for execution tracking. It runs parallel to `offer-scope` -- where offer-scope produces a one-time product spec, community-pitch produces a recurring-revenue community plan.

## When to Use

- Converting validated persona insights into a paid community plan
- Evaluating whether a domain supports a recurring community model
- Designing a Skool (or comparable platform) community from scratch
- Creating a membership pricing model anchored to WTP data
- Planning a community launch from zero audience
- Building a recurring revenue complement to one-time products from offer-scope

## Trigger Phrases

- "Pitch a community for [domain]"
- "Design a paid community from this persona data"
- "Should I build a community for [domain]?"
- "Community plan for [persona]"
- "Skool community for [domain]"
- "/community-pitch [persona-extract output]"

---

## Prerequisites

Before starting, the following must be available:

1. **Persona extraction output** -- A completed persona-extract result containing: persona names, pain stories (with situation/pain/emotional state), decision triggers, willingness-to-pay data, and channel behavior
2. **Signal scan data** -- SPEND signals and COMPETITIVE signals from a completed signal-scan, plus the meta-signal
3. **Domain and opportunity** -- The specific domain and opportunity area being targeted

If any of these are missing, prompt the user to run the upstream skill first or provide the data manually.

---

## Input

The skill expects the following input structure (typically assembled from upstream skill outputs):

```typescript
interface CommunityPitchInput {
  personas: {
    persona_name: string
    pain_stories: { situation: string, pain: string, emotional_state: string }[]
    decision_triggers: { trigger: string, urgency: string }[]
    willingness_to_pay: { range: string, evidence: string }
    channels: { platform: string, behavior: string }[]
  }[]
  domain: string
  opportunity: string
  spend_signals: { signal: string, price_range: string, platform: string }[]
  competitive_signals: { signal: string, type: string, impact: string }[]
  meta_signal: string
}
```

---

## Workflow

```
Persona + Signal Scan Data (from upstream skills)
    |
Phase 1: Community-Market Fit Assessment (does this domain support a community?)
    |
Phase 2: Concept Design (name, transformation, core promise)
    |
Phase 3: Platform Selection (Skool, Circle, Discord, etc.)
    |
Phase 4: Membership & Pricing (tiers, monthly/annual, founding member pricing)
    |
Phase 5: Content Cadence Design (recurring value, minimum viable cadence)
    |
Phase 6: Launch Planning (pre-launch, founding members, first 30 days, growth)
    |
Phase 7: Economics (MRR projections, churn, break-even, time investment)
    |
Phase 8: Structure Design (channels, onboarding, engagement, retention)
    |
Phase 9: Bundling Strategy (connect to one-time products, value ladder)
    |
Output: JSON spec + Markdown summary -> hunter/docs/
```

---

## Phase 1: Community-Market Fit Assessment

Before designing anything, evaluate whether this domain actually supports a paid community. Not all domains do. A community is the wrong model for one-time problems.

Score the following five dimensions (1-10 each), with evidence from persona data:

| Dimension | Question | Where to Find Evidence |
|-----------|----------|----------------------|
| Recurring pain | Is the pain ongoing or one-time? | Persona pain stories -- look for patterns of repeated frustration, not single events |
| Peer connection desire | Do these personas want to connect with others like them? | Persona channel behavior -- are they already in communities, forums, Discords? |
| Identity component | Is there a professional or personal identity tied to this domain? | Persona names and language -- "I'm a DevOps engineer" suggests identity; "I need to fix my router" does not |
| Knowledge evolution | Does the knowledge in this domain change frequently? | Signal scan -- are there trend signals showing the landscape shifts? |
| Accountability need | Do these personas need external structure to follow through? | Pain stories -- look for "I know I should but..." or abandoned attempts |

From Peleke/brunnr, MIT.

More from Peleke/brunnr