to-prd — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited to-prd (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
This skill takes the current conversation context and codebase understanding and produces a PRD. Do NOT interview the user — just synthesize what you already know.
The issue tracker and triage label vocabulary should have already been provided to you — if not, run /setup-matt-pocock-skills.
A deep module (as opposed to a shallow one) encapsulates a lot of functionality behind a simple, testable interface that rarely changes.
Confirm with the user whether these modules match their expectations. Confirm which modules they want tests written for.
needs-triage label so it enters the standard triage flow.<prd-template>
The problem the user faces, from the user's perspective.
The solution to the problem from the user's perspective.
A LONG numbered list of user stories. Each story should be in the format:
<user-story-example>
</user-story-example>
This list of user stories should be very extensive and cover every aspect of the functionality.
A list of accepted implementation decisions. This may include:
Do NOT include concrete file paths or code snippets. They can become stale very quickly.
A list of accepted testing decisions. Include:
A description of things that are outside the scope of this PRD.
Any additional notes about the functionality.
</prd-template>
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.