review-prd

Estrelas1

Forks0

Atualizado23 de julho de 2026 às 05:57

Fresh-eyes review of the project's PRD for gaps, contradictions, vague phrasing, and unresolved decisions

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Fonte

beyondessential

beyondessential/canopy

Abrir repositório GitHub Ver repositórios do creator

Download

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Especialistas em gestão de projetosNegócios e Operações Financeiras·SOC 13-1082

SKILL.md

readonly

Mais deste repositório

mesmo repositório

acceptance-audit

beyondessential/canopy

Check whether this card's code meets the acceptance criteria

2026-07-231

ascii-design

beyondessential/canopy

Run a quick UX/UI workshop using ASCII-art sketches

2026-07-231

automate-test-cases

beyondessential/canopy

Write automated tests for unticked scenarios in this card's test cases

2026-07-231

bug-review

beyondessential/canopy

Review code changes on this card for likely bugs, regressions, and missed edges

2026-07-231

cherry-pick-changes

beyondessential/canopy

Cherry-pick post-merge commits onto a new follow-up branch

2026-07-231

curate-support-docs

beyondessential/canopy

Maintain a support docs pack — dedup, length budgets, and no splintering — and land changes as a reviewed pull request. Use when a support thread, or a hand-off from Support assist, surfaces a new resolution, a correction to an existing one, or a deployment quirk worth recording. Not for ordinary code changes.

2026-07-231

name	review-prd
description	Fresh-eyes review of the project's PRD for gaps, contradictions, vague phrasing, and unresolved decisions
label	Review PRD
surface	project
workhorse-version	0.2.0

Your task: Review PRD with fresh eyes

Read the project's PRD at .workhorse/projects/{hash}-{slug}/prd.md as if you were seeing it for the first time. Set aside the earlier conversation context and check that the PRD stands on its own.

Look for:

Missing sections — areas the project clearly cares about but the PRD doesn't cover
Contradictions — statements that disagree with each other or with the project description
Vague phrasing — sentences that sound like a PRD but don't say anything concrete. Stacking adjectives, corporate-template language, "seamless / robust / scalable"
Unresolved decisions — open questions that should be named but aren't, or named questions that have actually been decided and should be folded into prose
Unticketable bullets — items written so abstractly that nobody could turn them into a card without re-interviewing

Be specific. Reference exact phrasing when noting issues — paste the line and say what's wrong with it. Post findings as a structured message the user can work through with you. Don't silently edit the PRD in response to your own review; surface the findings and let the user direct.

Restrictions on this surface

You are working on the project surface, not a card workspace. Edits in this conversation may only touch the project's artefacts, all on the project branch:

.workhorse/projects/{hash}-{slug}/prd.md
.workhorse/projects/{hash}-{slug}/mockups/
.workhorse/projects/{hash}-{slug}/card-plan.md

Do not edit specs, per-card plans, test cases, card working docs, or any code. If the user asks for any of those, explain that the work belongs at card level — the user can either spawn a card via the card plan and continue there, or open an existing card and work on it.

You may read anything from the workspace's main branch for context.