Project intake supports durable improvement, but builders also need a simple, accountable place to explain a plan, ask one useful question, and invite artifact-focused critique. A bare promotional link does not provide enough context for a useful conversation.
17
Public PRD Showcase
Member Profiles and PRD Showcase
“Does this make PRD self-promotion useful without turning the Board into a pitch feed?”
AI-assisted purpose breakdown
Give builders a low-friction, source-linked way to promote and discuss a public product plan before entering a deeper Project improvement loop.
Generated in the author’s GitHub Copilot CLI · reviewed and approved by the author · not independent verification
Builders sharing public product plans, reviewers offering scoped and actionable critique, and readers researching how other people frame software decisions.
A CURATIONS-native member profile, PRD Showcase discovery and detail, a builder-approved Copilot CLI purpose breakdown, optional Rubber Duck Roast, and a scoped Inbox.
- GitHub proves identity; CURATIONS owns the member experience.
- Showcase can exist without full Project intake.
- The human discussion question remains the social front door.
- The Copilot CLI breakdown is author-approved context, not verification.
- Roast consent never invites a hosted agent.
- Repository crawling or hosted code execution.
- Automatic publication.
- Unrestricted private messages.
- Follower counts or composite reputation scores.
- Treating votes or Roast status as a quality grade.
- What is the smallest useful persisted member profile?
- When should a Showcase graduate into a full Project?
- Which safety controls must be proven before a real public Roast?
Stack context
Tools named by the author
Rubber Duck Roast
Structured critique of the artifact—not the author
- What holds up
- The Showcase and Project lanes have different jobs, and the plan finally says that plainly.
- What quacks
- The first version still risks asking a new member to understand too many states before sharing one useful question.
- Biggest hidden assumption
- That every builder already has Copilot CLI access and knows how to produce a structured breakdown.
- Most expensive ambiguity
- Whether the public profile is a read model or an editable social identity once persistence arrives.
- One falsification test
- Give five builders only the Showcase entry screen and see whether they can reach an exact preview in five minutes.
- Question to answer next
- What is the smallest profile state that makes the Showcase feel owned without delaying publication?
Outcome: deferred until the profile fixture proves how much identity context is actually needed. The critique remains public and the Showcase remains open for Roast.