trellis-verify-prd

Audits prd.md against original requirement documents via forward and reverse coverage checks.

Updated Jun 8, 2026
One-click install
npx skills add https://github.com/SilentFlower/flower-trellis --skill trellis-verify-prd-silentflower
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: trellis-verify-prd
Source: https://github.com/SilentFlower/flower-trellis/tree/main/enhancements/0.5/.agents/skills/trellis-verify-prd
Command: npx skills add https://github.com/SilentFlower/flower-trellis --skill trellis-verify-prd-silentflower

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Generated PRDs often drift from the original requirement document through omissions, misinterpretations, embellishments, or mismatched UI copy, and this Skill systematically detects and corrects every such deviation before development begins. ## Core Features & Use Cases - Forward Accuracy Check: Compares each PRD entry against the original requirement document item by item, classifying deviations as accurate, wording drift, misinterpretation, missing, or over-embellished. - Reverse Coverage Scan: Scans the full requirement document for all changes belonging to the current version (including changes embedded mid-paragraph) and verifies each is covered by the PRD. - UI Copy Verification: Flags any user-visible text (buttons, toasts, dialogs, table headers, placeholders) that does not match the source document verbatim. - Use Case: After generating a PRD with trellis-brainstorm, run this Skill against the original requirement spec to produce a deviation report, then apply confirmed corrections to prd.md. ## Quick Start Verify the current task's prd.md against the original requirement document and report all missing, misinterpreted, or mismatched items.

Frequently Asked Questions about trellis-verify-prd

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

FAQPage Schema
How do I verify a PRD against original requirements?▼

Provide the original requirement document (file, pasted text, or path) and run the verification on the task's prd.md. The Skill performs a forward item-by-item comparison plus a reverse coverage scan, then outputs a classified deviation report.

What types of PRD deviations does this check detect?▼

It classifies deviations as accurate, wording drift, misinterpretation, missing content, or over-embellishment. UI-visible copy such as button labels, toasts, and placeholders must match the source verbatim, otherwise it is flagged as misinterpretation.

Can it verify a PRD without the original requirement document?▼

No. The Skill explicitly refuses to run without an authoritative source document, since verification without a reference is meaningless. It will ask you to paste the requirements, provide a file path, or describe key points.

How does the reverse coverage scan find hidden requirement changes?▼

It scans the full document text for change markers, requirement tables, version sections, and action words like add, change, or adjust, including changes embedded mid-paragraph. Each change is mapped to its requirement unit and cross-checked against PRD coverage.

When should I use trellis-verify-prd versus trellis-check-all?▼

Use trellis-verify-prd after PRD generation and before development to check the PRD against the source requirements. Use trellis-check-all after coding to verify the implementation matches the PRD.