trellis-verify-task

Audits task planning documents against original requirements for accuracy, coverage, and cross-layer consistency.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Task planning artifacts (prd.md, design.md, implement.md) often drift from the original requirements document through misinterpretation, omission, embellishment, or inconsistent UI copy, and these errors surface only after development begins. This Skill performs a systematic bidirectional audit of the planning documents against the authoritative requirements before coding starts. ## Core Features & Use Cases - Bidirectional PRD verification: Forward-checks every PRD item against the original requirements and reverse-scans the requirements for uncovered or partially covered changes, including scattered field-level edits. - Cross-layer consistency checks: For complex tasks, verifies design.md and implement.md trace back to the PRD, flags out-of-scope additions, and detects naming, UI copy, and boundary drift across all three documents. - Version planning validation: When a version plan with task candidates and waves exists, checks task cohesion, requirement-to-task-to-wave coverage, wave testability, and creation ordering. - Use Case: After generating a PRD, design, and implementation plan for a feature, run this Skill with the original requirements doc to get one consolidated deviation report and a single confirmed fix list applied in batch. ## Quick Start Ask the AI to verify the current task's prd.md, design.md, and implement.md against the original requirements document and produce one consolidated correction list.

Frequently Asked Questions about trellis-verify-task

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

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

Provide the original requirements document and run this Skill on the task directory. It decomposes the PRD into individual requirement items, traces each back to the source text, and reverse-scans the requirements for uncovered changes, flagging each item as accurate, misworded, misinterpreted, or embellished.

How to check consistency between PRD, design, and implementation documents?▼

For complex tasks containing design.md and implement.md, the Skill traces every design unit and implementation step back to the PRD, then scans all three documents for naming drift, UI copy mismatches, and scope boundary violations, reporting each inconsistency by type.

Does this Skill work for tasks that only have a prd.md file?▼

Yes. Lightweight tasks with only prd.md receive PRD accuracy and coverage checks against the original requirements. The cross-layer design and implementation checks run only when design.md or implement.md exist, so nothing is forced on simpler tasks.

What happens if no original requirements document is available?▼

The Skill refuses to run the accuracy and coverage checks without a source document, since there is no authoritative reference to compare against. It searches the task directory and PRD references first, then explicitly asks you to paste the text, provide a file path, or state the key points.

When should I use this versus checking code against the spec?▼

Use this Skill after the planning documents are written but before development starts, to catch requirement drift early. Checking implemented code against the specification is a separate step handled by a different skill after coding is complete.