prd — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited 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.
Create detailed Product Requirements Documents that are clear, actionable, and suitable for implementation.
tasks/prd-[feature-name].mdImportant: Do NOT start implementing. Just create the PRD. Ask only critical questions where the initial prompt is ambiguous.
Focus on:
#### Format questions like this:
1. What is the primary goal of this feature?
A. Improve user onboarding experience
B. Increase user retention
C. Reduce support burden
D. Other: [please specify]
2. Who is the target user?
A. New users only
B. Existing users only
C. All users
D. Admin users only
3. What is the scope?
A. Minimal viable version
B. Full-featured implementation
C. Just the backend/API
D. Just the UIThis lets users respond with "1A, 2C, 3B" for quick iteration.
Brief description of the feature and the problem it solves.
Specific, measurable objectives (bullet list).
Each story needs:
Format:
### US-001: [Title]
**Description:** As a [user], I want [feature] so that [benefit].
**Acceptance Criteria:**
- [ ] Specific verifiable criterion
- [ ] Another criterion
- [ ] Typecheck/lint passes
- [ ] **[UI stories only]** Verify in browser using dev-browser skillRules:
Numbered list:
What this feature will NOT include.
Known constraints, dependencies, integration points.
How will success be measured?
Remaining questions needing clarification.
.md)tasks/prd-[feature-name].md (kebab-case)# PRD: Task Priority System
## Introduction
Add priority levels to tasks so users can focus on what matters most.
## Goals
- Allow assigning priority (high/medium/low) to any task
- Provide clear visual differentiation between priority levels
- Enable filtering and sorting by priority
## User Stories
### US-001: Add priority field to database
**Description:** As a developer, I need to store task priority so it persists across sessions.
**Acceptance Criteria:**
- [ ] Add priority column to tasks table: 'high' | 'medium' | 'low' (default 'medium')
- [ ] Generate and run migration successfully
- [ ] Typecheck passes
### US-002: Display priority indicator on task cards
**Description:** As a user, I want to see task priority at a glance.
**Acceptance Criteria:**
- [ ] Each task card shows colored priority badge (red=high, yellow=medium, gray=low)
- [ ] Typecheck passes
- [ ] Verify in browser using dev-browser skill
## Functional Requirements
- FR-1: Add `priority` field to tasks table ('high' | 'medium' | 'low', default 'medium')
- FR-2: Display colored priority badge on each task card
## Non-Goals
- No priority-based notifications
- No automatic priority assignment
## Technical Considerations
- Reuse existing badge component with color variants
## Success Metrics
- Users can change priority in under 2 clicks
## Open Questions
- Should priority affect task ordering within a column?tasks/prd-[feature-name].md~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.