Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →product-on-purpose/foundation-prioritized-action-plan
Produce a comprehensive, evidence-grounded prioritized action plan from any PM input (notes, transcripts, drafts, executive asks, Slack threads, or a raw situation). Outputs one saveable document with an executive summary, input mirror, situation classification (Cynefin), the binding constraint (Theory of Constraints), prioritized questions and open decisions, a ranked action plan with the critical effort plus follow-ons, risks and pre-mortem, copy/paste prompts for downstream pm-skills, and an
Passed 8 of 21 test cases with the skill, and 6 of 21 without it.
and 7 more in the full report
6 fixed2 passed either way10 still failing4 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
Here is the final completed version of our search experience PRD. The team has reviewed it and we are getting ready for engineering sign-off. Can you critique this finished artifact, highlight logical flaws, and point out missing edge cases?
| Checked | Without skill | With skill |
|---|---|---|
| The response indicates that analyzing or critiquing a finished artifact is out of scope for raw situation action planning. | Missed | Passed |
| The output suggests using a product management critic tool instead. | Missed | Passed |
The instructions your model reads when the skill loads.
You produce a comprehensive, evidence-grounded action plan from PM input the user provides. Your job is to identify the critical next effort, sequence the follow-on efforts behind it, and equip the user with copy/paste prompts to execute. The plan is the deliverable; the prompts are an enabler.
utility-pm-workflow-orchestrator, which runs them behind its own per-step checkpoints (see "Handoff to the orchestrator")One constraint binds at any moment; everything else is noise until it is lifted. Theory of Constraints supplies the prioritization logic: find the single binding constraint, make the critical effort (P1) the one that lifts it. Cynefin supplies the confidence calibrator: how knowable the situation is caps how confident the plan may be.
Evidence is structural, not decorative. You build a source ledger of exact input quotes before writing any section, and every load-bearing claim cites a ledger entry. If you cannot cite, you cannot claim it as fact.
The skill is honest about what it does not know. In Complex or Chaotic situations it refuses to manufacture High-confidence multi-step plans: Complex situations get safe-to-fail probes, Chaotic situations get stabilization actions, both at capped confidence.
utility-pm-critic: if the user asks "is this artifact good, what is wrong with it," use utility-pm-critic. Use this skill when the user asks "what should I do next" with incomplete context. A half-baked draft is in scope here; a finished artifact awaiting critique is not.jp-strategy-brief (jp-library): if the user wants broad strategic exploration, option framing, or "help me think through this," use jp-strategy-brief. Use this skill only when the user wants a ranked next-action plan inside PM delivery work. If both libraries are installed and the ask is ambiguous, prefer jp-strategy-brief for exploration and this skill for committed execution sequencing.using-workflows: if the user wants a multi-skill workflow walkthrough, use using-workflows. This skill may point toward a workflow but hands off rather than reproducing it.define-prioritization-framework: if the user already has a defined candidate list of features or initiatives and wants formal RICE/ICE/MoSCoW/Kano scoring, use define-prioritization-framework. Use this skill when the input is a raw, unstructured situation and the user wants the single critical next effort, not a scored comparison across a list.| Framework | Role in the skill | Where it appears |
|---|---|---|
| Theory of Constraints (Goldratt) | Prioritization engine; identifies THE one binding constraint, which becomes the critical effort P1 | Step 3 (constraint) and Step 5 (plan ranking) |
test cases passed, vs 6 / 21 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.