prd-writing — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited prd-writing (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.
Step-by-step workflow for writing clear, actionable Product Requirements Documents. Follow the 6-step process below, using the 25 rules across 7 categories as supporting knowledge.
Follow these steps in order. Skip a step only if the user has already provided that information. Do NOT start drafting before completing discovery.
Determine what you're working with:
disc-codebase-exploration.Ask 3-5 targeted questions to fill knowledge gaps. Use lettered options (A/B/C) when there are clear choices, and open-ended questions when you need free-text answers. Focus on:
Mark unknowns as TBD, not assumptions. See disc-clarifying-questions.
Use the template from struct-prd-template and fill in all 12 sections:
Key rules to follow while drafting:
disc-problem-first)metric-no-vague-language)quality-acceptance-criteria)Show the draft to the user. Ask specifically:
Incorporate feedback, resolve open questions, and update the PRD. Add a review history entry if the PRD will be shared with a team.
Save to docs/prd/{feature-name}.md using kebab-case naming. Include frontmatter:
---
title: Feature Name
status: draft
author: Author Name
created: YYYY-MM-DD
updated: YYYY-MM-DD
---The 25 rules below provide detailed guidance for each step. Read them when you need deeper context.
disc-problem-first - Start with the problem, not the solutiondisc-clarifying-questions - Ask clarifying questions before writingdisc-codebase-exploration - Explore the codebase before draftingdisc-stakeholder-alignment - Align with stakeholders on goals and constraintsstruct-standard-sections - Use standardized PRD sectionsstruct-executive-summary - Write a concise executive summarystruct-prd-template - Provide a ready-to-use PRD templatestruct-output-location - Save PRDs to a consistent file locationstruct-single-source-of-truth - PRD is the definitive reference for a featurereq-user-personas - Define target user personasreq-user-stories - Write user stories with acceptance criteriareq-functional - Define specific functional requirementsreq-non-functional - Define non-functional requirementsscope-out-of-scope - Explicitly define what is out of scopescope-non-goals - List non-goals to protect timelinescope-dependencies - Identify dependencies and blockersmetric-measurable-success - Define measurable success criteriametric-no-vague-language - Replace vague terms with quantifiable benchmarksmetric-kpis - Define 3-5 key performance indicatorstech-data-model - Document the data model and relationshipstech-auth-model - Define authentication and authorizationtech-api-routes - Document API and route structuretech-integration-points - Identify third-party integrationsquality-acceptance-criteria - Write testable acceptance criteriaquality-iterative-review - Iterate with feedback before finalizingFor the complete guide with all rules expanded: AGENTS.md
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.