Spec to prd

Skill markoblogo/abvx-agent-skills/skills/spec-to-prd

Reviewable capability layer for coding agents. Portable skills, delivery gates, workflow patterns, and verification-first engineering.

Install

npx -y skills add markoblogo/abvx-agent-skills --skill spec-to-prd

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Turn the current conversation, repo understanding, and clarified decisions into a PRD. Use when a vague feature, client request, internal roadmap item, or discovery thread needs to become a durable product artifact. Prefer repo/domain language, explicit scope, implementation decisions, testing decisions, and issue-tracker-neutral output.

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

1.6 KB, as published. Nobody here has run it

Spec To PRD

Convert current understanding into a durable PRD without re-running the whole discovery session.

Workflow

Synthesize what is already known from the conversation and repo.
Use the project's domain language and existing architectural decisions.
Identify the highest useful seams for implementation and testing.
Confirm only the few assumptions that would distort the PRD if wrong.
Produce one PRD artifact:
- issue tracker body;
- markdown file;
- handoff-ready document.

PRD Shape

Include:

problem statement;
solution from the user's perspective;
extensive user stories;
implementation decisions;
testing decisions;
out of scope;
further notes and open assumptions.

Rules

Do not dump file paths unless they are durable anchors.
Do not include code unless a small shape encodes a real decision more precisely than prose.
Keep scope sharp; explicitly name what is out of scope.
If discovery is too weak, route back to rapid-grilling or doc-grounded-grilling first.

Final Report

State where the PRD lives, what assumptions remain, and the best next step: issue breakdown, prototype, or execution.