Results for “release-planning”
10 skills
deanpeters roadmap-planning
Guide product managers through strategic roadmap planning by orchestrating prioritization, epic definition, stakeholder alignment, and release sequencing into a structured process.
5.6k · bundle
deanpeters press-release
Draft an Amazon-style press release to define customer value and align stakeholders before building a product or feature.
5.6k · bundle
deanpeters user-story-mapping-workshop
Run a user story mapping workshop with adaptive questions and a structured map output, generating backbone activities, user tasks, and release slices for a workflow.
5.6k · bundle
akillness task-planning
Turns vague features, bug clusters, roadmap items, or launch work into an execution-ready planning packet by choosing the right packet type, separating discovery from delivery, and making blockers, dependencies, and the next move explicit.
42 · bundle
More results
pwdev-solucoes flow-product
Creates an approval-gated product requirements document or decomposes an approved PRD into a traceable roadmap, covering product-level problems, new initiatives, multi-feature scope, PRDs, release outcomes, and roadmap planning.
2 · bundle
phuryn sprint-plan
Plan a sprint by estimating team capacity, selecting and sequencing stories, and identifying risks.
22.6k
phuryn create-prd
Create a comprehensive Product Requirements Document using an 8-section template covering problem, objectives, segments, value propositions, solution, and release planning.
22.6k
tangchunwu create-prd
Create a Product Requirements Document using a comprehensive 8-section template covering problem, objectives, segments, value propositions, solution, and release planning. Use when writing a PRD, documenting product requirements, preparing a feature spec, or reviewing an existing PRD.
1
peteedoo create-prd
Create a Product Requirements Document using a comprehensive 8-section template covering problem, objectives, segments, value propositions, solution, and release planning. Use when writing a PRD, documenting product requirements, preparing a feature spec, or reviewing an existing PRD.
0
theheavenlyd3mon neckbeard
Use when asked to fix, build, refactor, review, verify, or release software and the work is non-trivial — including delivering a change request (issue, ticket, or request) from intake through planning, gates, implementation, review, verified PR, and authorized post-merge release. neckbeard routes the change through framing, discovery, design, implementation, review, verification, delivery, and learning — choosing the smallest *safe* intervention, proving it at the real delivery boundary, and leaving an inspectable evidence ledger. For change-request / issue-to-PR work, conditionally loads a 9-phase journey with gates, delivery packet, and lifecycle integration. Composes specialist catalog skills rather than replacing them. Not a persona, not a '10x developer' prompt, not a LOC-minimizer. The journey is not loaded for plain fixes, refactors, or reviews that lack an issue/ticket trajectory.
28 · bundle