How it works · Motifs

COMING SOON

The skills on this page are parked while we test them. Today, copy a play into your coding agent, or connect the MCP so it can look plays up.

Connect the MCP

HOW MOTIFS WORKS

From first idea
to what’s next.

Three skills run in the coding agent you already use. Each reads what the last one wrote, asks you only what it can’t find, and pulls researched plays from Motifs on the way.

Start with one play Questions

Made for your coding agentCodexClaude CodeOther coding agents

FROM FIRST IDEA TO WHAT’S NEXT

Marketing belongs in
your product’s DNA.

It’s more than what you say at launch. It’s what you choose to build,
how it feels to use, and why someone comes back.

Claude, use Motifs to plan a habit app for language learners, then find a growth play that fits. Start with Planning Head: ask about my idea and write PRODUCT.md.

motifs MCP connectedTry it in Claude Code

01 · Plan

Start from scratch

“Tell me what you want to build, who you imagine using it, and what you want it to help them accomplish.”

Then one to three at a time

Who are you building it for first?
How do they handle this today?

Planning Head · writesPRODUCT.md

01 · Plan

Start from your repo

README and landing copy, done
Pricing and billing code, done
Onboarding screens, in progress

Drafts what the code says, then asks only about the gaps. Motifs never sees the code.

Planning Head · writesPRODUCT.md

02 · Build

Build from the plan

Reads PRODUCT.md first, done
Feature: reward the return after a miss, done
Research suggestion, with its limits, in progress

Execution Head · writesFEATURES.md

03 · Go to market

Pick the play, then test it

Compares 3 reference plays on

Outcome evidence, done
Whether it transfers here, done
What the build supports, in progress
Then one small first test

GTM Head · writesLAUNCH.md

PRODUCT.md2 agreed2 provisional1 open

SectionDecisionBorrowed from

Product descriptionAgreedA daily speaking habit for adults learning a languageYour answer—

Problem and desired progressAgreedLessons never turn into speaking. They want to hold a real conversationYour answer—

Sample use caseProvisionalTen minutes of speaking on the commute, the month before a tripExample, not observed—

OfferProvisionalDaily practice free; paid unlocks feedback on speakingYour answerLock everything, or give the core awaySourced · 7 evidence entries

What makes it differentOpenWhy would someone choose this over their current solution?Question to resolve—

Example output. Pick either plan card to switch. The product and its answers are illustrative; every play named is a real record.

THREE HEADS, ONE THREAD

Each step writes down
what the next one reads.

Nothing lives in a chat that scrolls away. Every decision lands in a markdown file in your project,
so the agent that builds knows what the agent that planned agreed with you.

01 · Plan
Planning Head
ReadsYour idea, or your repoPlays you pick, as inspiration
AsksOne to three questions at a time
WritesPRODUCT.md
- 1Product description
- 2Problem and desired progress
- 3Sample use case
- 4Offer
- 5What makes it different
02 · Build
Execution Head
ReadsPRODUCT.mdPlays for the feature
AsksOnly what would change the answer

THE PLANNING HEAD

It asks. You decide.

Start with one rough sentence, or point your agent at the repo. The Planning Head turns either into a product brief, PRODUCT.md: five sections, and each decision marked by who made it.

From scratch, it asks one to three questions at a time: the ones that would change the direction, never the whole checklist.
From your repo, it drafts what the code already says, marks it Provisional, and asks only about the gaps.
Plays you pick come in as inspiration. They never override what you want to build.

What makes it differentOpen

What would make someone switch to it?

THE EXECUTION HEAD

Every feature arrives with its limits.

The Execution Head reads your product brief before anything else. If the direction isn’t settled, it goes back and plans with you first, keeping whatever you already agreed.

A feature comes with the smallest useful version and how you’ll know it helped.
A research-based suggestion doesn’t have to add anything. Sometimes the answer is to remove a step.
It writes the feature list, FEATURES.md: what is live, unreleased or half-built, so nothing gets marketed before it exists.

THE GTM HEAD

The biggest number doesn’t win by default.

Hand it one play or several. The GTM Head weighs each against the same goal: the outcome evidence, whether it transfers to you, and what your build supports. Then it picks, and says how sure it is.

It asks for goal, budget and audience in small batches, and records the answers in the launch plan, LAUNCH.md, so nobody asks twice.
“Not feasible now” is not “unlikely to work”. It says which.
The first test is chosen for what it teaches, not as a prediction that it wins.

WHAT YOUR AGENT PULLS

Plays, with the fine print attached.

Each head reaches into the same library. A finding never travels without its limits,
and every row says how strong its evidence is.

Your repoRead by your agent, on your machine

Motifs MCPAnswers with records

Motifs gets the search, never your code.

motifs · tool calls

