@deanpeters
Product manager & former coder who, given enough coffee, connects others, makes good things happen & creates order out of your software development chaos.
77 skills1 repository 7.6K
Map a user's journey into activities, steps, and tasks, then organize the work by priority and release. The skill helps teams define a usable first version, place backlog items in context, and spot missing parts of the experience.
Analyze public reviews, app stores, and forums to identify unmet customer needs, competitor weaknesses, and reasons for switching products. Receive short customer quotes with source links, recurring themes, and hypotheses to validate in interviews.
Turn product management notes or workshop material into a structured skill, or update an existing one. Follow a workflow covering duplicate checks, drafting, validation, catalog updates, and optional ZIP packaging for upload.
Plan the first 90 days as a VP or CPO product leader through organizational interviews, validation, and evidence-based action. Build a people assessment, identify unwritten priorities, and choose three to five changes grounded in what you learn.
Evaluate a proposed pricing change by modeling revenue per customer, conversion, cancellations, and customer acquisition cost recovery. Compare scenarios and receive a recommendation to implement, test, modify, or hold the change, with supporting calculations and risks.
Quickly look up SaaS financial metrics, including recurring revenue and customer acquisition costs. Get definitions, formulas, benchmarks, and warning signs, plus reminders of which metrics matter when reviewing features, pricing, acquisition channels, or business health.
Create a clear statement of your product’s market position using Geoffrey Moore’s framework. Define the target customer, unmet need, product category, customer benefit, and meaningful differences from the alternatives buyers actually consider.
Turn research notes and discussions into a PRD, a product requirements document for development teams. Connect customer problems, target users, proposed solutions, and success metrics, while documenting acceptance criteria, excluded work, dependencies, and unresolved questions.
Turn product management notes, frameworks, or rough ideas into a complete SKILL.md draft. Guided questions help choose the skill type, narrow its purpose, and organize instructions, examples, and common mistakes into the required structure.
Map a market from the buyer's perspective, covering segments, established companies, alternatives, and emerging entrants. Produce a sourced overview that distinguishes facts from assumptions and tests whether apparent gaps represent opportunities or weak demand.
Design workflows where specialized AI agents share recurring product management tasks. Define each agent’s role, required information, handoffs, and human review points, then create monitoring and evaluation plans for the overall workflow.
Assess a product that has stopped growing and compare extending it, replacing it, or retiring it. Guided questions separate customer demand from cost and technology pressures, producing a reasoned recommendation that may also favor continued operation without investment.
Create a customer journey map showing actions, contact points, emotions, success measures, and responsible teams at each stage. Use it to identify frustrating experiences, compare improvement opportunities, and build a shared view across departments.
Turn a major product initiative into a testable hypothesis with a clear target user and expected outcome. Define small experiments, measurable success criteria, and an evaluation timeframe before committing to full development.
Evaluate whether a product feature deserves investment by comparing revenue or retention benefits with development and ongoing costs. Receive calculations, payback estimates, and recommendations that account for strategic value and uncertain assumptions.
Work through eight canvas sections to clarify a business problem, target users, desired outcomes, and possible solutions. Turn assumptions into testable hypotheses and choose the smallest experiment to investigate the most important uncertainty before development.
Work through up to five adaptive questions to clarify your product’s customers, unmet needs, category, benefits, and competitive differences. Turn the answers and supporting evidence into a positioning statement and a concise summary for stakeholder review.
Assess whether to retire a product or feature by reviewing customers, revenue, commitments, and migration options. Get a reasoned recommendation to proceed, wait, or maintain it with limited investment, plus an appropriate effort level.
Review a product or AI idea across ten internal and external risk areas. Identify useful tests and measurements, separate immediate actions from ongoing monitoring, and produce a prioritized risk register with concrete next steps.
Turn stakeholder requests into measurable goals, customer problems, possible solutions, and experiments. Through guided discussion, compare feasibility, expected impact, and customer fit to choose a proof of concept: a small test of a proposed solution.
Compare a previous PESTEL analysis of political, economic, social, technological, environmental, and legal factors with current evidence. Identify meaningful changes and broken assumptions, then summarize their implications for strategy and product plans with sources.
Compare current competitor evidence with a previous research snapshot and report only meaningful changes, with sources and dates. Flag sales comparison materials, positioning, pricing analysis, or roadmap assumptions that need updating during recurring monitoring.
Guide a product retirement through six phases, from the initial decision to closure and review. Scale the process to its impact, coordinate supporting skills, and identify missing steps when a retirement is already underway.
Structure customer research around what people want to accomplish, the difficulties they face, and the benefits they seek. Explore practical tasks, social perceptions, and emotions to clarify unmet needs and guide product positioning or priorities.
Is this your account? Link GitHub to bring it onto your creator page (Japanese)