Pawel Huryn

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Preparing sales teams for competitive deals
• Answering questions about a cheaper competitor
• Creating a feature and pricing comparison

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Defining ideal customers from surveys and interviews
• Finding patterns among customers who stay and expand
• Aligning 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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Finding recurring themes across large volumes of user feedback
• Comparing satisfaction across user groups
• Prioritizing product improvements from customer complaints

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Creating three personas from survey responses
• Grouping interview findings by user goals and behavior
• Comparing user needs to guide product decisions

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking feature assumptions before implementation
• Planning prototype usability tests
• Defining metrics and success thresholds for A/B tests

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Choosing a central measure of customer value
• Organizing the metrics a team tracks
• Comparing candidates for a North Star Metric

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Identifying stakeholders before a launch
• Planning updates for executives and teams
• Aligning groups with competing interests

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Preparing a sprint planning meeting
• Estimating capacity around leave and other duties
• Selecting backlog work that fits team capacity

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Writing test cases from user stories
• Preparing acceptance test scenarios
• Checking invalid inputs and boundary cases

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Creating release notes from development tickets
• Turning internal changelogs into user announcements
• Explaining updates that require user 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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Preparing a first customer interview
• Exploring current workflows and frustrations
• Adapting interview questions to a time limit

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Turning a feature list into measurable outcomes
• Connecting roadmap initiatives to company strategy
• Defining success metrics for planned work

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Defining positioning for a new product
• Exploring ways to stand apart from competitors
• Finding gaps in competitor messaging

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Extract users who meet specific activity conditions
• Build revenue reports by region and customer tier
• Create queries from database diagrams

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Creating meeting minutes from transcripts
• Organizing action items by owner and deadline
• Sharing decisions with people who missed the meeting

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking launch plans for possible failure causes
• Separating real risks from overblown concerns
• Surfacing assumptions the team has not discussed

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Finding customer groups within diverse user feedback
• Comparing needs across user groups
• Prioritizing product improvements by customer 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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing changes for bugs before integration
• Investigating state mismatches across components
• Checking whether a fix introduces another defect

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Exploring features for a startup idea
• Comparing ideas from three professional perspectives
• Choosing five ideas to validate first

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking assumptions behind a new product concept
• Reviewing launch channels and messaging assumptions
• Examining technical and team risks together

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Breaking a new feature into backlog items
• Defining testable acceptance criteria
• Sharing user needs alongside design references

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Review a Python solution against a markdown spec, run it, and report bugs.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Apply the Acme house style to any prose - short sentences, no hype, lead with the answer. Shared across agents.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.