skill-prd — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited skill-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.
DO NOT call Skill() again. DO NOT load any more skills. Execute directly.
Before writing ANY PRD content, you MUST ask the user these questions:
I need to understand your requirements before creating the PRD.
1. **Target Users**: Who will use this? (developers, end-users, admins, etc.)
2. **Core Problem**: What specific pain point does this solve? Any metrics?
3. **Success Criteria**: How will you measure if this succeeds?
4. **Constraints**: Any technical, budget, or timeline constraints?
5. **Existing Context**: Is this greenfield or integrating with existing systems?
Please answer these (even briefly) so I can create a more targeted PRD.WAIT for user response before proceeding to Phase 1.
If user says "skip" or provides the feature description inline, extract what you can and note assumptions.
Only search if topic is unfamiliar. Limit to 2 web searches max:
Do NOT over-research. 60 seconds max for this phase.
Structure:
After drafting the PRD but BEFORE self-scoring, dispatch the draft to a second provider for adversarial review. A single-model PRD has blind spots — cross-provider challenge surfaces wrong assumptions, uncovered scenarios, and contradictory requirements.
Dispatch the PRD draft to a different provider (Codex, Gemini, or Sonnet as fallback) with this prompt:
"Challenge this PRD. What assumptions are wrong? What user scenarios are missing? What requirements contradict each other? What will the first user complaint be? What risk does this PRD ignore?"
After receiving the challenge:
Adversarial review: appliedSkip with `--fast` or when user requests speed over thoroughness. See prd.md command for full dispatch syntax.
Score against 100-point framework:
Write to user-specified filename or generate based on feature name.
START WITH PHASE 0 CLARIFICATION QUESTIONS NOW.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.