adidactaadidacta/pmf-detective/skills/pmf-context/SKILL.md

pmf-context

Skill18 starsChanged 9 months agoMITView on GitHub

Build your PMF context layer - reference files that capture the "WHY" behind your product. Use when user mentions "PMF", "product market fit", "define my PMF context", "PMF context", "ICP", "value prop", "aha moments", or asks about understanding customers or market positioning.

In this repository9 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- landing-generatorSkill
- build-test-guideSkill
- icp-builderSkill
- mvp-builderSkill
- outreach-builderSkill
- plan-pmf-modeSkill
- validation-plan-builderSkill
- value-prop-builderSkill

The file

We split this skill into the rules it gives an agent

9 rules. About 0 are common, 8 are distinctive, and 1 is very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Distinctive:
Check for existing context files
line 17
Distinctive:
Keep everything focused on building useful context
line 19
Very specific:
Check the pmf/ folder to understand current progress:
line 37
Distinctive:
Read existing files to understand what's defined
line 73
Distinctive:
When user wants to work on a specific section:
line 133
Distinctive:
Check for existing pmf/ files first
line 142
Distinctive:
Never overwrite without user consent
line 143
Distinctive:
Use visual boxes for important information
line 145
Distinctive:
Keep it simple - no sprints, no tasks, no validation metrics
line 146

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

SKILL.md

PMF Context - Coordinator Skill

You help product builders create their PMF context layer - a set of reference files that Claude uses when building anything for their product.

Your Role

Orchestrate the PMF context layer building process
Check for existing context files
Route to appropriate builders or show status
Keep everything focused on building useful context

The Context Layer

The PMF context layer consists of 4 files in the pmf/ folder:

pmf/
├── icp.md              # Who you believe your customer is (assumption)
├── value-prop.md       # Why they should care (assumption)
├── mvp.md              # MVP scope — aha moment, features & requirements (assumption)
└── validation-plan.md  # How you'll test these assumptions

The first 3 files are assumptions. The validation plan helps test them with real market signals.

Progress Detection

Check the pmf/ folder to understand current progress:

pmf/icp.md exists → ICP defined
pmf/value-prop.md exists → Value proposition defined
pmf/mvp.md exists → MVP scope defined
pmf/validation-plan.md exists → Validation plan set

Behavior

When user starts fresh (no pmf/ folder):

Show welcome and suggest starting the full context build:

┌───────────────────────────────────────────────────────────────┐
│  PMF CONTEXT LAYER                                            │
├───────────────────────────────────────────────────────────────┤
│                                                               │
│  Build your PMF context - reference files that capture        │
│  the "WHY" behind your product.                               │
│                                                               │
│  The context layer:                                           │
│  • icp.md - Who your customer is                              │
│  • value-prop.md - Why they should care                       │
│  • mvp.md - MVP scope & features                              │
│                                                               │
│  Claude will reference these files when building              │
│  anything for your product.                                   │
│                                                               │
├───────────────────────────────────────────────────────────────┤
│  Start: /plan-pmf to build your full context layer            │
└───────────────────────────────────────────────────────────────┘

When user has some context files:

Read existing files to understand what's defined
Show status with visual box
Suggest completing missing sections or updating existing ones

When all context files exist:

Show complete status and explain how to update:

┌───────────────────────────────────────────────────────────────┐
│  PMF CONTEXT LAYER - COMPLETE                                 │
├───────────────────────────────────────────────────────────────┤
│                                                               │
│  [✓] ICP - pmf/icp.md (assumption)                            │
│  [✓] Value Proposition - pmf/value-prop.md (assumption)       │
│  [✓] MVP - pmf/mvp.md (assumption)                            │
│  [✓] Validation Plan - pmf/validation-plan.md                 │
│                                                               │
├───────────────────────────────────────────────────────────────┤
│  Your context layer is ready.                                 │
│  Claude will reference these when building for your product.  │
│  Run your validation plan to test your assumptions.           │
│                                                               │
│  To update:                                                   │
│  • /update-icp - Refine your ICP                               │
│  • /update-value-prop - Update your value proposition         │
│  • /update-mvp - Revise MVP scope                              │
└───────────────────────────────────────────────────────────────┘

Status Display

When showing status:

┌───────────────────────────────────────────────────────────────┐
│  PMF CONTEXT STATUS                                           │
├───────────────────────────────────────────────────────────────┤
│                                                               │
│  [✓] ICP (assumption)                                         │
│      Who: [Brief summary from icp.md]                         │
│                                                               │
│  [✓] Value Proposition (assumption)                           │
│      Core: [Primary message from value-prop.md]               │
│                                                               │
│  [ ] MVP (assumption)                                         │
│      Not yet defined                                          │
│                                                               │
│  [ ] Validation Plan                                          │
│      Not yet defined                                          │
│                                                               │
├───────────────────────────────────────────────────────────────┤
│  Progress: ██████████░░░░░░░░░░  2/4 sections                 │
├───────────────────────────────────────────────────────────────┤
│  Next: /update-mvp to define MVP scope                        │
└───────────────────────────────────────────────────────────────┘

Routing

When user wants to work on a specific section:

ICP, customer, target audience → icp-builder
Value prop, messaging, Callout + Magnet → value-prop-builder
MVP, PRD, scope, features, aha moments, benefits → mvp-builder
Full context build → plan-pmf-mode

Important Rules

Check for existing pmf/ files first
Never overwrite without user consent
Show summaries from existing files when available
Use visual boxes for important information
Keep it simple - no sprints, no tasks, no validation metrics

Attribution

Created by Adi Shmorak, The P/MF Detective Star on GitHub if this helped | Feedback: adi@adidacta.com

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

It worked
Partly
It didn't

What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free