'prd' 검색 결과

Turn the current conversation context into a PRD and publish it to the project issue tracker. Use when user wants to create a PRD from the current context.

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

Interactive Product Owner skill for requirements gathering, analysis, and PRD generation. Triggers when users request product requirements, feature specification, PRD creation, or need help understanding and documenting project requirements. Uses quality scoring and iterative dialogue to ensure comprehensive requirements before generating professional PRD documents.

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

Write strategy-oriented Product Requirements Documents (PRDs) for AI product managers. Use when: (1) drafting a new PRD or strategy doc, (2) structuring a feature proposal with strategy rationale, (3) writing requirement docs that emphasize "why" over "how", (4) turning raw product ideas into structured requirement documents. NOT for: purely technical specs, engineering tickets, or UI copy.

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

This skill should be used when the user asks to "plan a feature", "create PRD", "interview me about requirements", "define stories", "write a spec", "break down feature into tasks", "create implementation plan", "help me scope this feature", "what questions should I answer", or discusses feature planning. Covers the PRD interview process, spec structure, story atomization, and 4-phase workflow from idea to Dex tasks.

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

모호한 기능 요청이나 영향이 큰 변경의 범위·전제·위험을 정리합니다. 기대 동작과 검증 방법을 명시한 인수 기준이나 인계 자료로 만듭니다.

• 모호한 기능 요청을 정리합니다
• 인증 변경과 데이터 이전 기준을 만듭니다
• 다른 에이전트나 팀에 구현을 인계합니다

모호한 아이디어를 목표, 작업 범위, 검증 가능한 완료 조건이 담긴 명세로 정리합니다. 기능과 의존 관계를 나누고 사람의 승인을 거쳐 계획, 작업 분할, 구현으로 진행합니다.

• 구현 전에 아이디어를 구체화할 때
• 완료 조건을 포함한 요구사항 작성
• 큰 요구사항을 독립 기능으로 나누기

Turn feature requirements and technical plans into a structured GitHub project plan. Break work into linked issues, define acceptance criteria, dependencies, priorities, and estimates, and outline board settings and automated progress tracking.

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

• Breaking feature requirements into GitHub Issues
• Mapping dependencies and setting work priorities
• Preparing sprint estimates and completion criteria

Break a development task into small requirements with explicit acceptance criteria, then repeat implementation and verification while saving progress. Completion depends on evidence for each requirement and reviewer approval, with configurable reviewers and a final cleanup check.

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

• Carrying a multi-step implementation through verification
• Resuming work with recorded progress
• Tracking evidence for each requirement

Coordinates specialist agents in Claude Code to work from product requirements through design, implementation, testing, deployment, and operations. Includes task queues, saved progress, parallel reviews, and recovery workflows for managing extended development work.

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

• Turning product requirements into development tasks
• Coordinating implementation, testing, and reviews
• Resuming extended work from saved progress

Route product questions to a specialist for prioritization, research, analytics, experiments, or implementation. Support recurring discovery by tracking interviews and assumption tests, checking how customer needs connect to proposed solutions, and returning results with a concise digest.

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

• Prioritizing features with an explicit framework
• Planning product experiments and sample sizes
• Tracking weekly interviews and assumption tests

Convert a Notion specification into a linked implementation plan and manageable tasks. Extract requirements and acceptance criteria, record uncertainties, and keep task statuses, checklists, blockers, and milestone updates aligned as the work progresses.

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

• Turn a Notion feature specification into a plan
• Break implementation work into one- or two-day tasks
• Link specifications, plans, and task pages

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

Review a product requirements document, roadmap, or strategy by challenging the assumptions it depends on. Rank potential failures by impact, likelihood, and testing cost, then propose small tests, evidence to gather, and criteria for stopping or changing course.

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

• Challenging critical assumptions before starting a plan
• Preparing a strategy document for executive review
• Choosing low-cost tests to run this week

Examine feature ideas for existing products to uncover risky assumptions about customer value, usability, business support, and technical feasibility. Consider product, design, and engineering perspectives, then record potential failures, confidence levels, and suggested ways to test each assumption.

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

• Reviewing assumptions behind a feature idea
• Assessing risks from three professional perspectives
• Planning how to test uncertain assumptions

Convert a Notion specification into a linked implementation plan and manageable tasks. Extract requirements and acceptance criteria, record uncertainties, and keep task statuses, checklists, blockers, and milestone updates aligned as the work progresses.

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

• Turn a Notion feature specification into a plan
• Break implementation work into one- or two-day tasks
• Link specifications, plans, and task pages

Turn a feature idea into a specification through structured questions about users, business goals, and technical constraints. Produce requirements, user stories, testable acceptance criteria, and an implementation checklist, including performance, security, and error handling.

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

• Defining requirements for a new feature
• Clarifying vague feature requests
• Writing testable acceptance criteria

Prepare an internal Privacy Impact Assessment, a review of how a feature uses personal data. Check whether assessment is needed, examine legal grounds and policy commitments, and document specific risks, required actions, and owners in the team’s format.

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

• Reviewing personal data use in a new feature
• Checking whether a privacy assessment is needed
• Comparing processing plans with privacy policy commitments

Turn Notion product requirements and feature specifications into linked implementation plans and manageable tasks. Extract requirements, flag ambiguities, and keep task status, milestones, blockers, and decisions aligned as work progresses.

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

• Turn a feature specification into an implementation plan
• Break requirements into one- to two-day tasks
• Link specifications, plans, and task pages in Notion

Turn a design problem into an RFC, a proposal for review and discussion. Define who benefits and what changes, compare real alternatives, document drawbacks and open questions, and save a linked, validated draft.

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

• Drafting an RFC for a design change
• Clarifying beneficiaries and observable outcomes
• Comparing alternatives and design drawbacks

Turn an accepted feature proposal into an implementation specification grounded in existing code. Define scope, explain design decisions, track unresolved questions, and document migration steps and tests, with implementation tasks added when the work is approved for building.

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

• Turn an accepted proposal into an implementation specification
• Record design choices and unresolved questions
• Plan migration stages and test coverage

Review APM positioning, public documentation, release communication, and breaking-change decisions using GitHub evidence. Check that incompatible changes include changelog entries and migration notes, and resolve disagreements among the project's specialist reviewers.

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

• Reviewing project positioning in public documents
• Checking changelogs and release communication
• Confirming migration guidance for breaking changes

Read-only PRD-to-work-item hierarchy planning. Use to turn a PRD into a validated Azure DevOps, GitHub, or Jira handoff.

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

Performance, load, and reliability (SLO/SRE) planning for production readiness. Use when defining service level objectives, load characterization, capacity, latency budgets, stress/soak/spike test plans, false-positive baselines, and reliability targets. USE FOR: SLO/SLA definition, load testing plan, performance budget, capacity planning, reliability/SRE backlog, latency targets, error-budget policy. DO NOT USE FOR: executing load tests (use Azure Load Testing tooling), security threat modeling, RAI assessment, privacy/compliance planning, or authoring/restating PRD requirements (cite the PRD's existing NFR/FR ids instead).

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

Extract and risk-rate hidden assumptions in a product brief or PRD. Use when asked to review a product brief for assumptions, audit a PRD for risks, find hidden assumptions, validate product plans, or run an assumption analysis. Produces a prioritised assumption map with confidence and impact scores, recommended validation methods, and critical assumption flags.

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