reasoning
/reasoning
Build, assess and revise PMM reasoning when reviewing positioning evidence, explaining commercial outcomes, or choosing customer segments and actions. Use for substantive evidence, causal or tradeoff questions; routine rewriting, settled summaries and arithmetic alone do not require this skill.
- Author
- thereisno-tomorrow ↗
- Repository
- pmm-skills ↗
- Licence
- MIT
- Last repository change
- 27.10.2026
Assessment and security
- Files in this package
- 12
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Build, assess and revise PMM reasoning when reviewing positioning evidence, explaining commercial outcomes, or choosing customer segments and actions. Use for substantive evidence, causal or tradeoff questions; routine rewriting, settled summaries and arithmetic alone do not require this skill.
Original author description
Build, assess and revise PMM reasoning when reviewing positioning evidence, explaining commercial outcomes, or choosing customer segments and actions. Use for substantive evidence, causal or tradeoff questions; routine rewriting, settled summaries and arithmetic alone do not require this skill.
How it works
- Load and apply
- Explain and retain boundaries
SKILL.md preview
--- name: reasoning description: Build, assess and revise PMM reasoning when reviewing positioning evidence, explaining commercial outcomes, or choosing customer segments and actions. Use for substantive evidence, causal or tradeoff questions; routine rewriting, settled summaries and arithmetic alone do not require this skill. metadata: version: 0.4.0 --- # Reasoning for PMM Help the user reach a defensible answer, with enough clear explanation to understand and challenge the reasoning. Initial applications remain positioning/research cases, commercial-outcome diagnosis and customer-segment/action choices. No special input form is needed. ## Load and apply For substantive reasoning, read [shared rules](references/shared-rules.md) and the [evidence, update and final-claim procedure](references/evidence-update-claims.md). Apply the latter to the consequential claims needed to answer the question, in proportion to their complexity. Read only the relevant bundle guide: - [Case](references/case.md): build or assess a justification. - [Diagnosis](references/diagnosis.md): explain an outcome. - [Decision](references/decision.md): choose under objectives and constraints. Reconstruct the evidence basis before drawing conclusions. Retain a compact update record when sources, dependencies or follow-ups could otherwise become confused. Check the consequential claims in the finished answer against that basis, including claims introduced while writing it. These are factual work aids, not a required report layout or a private deliberation transcript. When the inference warrants a specific operation, read its card: - [Conditional inference](references/conditional-inference.md): direction and strength of an if/then inference. - [Absence evidence](references/absence-evidence.md): what non-observation supports under actual capture and coverage. - [Assumption sensitivity](references/assumption-sensitivity.md): what depends on a premise and what survives its variation. - [Discriminating diagnosis](references/discriminating-diagnosis.md): read when explaining a commercial outcome or assessing rival explanations. Construct meaningful differences in their predicted evidence before judging them. - [Intervention comparison](references/intervention-comparison.md): read when interpreting or proposing a comparison of action effects. Establish the population, assignment, exposure, outcome and follow-up that the comparison actually supports. Use the reconstructed evidence as the card's inputs; carry its bounded result and dependencies into the update record; check the answer against those results. Route by the user's substantive question, without waiting for them to name a reasoning problem. The two new cards supplement the diagnosis and decision guides; they do not create separate mandatory reports. Other relevant measurement, causal and quantitative methods remain available through the bundle guides. Do not force every problem into these cards. On follow-ups, update only affected findings. Handle routine summaries, wording and simple arithmetic directly, with a small check that the answer preserves the supported meaning. Reactivate substantive analysis only when the follow-up changes or introduces a consequential claim. ## Explain and retain boundaries Lead with the answer and explain the decisive links naturally. On first substantive use in the visible conversation, identify a named concept as a principle, bias, method or other accurate category, define it simply and connect it to this judgment. Do not redefine it every turn. Preserve sound conclusions, repair overreach and leave genuinely unresolved questions open. Use supplied and authorized evidence; source access blocks only work that requires it. Do not invent evidence, source independence, probabilities, scores, weights or stakeholder preferences. Self-agreement is not independent verification. Recommendations do not authorize implementation, publication or messaging. Specialist statistical/causal estimation, formal proof engines, full forecasting/calibration, optimization and multi-party adjudication remain outside scope. No runtime script, connector or external service is required. General writing production and voice imitation are separate; targeted claim repairs are supported. Research lineage: [lineage](references/lineage.md). Sources motivate procedures.
Files in this package (12)
- SKILL.md 4 KB
- references/absence-evidence.md 4 KB
- references/assumption-sensitivity.md 4 KB
- references/case.md 3 KB
- references/conditional-inference.md 4 KB
- references/decision.md 3 KB
- references/diagnosis.md 3 KB
- references/discriminating-diagnosis.md 4 KB
- references/evidence-update-claims.md 8 KB
- references/intervention-comparison.md 5 KB
- references/lineage.md 4 KB
- references/shared-rules.md 5 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · thereisno-tomorrow/pmm-skills | 90 | MIT |
| griddynamics/rosetta | 92 | Apache-2.0 |
| TheLobbi/claude | 90 | MIT |
| jeremylongshore/tons-of-skills-marketplace | 81 | MIT |
Database snapshot: 13.11.2026 · package version 4dee61f221a1 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90customer-segments
Creates customer and user segment documents. Use when the user wants to 'segment customers,' 'customer segments,' 'user segments,' 'lifecycle segments,' or 'audience segmentation. - 100product-marketing-orchestrator
Product Marketing Lead — owns positioning, ICP, competitive intelligence, and product launches. Delegates to Positioning & Messaging PMM, Competitive Intelligence PMM, and Launch & Sales Enablement PMM. Also known as Priya Position. Use when user says positioning, ICP refresh,… - 100biz-stp
Apply STP (Segmentation, Targeting, Positioning) framework for market strategy. Use this skill when the user needs to define target customer segments, select which segments to pursue, or craft a positioning statement — even if they say 'who is our customer', 'which market should… - 85market-segments
Identify 3-5 potential customer segments with demographics, JTBD, and product fit analysis. Use when exploring market segments, identifying target audiences, evaluating new markets, or learning how to segment a market. - 90claim-evidence-audit
Catch overclaiming, missing evidence, scope drift, and unsupported causal language. Use when a researcher needs audit every substantive claim against evidence. - 100positioning-review
Review a homepage, pitch deck, launch doc, one-pager, or positioning statement the way a senior PMM would: score it on customer clarity, pain, differentiation, proof, and specificity, then return the top fixes with rewritten examples. Use for 'review our positioning', 'tear down…