skills/deanpeters__product-manager-skills

mirror of https://github.com/deanpeters/Product-Manager-Skills.git synced 2026-09-14 20:06:57 +08:00

Files

T

Dean Peters 23ede8ccc4 Overhaul prd-development template with per-section coaching, gap tagging, and self-assessment

template.md: Replace bare skeleton with full coaching structure — per-section
Instructions/Steps/Contributing Skills/Activities blocks, inline 🔶 Assumption
and 🔵 Open Question tagging convention, cross-section recommendation prompts
between all 10 sections, and a PRD Self-Assessment diagnostic at the end.
15 skills cross-referenced to their specific sections.

SKILL.md: Update Application section to describe the new template features.

examples/sample.md: Replace stub with worked excerpts demonstrating inline
gap tagging, evidence-backed claims, and a filled-in self-assessment.

commands/write-prd.md: Add assumption tagging, cross-section prompts, and
self-assessment to the Checkpoints list.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

2026-06-25 14:18:40 -04:00

1.5 KiB

Raw Blame History

name, description, argument-hint, uses, outputs

name

description

argument-hint

uses

outputs

write-prd

Create a decision-ready PRD by chaining problem framing, requirements definition, and story scaffolding.

<feature, initiative, or product change>

prd-development

problem-statement

proto-persona

user-story

user-story-splitting

Structured PRD

Core personas and requirements

Initial implementation-ready stories

/write-prd

Generate a PRD that moves smoothly from strategy to delivery.

Invocation

/write-prd Team inbox redesign for faster triage in customer support

Workflow

Define the problem context with problem-statement.
Align user assumptions with proto-persona.
Build the full document using prd-development.
Draft initial stories with user-story.
Split larger items with user-story-splitting.

Checkpoints

Validate scope boundaries before writing requirements.
Keep success criteria measurable and tied to outcome metrics.
Ensure at least one anti-pattern is called out in risks.
Tag every gap inline: 🔶 Assumption (plausible but unvalidated) or 🔵 Open Question (needs discovery).
After each section, review the "Before moving on" cross-section prompt in the template before continuing.
After the final section, complete the Self-Assessment: strongest section, weakest section, top assumptions to validate, and recommended next step.

Next Steps

Run /plan-roadmap to sequence delivery.
Run /prioritize if scope exceeds current capacity.

1.5 KiB Raw Blame History