@phuryn
AI PM Coach, ex-CPO, Builder | 400K+ Follow
88 skills7 repositories 28.3K
Create a concise sales reference comparing your product with a specific competitor. Organize product and pricing differences, strengths on both sides, responses to common objections, and win/loss patterns into a Markdown document for use during sales conversations.
Use customer research, surveys, and usage data to define an ideal customer profile: the customers most likely to gain value, stay, and expand. Summarize their characteristics, buying behavior, goals, needs, and fit criteria to guide sales and marketing priorities.
Analyze reviews, surveys, and other user feedback by user group. Summarize satisfaction scores, recurring complaints, positive themes, and the goals users want to achieve, then recommend product improvements based on frequency, severity, and business impact.
Turn survey responses, interviews, and other research data into three distinct user personas. Each profile explains the outcome users seek, their main difficulties, desired benefits, an unexpected behavioral insight, and how well the product meets their needs.
Plan low-effort experiments to check assumptions about an existing product before building a feature. Compare prototypes, A/B tests, and other methods, with a clear assumption, procedure, metric, and success threshold for each experiment.
Choose one North Star Metric, a central measure of customer value, and three to five supporting measures that influence it. Classify the business by how customers use it and assess the proposed metric against seven criteria.
Map project stakeholders by their influence and interest, then create a communication plan for each group. Specify update frequency, channels, and key messages, while identifying competing interests and suggesting ways to align people across teams.
Build a sprint plan for a short development cycle using team availability and recent delivery history. Select work that fits capacity, sequence dependent tasks, identify owners and risks, and reserve room for unexpected work.
Turn user stories and acceptance criteria into detailed test scenarios. Define objectives, starting conditions, user roles, actions, and observable results, including invalid inputs and boundary cases, so a quality assurance team can carry out the checks.
Turn development tickets, product requirements, or internal changelogs into release notes users can understand. Organize updates into features, improvements, and fixes, explain their benefits, and highlight changes that require users to take action.
Create a customer interview guide focused on past behavior, current problems, and desired outcomes. Adapt questions to research goals and available time, with follow-up prompts and a note-taking template to capture findings consistently.
Rewrite a feature-based roadmap around the changes customers and the business should experience. The result pairs each initiative with an outcome statement, success metrics, sequencing notes, and context connecting the plan to company strategy.
Explore five ways to position a product against competitors. Review five leading competitors, identify gaps in their messaging, and develop positioning statements with audience rationale, supporting messages, and the product advantages behind each idea.
Turn everyday questions into SQL queries, the commands used to retrieve and summarize database records. Uses your database structure and platform to produce queries with explanations, performance notes, and optional validation scripts.
Turn meeting transcripts or notes into structured summaries with dates, participants, topics, and decisions. Capture action items with owners and deadlines, highlight unresolved questions, and save the result as a Markdown document for sharing.
Review a product plan by imagining a failed launch and tracing possible causes. Separate real risks, overblown concerns, and unspoken worries, then define mitigation actions, owners, and deadlines for issues that must be resolved before launch.
Analyze user feedback and usage data to identify at least three customer groups based on behavior, goals, and unmet needs. Build profiles covering pain points, product fit, and priorities for serving each group.
Review code changes or a repository for actionable bugs by tracing how components interact. Findings explain reachable triggers, incorrect behavior, consequences, and checked counterarguments. Correctness is the default focus; performance and security can also be selected.
Explore features for a new product through product management, design, and engineering perspectives. Generate five ideas from each viewpoint, then select five priorities with reasoning and assumptions to test before developing the concept further.
Identify untested assumptions behind a new product idea across eight areas, including customer value, usability, business viability, technology, ethics, market launch, strategy, and team. Rate confidence in each assumption and suggest a test, producing a Markdown analysis.
Turn a new feature into user stories: short descriptions of what people need and why. Each story includes a design reference and testable acceptance criteria, with scope intended to fit within one sprint.
Initialize a PM Brain — a markdown-native second brain for a product operator (PM, product lead, founder, or anyone accountable for one product or initiative) doing judgment-heavy work with scattered inputs. Detects greenfield vs. migration mode, runs a focused interview, copies the deterministic scaffold into the working directory, populates placeholders from interview answers, runs a self-test, and commits. Use when invoked via `/pm-brain` or when the user asks to set up a PM Brain.
The English summary is being prepared. Showing the original description.
Review a Python solution against a markdown spec, run it, and report bugs.
The English summary is being prepared. Showing the original description.
Apply the Acme house style to any prose - short sentences, no hype, lead with the answer. Shared across agents.
The English summary is being prepared. Showing the original description.
Is this your account? Link GitHub to bring it onto your creator page (Japanese)