Run the strategy phase for one project — re-derive its judged files from the research records, build the offer, mechanism, and big-idea options, recombine them into MULTIPLE rated strategies the owner picks among, and attack each for construction and reality. Produces the three plan files the writer executes against. TRIGGER when a project needs its strategy set before writing. DO NOT TRIGGER to gather the evidence it cites (market-research, product-research) or to write the copy (write).
Installs into .claude/skills of the current project.
Are you the author of Strategy?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/heyjordanparker-strategy)
---
name: strategy
description: Run the strategy phase for one project — re-derive its judged files from the research records, build the offer, mechanism, and big-idea options, recombine them into MULTIPLE rated strategies the owner picks among, and attack each for construction and reality. Produces the three plan files the writer executes against. TRIGGER when a project needs its strategy set before writing. DO NOT TRIGGER to gather the evidence it cites (market-research, product-research) or to write the copy (write).
---
# Strategy
One Process: turn a project's research into a settled direction the writer can execute — MULTIPLE rated strategies the owner picks among, then the three plan files. This owns the phase; each composed skill owns its own step and is never restated here.
## 1. Build the strategies
Run plan-copy as the spine: it re-derives the project's own judged files from the original research records and recombines building blocks into high-level strategies. Fan the option sets inside the picked strategy with the shared idea process — draft-offers for the invitation, mechanism for the named Process, big-idea for the charged idea the piece hangs on — each returning survivors, not one guess.
## 2. Attack construction and reality
Run check-strategy on the assembled packet before any plan file is written — is this the right buyer, at the right stage, answered in the right order. Run check-reality on the strategies and their evidence — does the buyer, problem, and language actually exist. Findings ride to the owner; nothing is auto-killed.
## 3. Rate everything and write the plan
Every problem, buyer, offer, mechanism, and strategy carries a 1-to-100 rating with its reasoning (see grading) and its existence rating. Ratings RIDE to the pick; no low rating removes an option. From the settled direction, plan-copy writes the three plan files — Reader.md, Brief.md, Proof.md.
## Owner boundary
The phase stops at the owner's pick. It builds and rates the strategy set; the owner picks against the numbers and their reasoning, and only the picked direction becomes plan files.
## Verification
The strategy set carries every strategy with its rating and reality read, check-strategy and check-reality returned findings on the assembled packet, and Reader.md, Brief.md, and Proof.md are written from the owner's pick.
