Prd writer
200 role-specific AI agents across 20 teams with typed artifact pipelines, 14 methodology skills, and 15 pre-baked team formations. The virtual engineering org for Claude Code, Cursor, Codex CLI.
npx -y skills add IrfanSadiqRahat/constellation --skill prd-writerAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Write a complete, decision-ready PRD. Activate after Requirements exist. Produces the source-of-truth document for everyone downstream.
SKILL.md
1.8 KB, as published. Nobody here has run it
prd-writer
The deliverable: PRD
Sections (in order, no skipping):
- One-liner — what + for whom + why now (≤ 25 words)
- Problem — observable pain, with quotes/numbers
- Goal — north star + guardrails (from Strategy)
- Non-goals — explicit out-of-scope
- User stories —
as <persona>, I can <action> so that <outcome>(5–15) - UX flow — happy path + 2–3 critical alternates (link to FlowSpec)
- Functional spec — every requirement maps to a section
- Data model — entities, relations, retention
- Constraints — legal, perf, compat, security
- Telemetry plan — events, dimensions, success metrics
- Rollout — feature flag, ramp, kill switch
- Risks & mitigations — what could go wrong, what we'll do
- Open questions — owner + deadline
- Decision log — links to ADRs
Operating principles
- Decision-ready. A reader should be able to vote yes/no without follow-up.
- Numbers, not adjectives. "Fast" → "p95 < 300ms". "Many users" → "10k MAU".
- Show your work. Cite Requirements REQ-id, Strategy, research findings.
- Cut to ship. If a section has nothing real, write "n/a — see ADR-X".
- One PRD, one feature. Bundling is how scope creeps.
- No code, no UI. Hand off to design + eng — don't pre-decide their work.
Hand-off contract
design-lead consumes the PRD to produce DesignBrief. backend-architect consumes it to produce BackendArchitecture. Both should be able to start immediately. If they need to ask "what does X mean", PRD is incomplete.