acedergren/prd
skills/prd/SKILL.md
Use when creating, updating, validating, or phasing a PRD. Drives interactive discovery, technical architecture, phasing DAG, TDD protocol, and dependency analysis. Keywords: PRD, product requirements, feature planning, acceptance criteria, MoSCoW, phasing, requirements document.
$ install --global
skillsauthnpx skillsauth add acedergren/agentic-tools prdInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
4 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
4
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 7, 2026, 9:00 AM72.1s1 file scanned
SKILL.md
- name:
- prd
- description:
- Use when creating, updating, validating, or phasing a PRD. Drives interactive discovery, technical architecture, phasing DAG, TDD protocol, and dependency analysis. Keywords: PRD, product requirements, feature planning, acceptance criteria, MoSCoW, phasing, requirements document.
PRD Skill
Produce drift-proof Product Requirements Documents through iterative discovery.
Output: .claude/reference/PRD.md (living requirements document for the project).
Do NOT load when
- user has a final spec and only wants implementation planning (use
/orchestrateor/prd --to-plan) - task is a code review or repo health check
- request is a lightweight note or issue, not a full requirements document
NEVER
- Never generate a PRD without scanning the codebase first — requirements that contradict existing architecture produce unimplementable specs
- Never write acceptance criteria as "should work correctly" — use Given/When/Then; untestable criteria cannot be verified at phase completion
- Never skip dependency analysis — untracked dependencies produce phases that can't be parallelized safely
- Never batch all discovery questions into one wall of text — max 4 questions per round; users disengage from interrogations
- Never assume a library version — check
package.jsonand npm; version assumptions produce broken phase plans - Never write phasing without dependency arrows — phases must be a DAG; implicit ordering creates unmergeable parallel work
- Never leave
[NEEDS CLARIFICATION]markers in a finalized PRD — they signal a spec that cannot drive implementation
Mode routing
| Argument | Mode | Description |
|---|---|---|
| (empty) | Create | Interactive PRD creation from scratch |
| <feature text> | Create | Start with context, then iterate |
| --update | Update | Incremental update to existing PRD |
| --validate | Validate | Run validation checklist on existing PRD |
| --audit-deps | Audit | Dependency/drift analysis only |
| --to-plan | Plan | Generate orchestrate-ready task plan |
Create mode
Phase 1 — Codebase scan (automatic, before any questions)
Launch an Explore agent to map relevant codebase areas. Read roadmap/changelog for prior decisions. Check for outdated dependencies in scope. This prevents asking questions the codebase already answers.
Phase 2 — Interactive discovery (2–4 rounds, max 4 questions each)
- Round 1: Problem, who, success criteria, personas
- Round 2: MoSCoW priorities, explicit out-of-scope, interactions
- Round 3: Architecture constraints, database, auth, performance
- Round 4 (if needed): Phasing, parallelization risks
Never draft before Round 2. Never ask what the codebase scan already answered.
Phase 3 — Draft
Read template.md. Write to .claude/reference/PRD.md. Mark gaps [NEEDS CLARIFICATION: ...]. Populate Architecture Decisions (AD-N entries). Build phasing DAG with explicit arrows.
Phase 4 — Validation
Read validation.md, run every check. Present pass/fail. Iterate until critical gates pass.
Phase 5 — Finalize
Remove all markers. Commit: docs(prd): add <feature-name> requirements.
Update mode (--update)
- Read existing PRD
- Ask what changed (new requirement, scope change, dependency update)
- Launch Explore agent to detect codebase drift since last PRD update
- Generate diff-style updates:
[ADDED],[CHANGED],[REMOVED],[DRIFT DETECTED] - Present for approval, apply, re-validate
Plan mode (--to-plan)
Transforms PRD phasing into an /orchestrate-ready task plan at docs/plans/<feature-name>-plan.md.
Wave assignment rules:
- Wave 1: Schemas, types, migrations, config (foundation)
- Wave 2: Routes, services, repositories (implementation)
- Wave 3: Wiring, UI, end-to-end flows (integration)
- Wave 4: Error handling, edge cases, docs (polish)
Agent assignment rules:
haiku: Type definitions, config, simple CRUD, test writingsonnet: Business logic, complex integrations, security-sensitive code
Requires V5 (DAG) validation to pass before generating the plan.
Validate mode (--validate)
Read validation.md and run all gates. Print pass/fail with line references.
Audit-deps mode (--audit-deps)
Read drift-prevention.md and run dependency freshness + architectural drift checks.
Scripts
bash scripts/check-prd-assets.sh skills/prd
node scripts/list-prd-phases.js .claude/reference/PRD.md
Arguments
/prd— interactive creation/prd Workflow Designer— start with context/prd --update— incremental update/prd --validate— run validation only/prd --audit-deps— dependency audit only/prd --to-plan— generate orchestrate-ready task plan
Related Skills
acedergren/skills/api-audit
development
VerifiedTrustedCommunity
--- name: api-audit description: "Use when auditing API routes for schema drift, missing auth, or validation gaps. Scans routes against shared TypeScript types to find mismatches, missing middleware, and undocumented endpoints. Read-only — produces a severity-grouped report. Keywords: audit routes, schema drift, auth gaps, missing validation, type mismatch, orphaned schemas. Triggers on "audit API routes" or "find schema drift"." --- # API Route & Type Audit Skill ## When to Use Load this skil
14SKILL.mdUpdated Mar 26, 2026
acedergren/write-natural-swedish
development
VerifiedTrustedCommunity
Use when drafting, translating, polishing, or reviewing Swedish text so it sounds natural, fluent, contemporary, and appropriate for its audience. Triggers include "write better Swedish", "make this sound natural in Swedish", "translate into Swedish", "polish this Swedish", "tech company Swedish", "contemporary Swedish words", "Swedish developer docs", and "avoid Anglicisms".
13SKILL.mdUpdated May 13, 2026
acedergren/shadcn-svelte
development
VerifiedTrustedCommunity
Use when working with shadcn-svelte components, TanStack Table in Svelte 5, or Tailwind v4.1. Covers non-obvious reactivity bugs, library selection trade-offs, and migration pitfalls not in the official docs. Keywords: shadcn-svelte, TanStack Table, Tailwind v4.1, Svelte 5 runes, bits-ui, superforms, data table, svelte-check.
13SKILL.mdUpdated Mar 26, 2026
acedergren/oracle-idcs-org-provisioning
data-ai
VerifiedTrustedCommunity
Use when mapping IDCS claims to org membership after OAuth login succeeds. Covers mapProfileToUser, session.create.before, session.create.after hooks, MERGE INTO upserts, tenant-org mapping, and first-admin bootstrap. Keywords: IDCS groups, org_members, provisioning, session hooks, tenant map, MERGE INTO.
13SKILL.mdUpdated Mar 26, 2026