prd-test-writer

Generates paired PRD and atomic test-case documents with review HTML from confirmed requirements.

Updated Jun 22, 2026
One-click install
npx skills add https://github.com/sliec/shared-files --skill prd-test-writer-sliec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prd-test-writer
Source: https://github.com/sliec/shared-files/tree/main/skills/prd-test-writer
Command: npx skills add https://github.com/sliec/shared-files --skill prd-test-writer-sliec

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve? Writing PRDs and test cases separately often produces documents that drift apart, contain vague test cases, or assert behaviors the code never implements. This Skill runs a structured six-phase collaboration that produces a story-driven PRD and a code-grounded atomic test-case document as a matched pair, plus human-readable HTML review versions kept strictly 1:1 with the Markdown sources. ## Core Features & Use Cases - Dual-document generation: Produces four artifacts per requirement — PRD Markdown and test-case Markdown (fact sources for AI) plus two templated review HTML files (for humans), validated by a scripted MD-to-HTML 1:1 check. - Code-grounded test cases: Every assertion carries a file:line code reference; task-type cases specify exact task names, round counts, verbatim prompts, and per-round expected results. - Adversarial review loop: Runs at least three independent review agents (code reconciliation, coverage completeness, executability and evidence honesty) before freezing documents. - Use Case: After splitting a feature into tasks, ask the agent to write the PRD and test cases; it reads the codebase first, confirms each user story and sample test case with you, then delivers the four frozen documents. ## Quick Start Ask the agent to write the PRD and executable test cases for your already-scoped task, and confirm each stage as it walks through requirement confirmation, code reading, story drafting, and test-case design.

Frequently Asked Questions about prd-test-writer

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

FAQPage Schema
How do I write a PRD and test cases together with an AI agent?

Provide an already-scoped task and let the agent run its six-phase flow: requirement confirmation, autonomous code reading, story-by-story PRD drafting, sample-first test-case alignment, HTML generation, and adversarial review. You confirm each stage before it proceeds.

What makes a test case atomic and executable?

Each case verifies exactly one assertion point, includes all 13 fields, carries literal command and prompt values, and cites a file:line code reference for every asserted field. Task-type cases must specify the task name, round count, and per-round inputs and expected results.

When should I not use this PRD test-case workflow?

Skip it when requirements are still vague or not split into tasks, when UI directions remain unexplored, when changing a small shipped feature, or when you need code written or tests actually executed. It only produces documents, not implementations.

How are the HTML review files kept consistent with the Markdown?

A scripted MD-to-HTML 1:1 validation algorithm compares normalized text, headings, all 13 test-case fields, code blocks, and table cells between the two formats. Any missing or compressed content fails the check and blocks delivery.

Does the skill handle projects without existing code?

Yes. For greenfield features it marks the work as pure-new with a planned-module list, using planned file placeholders instead of fabricated line numbers, so the PRD and test cases stay honest about what does not yet exist.