Results for “prd-to-production”

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.

Turns the current conversation context and codebase understanding into a PRD and publishes it to the project issue tracker with a triage label.

prd-writer

Synthesize the current conversation and codebase context into a Product Requirements Document and publish it to the project's issue tracker.

PRD Creation

Breaks a PRD into a multi-phase implementation plan using tracer-bullet vertical slices, saved as a local Markdown file in ./plans/.

Turn the current conversation into a PRD and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.

Generate a Product Requirements Document (PRD) for a new feature. Use when planning a feature, starting a new project, or when asked to create a PRD. Triggers on: create a prd, write prd for, plan this feature, requirements for, spec out.

Creates a comprehensive Product Requirements Document that aligns stakeholders on what to build, why, and how success will be measured. Use when specifying features, epics, or product initiatives for engineering handoff.

Create, validate, or edit product requirements documents. Tri-modal. Phase 2 Planning

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.

Turn the current conversation into a PRD and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.

Synthesizes the current conversation into a PRD and publishes it to the project issue tracker with a triage label.

Turn the current conversation context into a PRD and submit it as a GitHub issue. Use when user wants to create a PRD from the current context.

Creates an approval-gated product requirements document or decomposes an approved PRD into a traceable roadmap, covering product-level problems, new initiatives, multi-feature scope, PRDs, release outcomes, and roadmap planning.

Turns a raw idea, brain dump, or conversation into a complete PRD with mandatory acceptance criteria and measurable success metrics. Extracts the problem, target users, and jobs-to-be-done, runs a quick competitive scan (web if available, logged as a gap if not), drafts the full PRD (problem, personas, user stories.

Translates high-level ideas into detailed Epic-level Product Requirements Documents (PRDs) that serve as the single source of truth for engineering teams.

Generate comprehensive Product Requirements Documents (PRDs) for software systems and AI-powered features, including executive summaries, user stories, technical specifications, and risk analysis.

Turn the current conversation into a PRD and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.

This skill should be used when the user asks to "create PRD", "write product requirements document", or mentions "PRD", "product requirements document".

Generate structured PRD from conversation context without interviewing the user

Generates a structured Product Requirements Document (PRD) for a new feature, including clarifying questions, user stories, functional requirements, and success metrics.

Reverse-engineer any codebase into a complete Product Requirements Document (PRD). Analyzes routes, components, state management, API integrations, and user interactions to produce business-readable documentation detailed enough for engineers or AI agents to fully reconstruct every page and endpoint. Works with frontend frameworks (React, Vue, Angular, Svelte, Next.js, Nuxt), backend frameworks (NestJS, Django, Express, FastAPI), and fullstack applications. Trigger when users mention: generate PRD, reverse-engineer requirements, code to documentation, extract product specs from code, document page logic, analyze page fields and interactions, create a functional inventory, write requirements from an existing codebase, document API endpoints, or analyze backend routes.

Synthesizes the current conversation and codebase context into a structured PRD and publishes it to the project issue tracker with a triage label.

Gated PRD generation — interrogates problem, user, and metric before drafting; refuses to draft on unknowns. Usage: /prd <feature-or-problem>

Creates decision-focused PRDs and product specs — the kind that make explicit decisions, not document hopes. Make sure to use this skill whenever someone asks to write, review, draft, or improve any product document, including PRDs, feature specs, requirements docs, or product specifications. Trigger even when the user doesn't say "PRD" explicitly — phrases like "write a spec for X", "define requirements for Y", "what should my PRD include", "help me document this feature", or "my spec feels too vague" all apply. Do not attempt to write the PRD directly without consulting this skill. Produces 5-stage PRDs with behavior contracts (15-25 labeled examples for AI features), measurable success metrics with specific thresholds, precise rollout plans with percentages and ramp gates, and antipattern detection. Works for AI features, SaaS, mobile apps, and traditional software.

Run a structured discovery interview and produce a complete, developer-ready Product Requirements Document. Load when the user asks to write a PRD, create product requirements, document a feature, define user stories with acceptance criteria, or turn a rough idea into a formal product requirements document. Also triggers on "document this feature", "write requirements for", "create a one-pager", "turn this into a PRD", "I need a PRD for", or any request to produce a structured product document for stakeholder alignment or engineering handoff. Supports Full PRD, Lean PRD, and One-Pager formats. Note: for executable feature specifications (FRs, NFRs, ACs as Given/When/Then consumable by AI coding agents), route to `feature-spec` instead — PRDs frame the product, feature-specs encode the implementable contract.

专业级产品需求文档（PRD）生成器。自动生成包含 UML 用例模型、详细用例规格说明、数据字典、交互设计、UI 规范的完整 PRD。 Use when: 用户提到写PRD、写产品需求文档、产品设计、产品规划、新功能需求分析、用例分析、用例建模时触发。 NOT for: 已有完整需求文档的润色、代码生成、技术架构设计、数据分析报告。

Prd

Create, update, or validate a PRD. Use when the user wants help producing, editing, or validating a PRD.

Create a Product Requirements Document using a comprehensive 8-section template covering problem, objectives, segments, value propositions, solution, and release planning. Use when writing a PRD, documenting product requirements, preparing a feature spec, or reviewing an existing PRD.

Guide product managers through structured PRD creation by orchestrating problem framing, user research synthesis, solution definition, and success criteria into a cohesive document.

Generate Product Requirements Documents through structured conversation for any project. Use when starting a new feature, documenting requirements, creating specs before implementation, or needing clarity on scope and success criteria.