search_plays funnel_stage: retention · min_evidence: controlled_experiment→ summaries, strongest evidence first

get_play comeback-after-miss-or-lapse→ the whole record: mechanism, sources, evidence, when to avoid it

STRONGPublished play preview

Finding

A 125-point bonus (about $0.09) for the planned gym visit after a missed one added 0.40 weekly visits over four weeks — 27% above the placebo group's 1.48. Milkman et al. megastudy, 24 Hour Fitness members.

Limits

The only outcome evidence is one megastudy of gym members over four weeks, with bonuses worth $0.09 and $0.16. The authors say top-performing estimates are probably inflated and need replication.

WRITTEN INTO EACH SKILL

What it won’t do.

The rules the three heads keep, whoever asks.

Every head
It won’t Invent evidence
No made-up studies, statistics or customer evidence. A number keeps its population and its caveat.
Planning Head
It won’t Mark a guess as agreed
What it infers from your repo stays Provisional until you confirm it.
Execution Head
It won’t Rewrite your direction to fit a play
Plays adapt to your product. Your product brief changes only with your agreement.
GTM Head
It won’t Let the famous company win
The biggest result or best-known name doesn’t rank first by default.
GTM Head
It won’t Market what isn’t built
Unreleased or partial features are never promised as available.
GTM Head
It won’t Publish, contact or spend
A plan authorises nothing. It acts only on what you explicitly ask.

BEFORE YOU START

Questions, answered.

Which coding agents does it work with?

You can paste a copied play into any coding agent or AI chat. To connect Motifs for the full workflow, your agent’s MCP client must support remote HTTP servers and browser sign-in. The examples here use Claude Code, Codex and Cursor. See connection options.

Do I have to start from scratch?

No. Point your agent at an existing repo and the Planning Head drafts your product brief from what the code already says: the README, pricing, onboarding. Everything it infers starts Provisional, and it asks only about what the code can’t tell it.

Does Motifs see my code?

No. Your agent reads your repo on your machine. What reaches Motifs is a search for plays, and what comes back is the records.

Where do the product brief, feature list and launch plan live?

At the root of your project, as PRODUCT.md, FEATURES.md and LAUNCH.md: plain markdown your agent writes, where any agent will find them. If your AGENTS.md says they live somewhere else, the heads look there. They’re yours to read, edit and commit. Each head reads the ones before it, so a question you’ve answered once isn’t asked again.

Can I skip straight to building or launching?

You can ask, but the Execution Head won’t recommend features without a settled product brief. It goes back to planning, keeps what you’ve already agreed, and asks only what’s missing. The GTM Head needs at least one reference play and won’t substitute generic marketing advice for one.

How much should I trust a play?

As far as its evidence goes, and each record says how far that is. Every evidence row carries its tier and what it does not establish, side by side, in the copied record and on the page for members. All plays today are Sourced: built from published experiments and company reports, not yet checked on a dated day.

Will it change my product on its own?

No. A feature recommendation is not permission to build it, and a launch plan is not permission to publish, contact anyone or spend money. It implements only what you ask, and edits your product brief only with your agreement.

Start with
one play.

Copy it into the agent you already use. No account needed to browse.

Start with one play Explore the plays

A good place to start

From first idea
to what’s next.

Marketing belongs in
your product’s DNA.

Start from scratch

Start from your repo

Build from the plan

Pick the play, then test it

Each step writes down
what the next one reads.

Planning Head

Execution Head

It asks. You decide.

Every feature arrives with its limits.

The biggest number doesn’t win by default.

Plays, with the fine print attached.

What it won’t do.

It won’t Invent evidence

It won’t Mark a guess as agreed

It won’t Rewrite your direction to fit a play

It won’t Let the famous company win

It won’t Market what isn’t built

It won’t Publish, contact or spend

Questions, answered.

Start with
one play.

GTM Head

Reward the return after a miss

Two button labels, two groups

From first ideato what’s next.

Marketing belongs inyour product’s DNA.

Start from scratchFrom scratch

Start from your repoYour repo

Build from the planBuild

Pick the play, then test itGo to market

Each step writes downwhat the next one reads.

Planning Head

Execution Head

It asks. You decide.

Every feature arrives with its limits.

The biggest number doesn’t win by default.

Plays, with the fine print attached.

What it won’t do.

It won’t Invent evidence

It won’t Mark a guess as agreed

It won’t Rewrite your direction to fit a play

It won’t Let the famous company win

It won’t Market what isn’t built

It won’t Publish, contact or spend

Questions, answered.

Start withone play.

GTM Head

Reward the return after a miss

Two button labels, two groups

From first idea
to what’s next.

Marketing belongs in
your product’s DNA.

Start from scratch

Start from your repo

Build from the plan

Pick the play, then test it

Each step writes down
what the next one reads.

Start with
one play.