prd
prd converts feature requests into structured Product Requirements Documents, delivering actionable outcomes and concrete decisions. It's designed for executable documentation tasks, not high-level strategy or planning discussions.
prd generates a structured Product Requirements Document directly from a feature request.
AI-generated summary based on this skill's SKILL.md
Decision gist · record as of 2026-07-27
prd generates a structured Product Requirements Document directly from a feature request. prd converts feature requests into structured Product Requirements Documents, delivering actionable outcomes and concrete decisions. It's designed for executable documentation tasks, not high-level strategy or planning discussions.
Use it when
- Yes.
- prd excels at converting feature ideas into structured product documentation and automating PRD creation from user stories or feature.
Verify before relying
Read SKILL.md below before installing (3 files). Open directory: indexed for reading, not audited.
Install
CoWork-OS/CoWork-OS/prd · repository language: TypeScript
Open directory. Skills are indexed for reading, not audited. Review a skill's body before installing it.
Frequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How does prd generate a structured Product Requirements Document from a feature request?
prd takes informal feature requests and transforms them into structured Product Requirements Documents with actionable outcomes and concrete decisions. It converts raw feature ideas into formal, executable documentation by organizing requirements into clear sections, defining acceptance criteria, and identifying concrete action notes for implementation teams.
Can prd convert feature requests into formal, actionable PRD format?
Yes. prd is specifically designed to convert informal feature requests into formal, actionable PRD format. It takes unstructured user stories or feature specifications and delivers them as properly formatted product requirements documents with executable guidance, making them ready for development handoff.
What is prd best used for in product documentation?
prd excels at converting feature ideas into structured product documentation and automating PRD creation from user stories or feature specifications. It's designed for executable documentation tasks—turning feature requests into actionable requirements with concrete decisions. It's not intended for high-level strategy or planning discussions.
Does prd create executable product requirements with action notes?
Yes. prd creates executable product requirements with concrete action notes built in. It transforms feature specifications into structured documentation that includes not just requirements but also actionable guidance, making the output immediately usable by development and implementation teams.
What license does prd operate under?
prd is released under the MIT license, allowing broad use and modification for both commercial and personal projects.
SKILL.md
Rendered from the published skill. Quoted content, verbatim.
prd
Purpose
Generate a structured Product Requirements Document from a feature request.
Routing
- Use when: Use when the user asks to generate a structured Product Requirements Document from a feature request.
- Do not use when: Do not use when the request is asking for planning documents, high-level strategy, or non-executable discussion; use the relevant planning or design workflow instead.
- Outputs: Outcome from prd: task-specific result plus concrete action notes.
- Success criteria: Returns concrete actions and decisions matching the requested task, with no fabricated tool-side behavior.
Trigger Examples
Positive
- Use the prd skill for this request.
- Help me with prd.
- Use when the user asks to generate a structured Product Requirements Document from a feature request.
- prd: provide an actionable result.
Negative
- Do not use when the request is asking for planning documents, high-level strategy, or non-executable discussion; use the relevant planning or design workflow instead.
- Do not use prd for unrelated requests.
- This request
(truncated - see the full file via the links below)
File tree — 3 files
resources/skills/prd/SKILL.md
resources/skills/prd/references/full-guidance.md
resources/skills/prd/scripts/.gitkeep
Let your AI agent find skills like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 56,283 agent skills by what they can do, searchable in plain language.
wish › “Generate a structured Product Requirements Document from a feature request”
Give your agent the search over MCP, or paste the wish link into any chat. No install? Search from any chat →
Related skills
Project Structure analyzes and explains your project's architecture, helping you understand how your codebase is organized. It delivers concrete, actionable insights into your project layout rather than abstract planning or strategy.
Memory Kit sets up a .cowork/ directory in your workspace to store rules, identity information, long-term notes, daily logs, and heartbeat templates. Use it when you need to establish persistent context and configuration for your work environment.
deliver-prd guides you through building a complete Product Requirements Document that bridges problem understanding and engineering implementation. It structures your specification across goals, functional requirements, scope boundaries, and technical considerations—ensuring teams have clarity on deliverables and success criteria. Use this when you're ready to hand off a feature, epic, or initiative to engineering.
doc-prd generates a Product Requirements Document as Layer 2 of the SDD workflow, converting business requirements into product capabilities, user personas, and measurable success criteria. It structures features and acceptance criteria at the container level, sitting between upstream BRD and downstream EARS artifacts.
Documentation Criteria provides decision matrices and templates to identify which technical documents your feature or change requires. Use it to navigate PRD, ADR, UI Spec, Design Doc, and Work Plan creation based on scope, complexity, and architectural impact.
Requirements Analysis guides you through discovering actual problems versus assumed solutions, clarifying vague needs into testable requirements, and surfacing hidden constraints before they derail your project. It provides diagnostic states, targeted questions, and structured exercises to move from solution-first thinking to validated requirements.