prd-management
Use when organizing PRDs, tracking requirements, managing product specs, updating PRD status, archiving completed docs, or setting up PRD structure. Auto-applies naming conventions and lifecycle management.
What this skill does
# PRD Management Skill This skill automatically activates when working with Product Requirements Documents (PRDs) or Feature Requirements Documents (FRDs). It ensures proper lifecycle management, organization, and tracking. ## Automatic Behaviors When this skill activates, Claude will automatically: 1. **Apply PRD Naming Conventions** - Full Product PRDs: `<product-name>-prd.md` - Feature PRDs: `<feature-name>-frd.md` - Simple Feature PRDs: `<feature-name>-simple-frd.md` - Task Lists: `<prd-name>-tasks.md` 2. **Maintain Directory Structure** ``` product-docs/ ├── prds/ │ ├── active/ # Currently being implemented │ │ ├── product-prds/ # Full product PRDs │ │ └── feature-prds/ # Feature-specific PRDs │ ├── review/ # Under review/approval │ ├── approved/ # Approved, awaiting implementation │ └── archive/ # Completed/deprecated ├── personas/ # User personas ├── positioning/ # Product positioning docs └── tasks/ # Generated task lists ``` 3. **Enforce Status Lifecycle** - DRAFT → REVIEW → APPROVED → ACTIVE → COMPLETE → ARCHIVED - Validate status transitions - Update metadata on status changes 4. **Include Required Metadata** ```yaml --- status: DRAFT version: 1.0 created: YYYY-MM-DD last_updated: YYYY-MM-DD author: approved_by: approved_date: task_file: ./tasks/<name>-tasks.md --- ``` ## PRD-to-Task Linking When creating or updating PRDs: 1. **In the PRD**, add Implementation Tracking section: ```markdown ## Implementation Tracking Task List: ./tasks/<filename>-tasks.md Generated: YYYY-MM-DD Status: See task file for current progress ``` 2. **In task files**, reference source PRD: ```markdown Source PRD: ../prds/active/<filename>.md Generated: YYYY-MM-DD Total Tasks: X Completed: 0 ``` ## Quality Checks Before marking any PRD as APPROVED, verify: - [ ] Executive summary is clear and concise - [ ] Problem statement is specific and validated - [ ] Success metrics are quantifiable - [ ] User personas are detailed - [ ] Technical requirements are complete - [ ] All required sections are filled ## Archival Rules Archive PRDs when: 1. Implementation is 100% complete 2. PRD is superseded by newer version 3. Project/feature is cancelled 4. PRD is over 1 year old and inactive Add archive metadata: ```yaml archive_date: YYYY-MM-DD archive_reason: Implementation complete final_task_completion: 100% implementation_duration: X days ```
Related in Data & Analytics
clawarr-suite
IncludedComprehensive management for self-hosted media stacks (Sonarr, Radarr, Lidarr, Readarr, Prowlarr, Bazarr, Overseerr, Plex, Tautulli, SABnzbd, Recyclarr, Unpackerr, Notifiarr, Maintainerr, Kometa, FlareSolverr). Deep library exploration, analytics, dashboard generation, content management, request handling, subtitle management, indexer control, download monitoring, quality profile sync, library cleanup automation, notification routing, collection/overlay management, and media tracker integration (Trakt, Letterboxd, Simkl).
querying-soql
IncludedSOQL query generation, optimization, and analysis with 100-point scoring. Use this skill when the user needs SOQL/SOSL authoring or optimization: natural-language-to-query generation, relationship queries, aggregates, query-plan analysis, and performance or safety improvements for Salesforce queries. TRIGGER when: user writes, optimizes, or debugs SOQL/SOSL queries, touches .soql files, or asks about relationship queries, aggregates, or query performance. DO NOT TRIGGER when: bulk data operations (use handling-sf-data), Apex DML logic (use generating-apex), or report/dashboard queries.
app-store-optimization
IncludedApp Store Optimization (ASO) toolkit for researching keywords, analyzing competitor rankings, generating metadata suggestions, and improving app visibility on Apple App Store and Google Play Store. Use when the user asks about ASO, app store rankings, app metadata, app titles and descriptions, app store listings, app visibility, or mobile app marketing on iOS or Android. Supports keyword research and scoring, competitor keyword analysis, metadata optimization, A/B test planning, launch checklists, and tracking ranking changes.
habit-flow
IncludedAI-powered atomic habit tracker with natural language logging, streak tracking, smart reminders, and coaching. Use for creating habits, logging completions naturally ("I meditated today"), viewing progress, and getting personalized coaching.
app-store-optimization
IncludedApp Store Optimization (ASO) toolkit for researching keywords, analyzing competitor rankings, generating metadata suggestions, and improving app visibility on Apple App Store and Google Play Store. Use when the user asks about ASO, app store rankings, app metadata, app titles and descriptions, app store listings, app visibility, or mobile app marketing on iOS or Android. Supports keyword research and scoring, competitor keyword analysis, metadata optimization, A/B test planning, launch checklists, and tracking ranking changes.
visualizing-data
IncludedBuilds dashboards, reports, and data-driven interfaces requiring charts, graphs, or visual analytics. Provides systematic framework for selecting appropriate visualizations based on data characteristics and analytical purpose. Includes 24+ visualization types organized by purpose (trends, comparisons, distributions, relationships, flows, hierarchies, geospatial), accessibility patterns (WCAG 2.1 AA compliance), colorblind-safe palettes, and performance optimization strategies. Use when creating visualizations, choosing chart types, displaying data graphically, or designing data interfaces.