pm-release-plan
From the author
Turn a prioritized set of requirements into a committed Pragmatic release plan — themed, sized, and signed. Use when the PM asks to plan a release, define MVP scope, commit a date, build a release charter, or "what goes in this release". Covers MVP done right, themes, the estimation ladder, the market window, and the scope/schedule/resources change levers. Produces a Release Charter as a Markdown or Word .docx artifact.
Install
npx skills add julianoczkowski/product-manager --skill pm-release-plan -a claude-code
Installs to .claude/skills/pm-release-plan/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 77
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- pm-launch-planjulianoczkowski/product-managerBuild a Pragmatic go-to-market launch plan and readiness checklist. Use when the PM asks to plan a launch, GTM, go-to-market, launch readiness, launch checklist, release announcement, or "get sales and marketing ready". Coordinates the Programs and Enablement columns of the framework around a market window. Produces a Launch Plan as a Markdown or Word .docx artifact.Planning★ 52
- pm-product-roadmapjulianoczkowski/product-managerBuild a Pragmatic Institute Product Roadmap that communicates vision, direction and priorities over time — a plan, not a commitment. Use when the PM asks for a "roadmap", "product vision", "what's coming", "phases", "themes over time", or wants to align stakeholders on direction (as distinct from a dated release plan). Frames outcomes and market problems over time-frames, not features on dates. Produces a Product Roadmap as a Markdown or Word .docx artifact.Planning★ 52
- pm-prdjulianoczkowski/product-managerAssemble a full, market-driven Product Requirements Document (PRD) the Pragmatic way — problem-before-solution, evidence-based, persona-first. Use when the PM asks for a PRD, product spec, feature doc, "write the requirements doc", or "put it all together for the team". Pulls in existing personas, positioning, market problems, requirements and use scenarios if present, and gathers anything missing inline. Produces a Product Requirements Document as a Markdown or Word .docx artifact.Planning★ 52
- roadmap-planningdeanpeters/Product-Manager-SkillsPlan a strategic roadmap across prioritization, epic definition, stakeholder alignment, and sequencing. Use when turning strategy into a release plan that teams can execute.Planning★ 7.9K
- prd-templatemohitagw15856/pm-claude-skillsCreate a Product Requirements Document following proven PM template structure. Use when asked to write a PRD, product spec, feature specification, or requirements document for a new feature or product. Produces a complete PRD with problem statement, user stories, functional requirements, technical considerations, and success metrics.Planning★ 1.5K
- create-planDasDigitaleMomentum/opencode-processing-skillsCreate a persistent structured plan (plan.md, phases/, todo.md) when work needs multi-phase or multi-session coordination, durable tracking, or an explicitly requested plan.Planning★ 61
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in