Structured self-promotion

Share your PRD

Anchor one public plan, approve its purpose breakdown, and ask the community one useful human question.

No fetch · no hosted AI · no publication

Fixture-only Showcase journey · no repository read, CLI invocation, publication, or model call

01 Public source
02 CLI breakdown
03 Conversation
04 Exact preview

Anchor the Showcase to one public PRD.

The pilot requires an exact, commit-pinned Markdown PRD in a personal public GitHub repository owned by the signed-in member.

Exact public PRD URLUse a GitHub Markdown blob URL pinned to its full 40-character commit SHA. This fixture compares the URL owner locally; it makes no GitHub request.Source revisionPRD titleI am signed in as the personal GitHub account that owns this public repository.I removed secrets, personal data, customer records, and confidential material.

Create the required purpose breakdown.

Run this versioned prompt in your own GitHub Copilot CLI. CURATIONS does not start the CLI or receive its transcript.

prd-showcase-purpose/0.1

Review the public PRD at the exact URL below.

Public PRD URL: https://github.com/CurationsLA/prd-showcase-fixture/blob/4dccc0179b14c32f05be976a4d02ab4757a02d20/docs/member-profiles-and-prd-showcase.md
Source revision: 4dccc0179b14c32f05be976a4d02ab4757a02d20

Return only this structure:
PRD title:
Purpose in one sentence:
Problem:
Who it is for:
What the proposed product does:
Key decisions already made:
Important non-goals:
Stacks or tools explicitly named:
Open decisions:
Best first discussion question:
Source PRD URL:
Source revision:

Separate facts from assumptions. Do not inspect private files, .env files,
credentials, terminal history, or unrelated repository content.

Copilot CLI output

PRD title: Member Profiles and PRD Showcase
Purpose in one sentence: Give builders a low-friction, source-linked way to promote and discuss a public product plan before entering a deeper Project improvement loop.
Problem: 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.
Who it is for: Builders sharing public product plans, reviewers offering scoped and actionable critique, and readers researching how other people frame software decisions.
What the proposed product does: 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.
Key decisions already made: GitHub proves identity; Showcase can exist without full Project intake; the human question remains first; the breakdown is context, not verification; Roast consent never invites a hosted agent.
Important non-goals: Repository crawling, hosted execution, automatic publication, unrestricted private messages, follower scores, and quality grades.
Stacks or tools explicitly named: GitHub Copilot CLI.
Open decisions: Minimum persisted profile; when a Showcase becomes a Project; safety controls required before a real Roast.
Best first discussion question: Does this make PRD self-promotion useful without turning the Board into a pitch feed?
Source PRD URL: https://github.com/CurationsLA/prd-showcase-fixture/blob/4dccc0179b14c32f05be976a4d02ab4757a02d20/docs/member-profiles-and-prd-showcase.md
Source revision: 4dccc0179b14c32f05be976a4d02ab4757a02d20

Author-approved purpose in one sentenceI reviewed this AI-assisted breakdown and approve the public wording.

Preview exactly what would become public.

The required breakdown is author-approved context, not independent verification. This fixture cannot publish.

Shared Active feed + Showcase masterHuman question first

“Does this make PRD self-promotion useful without turning the Board into a pitch feed?”PRD SHOWCASEOPEN FOR ROAST

Member Profiles and PRD Showcaseshared by@CurationsLA

Give builders a low-friction, source-linked way to promote and discuss a public product plan before entering a deeper Project improvement loop.

AI-assisted purpose breakdown Astro TypeScript GitHub Actions

AI-assisted purpose breakdown

Builder-approved context

Generated in the author’s GitHub Copilot CLI · reviewed and approved by the author · not independent verification

PRD title: Member Profiles and PRD Showcase
Purpose in one sentence: Give builders a low-friction, source-linked way to promote and discuss a public product plan before entering a deeper Project improvement loop.
Problem: 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.
Who it is for: Builders sharing public product plans, reviewers offering scoped and actionable critique, and readers researching how other people frame software decisions.
What the proposed product does: 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.
Key decisions already made: GitHub proves identity; Showcase can exist without full Project intake; the human question remains first; the breakdown is context, not verification; Roast consent never invites a hosted agent.
Important non-goals: Repository crawling, hosted execution, automatic publication, unrestricted private messages, follower scores, and quality grades.
Stacks or tools explicitly named: GitHub Copilot CLI.
Open decisions: Minimum persisted profile; when a Showcase becomes a Project; safety controls required before a real Roast.
Best first discussion question: Does this make PRD self-promotion useful without turning the Board into a pitch feed?
Source PRD URL: https://github.com/CurationsLA/prd-showcase-fixture/blob/4dccc0179b14c32f05be976a4d02ab4757a02d20/docs/member-profiles-and-prd-showcase.md
Source revision: 4dccc0179b14c32f05be976a4d02ab4757a02d20

Exact public source: Read commit-pinned PRD ↗
Source revision: 4dccc0179b14c32f05be976a4d02ab4757a02d20
Review mode: Discussion
Roast consent: Not open for Roast