foundation-prioritized-action-plan

Name: foundation-prioritized-action-plan
Author: product-on-purpose

486stars64forks

How to install foundation-prioritized-action-plan?

product-on-purpose/pm-skills/foundation-prioritized-action-plan

$npx -y skills add product-on-purpose/pm-skills --skill foundation-prioritized-action-plan

Installs into the current project.

Summary

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 bin

Files · 1

View on GitHub

SKILL.md

1	<!-- PM-Skills \| https://github.com/product-on-purpose/pm-skills \| Apache 2.0 -->
2	# Prioritized Action Plan
3
4	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.
5
6	## Identity
7
8	- Foundation skill; produces a reusable PM working-document the user saves and reuses
9	- Single-turn; one action plan per invocation
10	- Read-only tools (Read, Grep); produces markdown output
11	- Recommends a bounded, tiered set of downstream pm-skills (see "Recommendable skill tiers") and never invokes them inline; on explicit confirmation it can hand the plan to `utility-pm-workflow-orchestrator`, which runs them behind its own per-step checkpoints (see "Handoff to the orchestrator")
12
13	## Core principle
14
15	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.
16
17	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.
18
19	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.
20
21	## When to Use
22
23	- The user has input (notes, transcript, executive ask, draft PRD, customer interview, Slack thread, raw situation) and wants a ranked next-action plan
24	- The user is uncertain what to do next and wants a recommendation grounded in their actual context
25	- The user wants a single referenceable artifact that says what is most important, why, and how to execute it
26
27	## When NOT to Use
28
29	- vs `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.
30	- vs `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.
31	- vs `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.
32	- vs `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.
33	- The user wants to generate a specific named artifact (persona, OKRs, journey map): invoke that skill directly.
34	- The input is unrelated to PM work: refuse with a one-line redirect.
35
36	## Frameworks (the analytical engine)
37
38	\| Framework \| Role in the skill \| Where it appears \|
39	\|---\|---\|---\|
40	\| 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) \|
41	\| Cynefin (Snowden) \| Situation classifier; caps plan confidence and shapes the posture (probes vs commitments vs stabilization) \| Step 2 (classification) and co

People who liked this also viewed

6 picks

Type

foundation-prioritized-action-plan

486stars64forks

View on GitHub

How to install foundation-prioritized-action-plan?

product-on-purpose/pm-skills/foundation-prioritized-action-plan

$npx -y skills add product-on-purpose/pm-skills --skill foundation-prioritized-action-plan

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	<!-- PM-Skills \| https://github.com/product-on-purpose/pm-skills \| Apache 2.0 -->
2	# Prioritized Action Plan
3
4	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.
5
6	## Identity
7
8	- Foundation skill; produces a reusable PM working-document the user saves and reuses
9	- Single-turn; one action plan per invocation
10	- Read-only tools (Read, Grep); produces markdown output
11	- Recommends a bounded, tiered set of downstream pm-skills (see "Recommendable skill tiers") and never invokes them inline; on explicit confirmation it can hand the plan to `utility-pm-workflow-orchestrator`, which runs them behind its own per-step checkpoints (see "Handoff to the orchestrator")
12
13	## Core principle
14
15	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.
16
17	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.
18
19	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.
20
21	## When to Use
22
23	- The user has input (notes, transcript, executive ask, draft PRD, customer interview, Slack thread, raw situation) and wants a ranked next-action plan
24	- The user is uncertain what to do next and wants a recommendation grounded in their actual context
25	- The user wants a single referenceable artifact that says what is most important, why, and how to execute it
26
27	## When NOT to Use
28
29	- vs `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.
30	- vs `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.
31	- vs `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.
32	- vs `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.
33	- The user wants to generate a specific named artifact (persona, OKRs, journey map): invoke that skill directly.
34	- The input is unrelated to PM work: refuse with a one-line redirect.
35
36	## Frameworks (the analytical engine)
37
38	\| Framework \| Role in the skill \| Where it appears \|
39	\|---\|---\|---\|
40	\| 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) \|
41	\| Cynefin (Snowden) \| Situation classifier; caps plan confidence and shapes the posture (probes vs commitments vs stabilization) \| Step 2 (classification) and co

People who liked this also viewed

6 picks

Type