This skill should be used when the user asks to "plan a feature", "create PRD", "interview me about requirements", "define stories", "write a spec", "break down feature into tasks", "create implementation plan", "help me scope this feature", "what questions should I answer", or discusses feature planning. Covers the PRD interview process, spec structure, story atomization, and 4-phase workflow from idea to Dex tasks.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Current branch: !git branch --show-current 2>/dev/null || echo "not in git repo"
Existing plans: !ls plans/ 2>/dev/null | head -5 || echo "none"
The PRD (Product Requirements Document) workflow transforms ideas into atomic, implementable stories through structured interview, research, and specification.
| Phase | Name | Purpose |
|---|---|---|
| 1 | Input Classification | Identify feature name and type |
| 2 | Interview + Exploration | Gather requirements, then run research/expert agents |
| 3 | Spec Write | Create specification with Implementation Stories section |
| 4 | Dex Handoff | Parse stories into Dex tasks |
Key Change: Research and expert agents run after interview completes (blocking). Findings are reviewed before spec writing.
/prd "Add user authentication" # From idea
/prd path/to/existing/code # From codebase
/prd # Interactive discovery
Commitment: "I will ask 8-10+ questions covering: core problem, success criteria, MVP scope, technical constraints, UX flows, edge cases, error states, and tradeoffs."
Cover these areas:
Focus on non-obvious details that will bite during implementation.
Spawn ALL agents in parallel (user waits ~2-3 min):
Research Agents:
prd-codebase-researcher - Existing patterns, files to modifygit-history-analyzer - Prior attempts, why patterns evolvedprd-external-researcher - Best practices, code examplesExpert Agents:
architecture-strategist - System design concernssecurity-sentinel - Auth, data exposure risksspec-flow-analyzer - User journeys, missing flowspattern-recognition-specialist - Codebase consistencySummarize key findings. Ask clarifying questions if gaps revealed.
Write to plans/<feature>/spec.md with this structure:
# <Feature> Specification
## Overview
## Problem Statement
## Success Criteria
## User Stories
## Detailed Requirements
## Technical Design
## Edge Cases & Error Handling
## Open Questions
## Out of Scope
## Implementation Stories
### Story 1: <Title>
**Category:** functional|ui|integration|edge-case|performance
**Skills:** <skill-name>, <skill-name>
**Blocked by:** none
**Acceptance Criteria:**
- [ ] Criterion 1
- [ ] Criterion 2
## Research Findings
## Expert Review Findings
Commitment: "Each story will have ≤7 acceptance criteria, touch ≤3 files, be independently testable, and have no 'and' in title."
Each story must be completable in ONE task (~15-30 min):
Use dex plan to automatically create tasks from the spec:
dex plan plans/<feature>/spec.md
This automatically:
Verify tasks created:
dex status
dex list
Use Dex for execution:
dex status # Dashboard view
dex list --ready # See unblocked tasks
dex start <id> # Claim a task
/complete <id> # Run reviewers and complete
/prd "feature description" # Start from idea
/prd path/to/code # Start from codebase
/cancel-prd # Cancel in-progress PRD
/complete - Complete task with reviewer workflowdex list - View pending tasksdex sync - Sync with GitHub issuesNo reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
This skill should be used when the user asks about "parallel agents", "background tasks", "run_in_background", "non-blocking agents", "check agent progress", "TaskOutput", "retrieve agent results", or discusses running multiple agents concurrently. Covers patterns for launching agents in background, monitoring progress, and retrieving results.
The English summary is being prepared. Showing the original description.
Creates and manages Biome GritQL custom lint rules to enforce coding patterns. Use when creating linter rules, enforcing code conventions, preventing anti-patterns, or when the user mentions Biome, GritQL, custom lint rules, or AST-based linting.
The English summary is being prepared. Showing the original description.
Transform brain dumps into polished blog posts in Nick Nisi's voice. Use when the user wants to write a blog post with scattered ideas, talking points, and conclusions that need organization into a cohesive narrative with Nick's conversational, authentic, and thoughtful tone.
The English summary is being prepared. Showing the original description.
This skill should be used when implementing features from a PRD spec, tracking implementation progress, or resuming work across sessions. Covers Dex task management for PRD story execution, daily workflows, and skill auto-loading.
The English summary is being prepared. Showing the original description.
This skill should be used when the user asks for "browser tests", "playwright tests", "end-to-end testing", "test user flows", "E2E coverage", "integration tests for UI", "page object pattern", "/e2e command", or discusses automated browser testing. Covers the E2E test loop workflow, Playwright patterns, page objects, and selector strategies.
The English summary is being prepared. Showing the original description.
Manage git worktrees using a centralized worktrees folder. Use for parallel development, PR reviews, or isolated work.
The English summary is being prepared. Showing the original description.