prd-writer

Generate a hackathon-grade PRD from an idea brief and a short structured interview.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/vinodkrishna221/Q-Trace --skill prd-writer-vinodkrishna221
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prd-writer
Source: https://github.com/vinodkrishna221/Q-Trace/tree/main/.agents/skills/prd-writer
Command: npx skills add https://github.com/vinodkrishna221/Q-Trace --skill prd-writer-vinodkrishna221

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams at hackathons waste hours writing bloated product documents that nobody reads; this Skill turns an idea brief plus a short interview into a tight PRD that acts as the contract between the team and the clock. ## Core Features & Use Cases - Guided Interview: Asks only the questions the idea brief does not answer, one at a time, capped at six, covering demo user, core loop, demo moment, scale gate, constraints, and non-goals. - Five-Question PRD Structure: Produces PROBLEM, USER & CORE LOOP, DEMO NARRATIVE, SCOPE (MUST/SHOULD/CUT/NON-GOALS), and SUCCESS sections with strict traceability between demo beats and scope items. - QUICK and FULL Modes: Outputs a one-page PRD for small fast builds (≤24h, ≤2 builders) or a three-page FULL version, with vocabulary frozen so code, schema, UI copy, and pitch use identical nouns. - Use Case: During a hackathon kickoff, feed the Skill your idea brief, answer its interview questions, and receive a docs/PRD.md that still gives clear orders at hour 20 and feeds a pre-ranked cut list to scope-guard. ## Quick Start Ask the assistant to run the prd-writer skill on your idea brief to produce a hackathon PRD at docs/PRD.md.

Frequently Asked Questions about prd-writer

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

FAQPage Schema
How do I write a PRD for a hackathon project?

Run the prd-writer skill with your idea brief; it interviews you with at most six targeted questions, then produces a PRD covering problem, user and core loop, demo narrative, scope, and success criteria. Output is written to docs/PRD.md using the PRD template.

What is the difference between QUICK and FULL PRD modes?

QUICK mode targets builds of 24 hours or less with at most two builders, collapsing the problem and user sections to three lines and limiting the SHOULD list to three items. FULL mode produces a three-page PRD for larger efforts.

How many interview questions does the PRD writer ask?

It asks a maximum of six questions, one at a time, and only about things the idea brief does not already answer. Topics include the named demo user, core loop, 90-second demo moment, scale gate, hard constraints, and non-goals.

When should I not use a hackathon-style PRD?

Avoid it for long-running products needing detailed market analysis, compliance requirements, or multi-quarter roadmaps. The format deliberately deletes everything beyond five questions and is optimized for demo-driven, time-boxed builds.

How does the PRD enforce scope discipline during a hackathon?

Every MUST item must map to a demo beat and every demo beat to at least one MUST, so orphan features are removed. The CUT list is born pre-ranked to feed scope-guard, and vocabulary is frozen so renaming later cannot drift across code and pitch.