PRD structure, writing patterns, and success metric definition. Use when authoring a product requirements document, writing a PRFAQ, or defining success criteria for a development…
Transform PRDs (Product Requirements Documents) into structured XML app specifications optimized for AI coding agents.
Generate a production-grade architecture diagram for Excalidraw from a PRD, focusing on services, data flow, dependencies, observability, security boundaries, and deployment…
Use when turning a PRD or requirements document into a first pass information architecture. Triggers on a pasted or linked PRD plus a request for an IA, sitemap, screen list, or…
Primary pipeline decomposition step after /write-a-prd. Use when a shaped PRD is ready to become implementation-ready slices with boundary maps and dependency order.
Decompose large PRDs, specs, or requirements documents into phased development plans with a master checklist and per-stage implementation files.
Turn a PRD into a multi-phase implementation plan using tracer-bullet vertical slices, saved as a local Markdown file in ./plans/.
Convert an approved PRD into a phase-gated implementation SPEC. User-facing entry point that dispatches to the prd-to-spec babysitter process via /babysitter:call (interactive) or…
Use when translating a PRD, feature spec, or raw product idea into screen-level prompts for web UX generators (Google Stitch, Figma AI, Pencil.dev, Claude Design, v0, or similar).
Разбить план, спецификацию или PRD на независимые задачи для реализации с помощью вертикальных срезов.
Skill untuk membuat PRD dan User Story untuk fitur baru. Output wajib direview PM sebelum lanjut ke Engineering Task.
Break a PRD in .cursor/plans/ into vertical slice markdown issues (tracer bullets), not horizontal layers.
When the user needs to define a product feature, write a product requirements document, or translate an idea into a structured spec. — from h-maki2/claude_sample
把 PRD 第四章「产品范围」按模块拆成禅道研发需求(SR),通过禅道 API 在浏览器会话里批量创建/更新。触发场景:同步禅道 / 建禅道需求 / 把 PRD 提到禅道 / 批量提研发需求 / PRD to zentao / 需求落禅道。关键词:禅道、研发需求、SR、同步需求、批量建需求、提研发需求、zentao。配套姐妹…
Gate 1: Business requirements document - defines WHAT/WHY before HOW. Creates PRD with problem definition, user stories, success metrics.
Explore intent and shape ideas before implementation planning. Use when Codex is asked to brainstorm, ideate, plan a feature/product/workflow, clarify a vague idea, compare…
中文优先：用于产品能力相关任务，帮助识别、设计、实现或验证对应工作流。English keywords: Translate PRD intent, roadmap asks, or product discussions into an implementation-ready capability plan that exposes…
Define user-facing product behavior from validated evidence and approved scope. Use for information architecture, task flows, state and recovery models, interface contracts,…
Use for product development work from PRD to implementation: make technical decisions, stress-test plans, document ADRs or spike/POC findings, break down engineering work, plan…
Write structured product requirements documents (PRDs) with problem statements, user stories, requirements, and success metrics.
Generate a full Product Requirements Document (PRD.md) from accepted PDRs using multi-agent DAG orchestration.
Create a new project with name and description and a somewhat fixed tech stack based on user's requirements
Product consultation for Conductor orchestrator. Clarifies scope, interprets ambiguous requirements, prioritizes features within a track.
Workflow to generate a comprehensive Product Requirements Document (PRD) detailing user stories, acceptance criteria, technical considerations, and metrics.
Strategic product leadership specializing in product strategy, roadmap development, feature prioritization, and cross-functional coordination.
Product management frameworks for translating validated evidence into prioritized backlogs, decisions, specifications, and stakeholder communications.
Define and run product governance — recurring decision rights, intake, portfolio cadences, evidence standards, and cross-functional operating contracts.
AI product photography with studio lighting, lifestyle shots, and packshot conventions. Covers angles, backgrounds, shadow types, hero shots, and e-commerce image require — from…
AI product photography with studio lighting, lifestyle shots, and packshot conventions. Covers angles, backgrounds, shadow types, hero shots, and e-commerce image require — from…
Write a Product Requirements Document — functional requirements, non-functional requirements, epics, and success metrics.
Defines 4 Risks confidence thresholds, OST hierarchy levels, Knowledge Pyramid tiers, and state design requirements.
Design or audit a product-level user-data durability and recovery contract spanning backup, restore, same-product export/re-import, device replacement, version compatibility,…
Model users, jobs, journeys, flows, stories, metrics, glossary, and traceability for a product. Use when product behavior or feature impact needs precise requirements rather than…
Comprehensive product requirements documentation from problem definition through launch planning. Supports both enterprise PRD (full specs, cross-functional alignment) and…
Optional PRD methodology — loaded by the questioner agent when a feature request is vague or complex enough to warrant a structured product spec alongside task.md.
Write a clear product requirements document that defines the problem, scope, requirements, success measures, risks, and open questions.
Writes product sourcing briefs with specifications, quality requirements, MOQs, supplier evaluation criteria, and negotiation guidelines.
Convert a rough idea, meeting notes, or shorthand into a structured Product Requirements Document. Use when the user mentions PRD, requirements, spec, or wants to formalize an…
Use when the task is to operationalize analytics for repeatable, scheduled, or monitored production use.
Senior Architect methodology for greenfield projects — collects business requirements through 1-3 chat phases, then produces 6+1 artifacts in docs/plans/
/ (brief,…
Prevent browser automation from freezing, getting stuck, or waiting excessively during page navigation and interaction.
PRP Framework wizard for PRD-driven development. Gathers requirements, generates PRD, creates implementation plan, and executes with validation loops.
Explore, debug, audit, compare, record, and test live websites with deterministic Playwright scripts and QE workflows.
Scaffold a Ralph-style autonomous agent loop (from snarktank/ralph) adapted for OpenAI Codex CLI; use for PRD-driven iterations (ralph loop, prd.json).
Initialize a PRD (Product Requirements Document) for structured ralph-loop execution
Project-agnostic agent setup wizard for Ralph Orchestra with Quick Start, Standard, and Expert modes
Generate a Product Requirements Document (PRD) for ralph-tui task orchestration. Creates PRDs with user stories that can be converted to beads issues or prd.json for automated…
Plan out the feature set for a release (MVP, v1, v2, or any milestone). Enumerates candidate features, prioritises them against capacity and deadline, publishes a Confluence…
Use when working on learn-likecc and the task involves new requirements, roadmap updates, README updates, git commits, GitHub Pages updates, or release/version changes.
Requirements analysis — problem decomposition, stakeholder scan, requirement structuring. Produces 1-requirements.md (Phase 1 lifecycle doc, NOT the per-task request ticket — for…
Acts as a Requirement Analysis Expert who systematically collects and structures business and technical requirements through effective stakeholder questioning to support practical…
Check architecture coverage against known requirements and ask focused stakeholder questions for missing, ambiguous, or risky requirements.
Feature-Spezifikation schreiben: User Stories, Acceptance Criteria, Edge Cases. Nutze bei: 'neues Feature', 'Anforderungen', 'was brauchen wir', 'spec schreiben', 'User Story'.
Turn stakeholder talk into testable, prioritized requirements. Activate after Strategy exists and before PRD writing.
Stakeholder interviews, PRD structure, and scope definition for software requirements elicitation. Use when gathering requirements, defining project scope, or structuring product…
Requirements gathering and elicitation techniques for business analysis. Use when conducting stakeholder interviews, gathering functional/non-functional requirements, or…
要件定義エージェント。機能要件、ユースケース、ユーザーストーリー、受入基準を定義。キーワード: 要件定義, requirements, ユースケース, use case, ユーザーストーリー, user story, PRD.
从粗需求到可执行 PRD 的方法论,同样覆盖既有模块的优化/重构与产品化。触发场景:① 用户给一句话粗需求(如"做一个 X 模块")需要梳理成 PRD;② 讨论"产品需求文档 / 产品方案 / 新模块设计 / PRD 草稿";③ 讨论或推进既有模块的优化、重构、通用性/标准化提升,或把"项目拼凑 /…
Automatically generate mobile-first responsive CSS/SCSS when creating component styles or mentioning responsive design.
Auditoria leitora estrita. Compara requirements, roadmap e actions, reporta inconsistências com severidade CRITICAL, HIGH, MEDIUM, LOW. JAMAIS altera os artefatos analisados.