576 skills · sorted by relevance
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
Turn unclear feature requests or high-impact changes into acceptance criteria: observable conditions for judging completion. Define scope, assumptions, risks, and verification methods, or review an existing specification so another agent or team can implement it with clearer requirements.
Turn an unclear feature idea into a structured specification with goals, boundaries, and testable success criteria. Split broader requests into independent modules when needed, then move through planning, task breakdown, and implementation with human review.
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.
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.
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.
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.
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.
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.
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.
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.
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 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.
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.
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 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 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.
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.
Turn a roadmap phase into executable PLAN.md files through research, planning, and repeated checks. Use requirements documents, verification gaps, or review feedback to shape the plan, then receive a continuation command for phase execution.
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).
The English summary is being prepared. Showing the original description.
Read-only PRD-to-work-item hierarchy planning. Use to turn a PRD into a validated Azure DevOps, GitHub, or Jira handoff.
The English summary is being prepared. Showing the original description.