write-a-prd

Turn rough feature ideas into implementation-ready PRD drafts.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/Canepro/codex-skills --skill write-a-prd-canepro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-a-prd
Source: https://github.com/Canepro/codex-skills/tree/main/skills/write-a-prd
Command: npx skills add https://github.com/Canepro/codex-skills --skill write-a-prd-canepro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Turn rough feature ideas into a concise, implementation-ready PRD through targeted questioning, codebase exploration, and scope tightening.

Core Features & Use Cases

  • Guided PRD creation with structured sections suitable for planning and review
  • Codebase-aware scoping to validate feasibility and dependencies
  • Stakeholder-aligned, testable requirements and success criteria
  • Use Case: turn an early concept into a shared PRD that guides implementation and milestones

Quick Start

Provide a rough feature idea and let the PRD writer generate a concise, implementation-ready PRD draft.

Frequently Asked Questions about write-a-prd

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn a rough feature idea into an implementation-ready PRD?

To turn a rough feature idea into an implementation-ready PRD, you provide the initial concept and the system generates a structured draft through targeted questioning, codebase exploration, and scope tightening. This results in stakeholder-aligned, testable requirements and clear success criteria.

What is codebase-aware scoping in product requirement drafting?

Codebase-aware scoping in product requirement drafting is the process of validating feature feasibility and dependencies by analyzing codebase constraints. It ensures that the generated PRD aligns with technical realities, producing implementation-ready requirements that prevent downstream engineering blockers.

How do I create testable requirements and success criteria for early product discovery?

You create testable requirements and success criteria for early product discovery by applying structured PRD templates and scope tightening. This workflow generates a shared, implementation-ready document that defines clear milestones and guides cross-functional alignment.

Can I use this PRD writer for new feature enhancements across existing codebases?

Yes, you can use this PRD writer for new feature enhancements across existing codebases. It applies codebase exploration to validate dependencies and constraints, ensuring the drafted requirements are implementation-ready and accurately scoped for your team's current technical environment.

What's the best way to tighten scope and align stakeholders during PRD creation?

The best way to tighten scope and align stakeholders during PRD creation is through targeted questioning and structured requirement analysis. This approach exposes codebase constraints early, producing a concise PRD that satisfies cross-functional alignment and implementation milestones.