prd
This skill contains shell command directives (!`command`) that may execute system commands. Review carefully before installing.
Pre-computed context
Current branch: !git branch --show-current 2>/dev/null || echo "unknown"
Recent commits: !git log --oneline -5 2>/dev/null || echo "no commits"
Working tree status: !git status --porcelain 2>/dev/null | head -10 || echo "clean"
Variables
Arguments: $ARGUMENTS
Purpose
Most product-feature rework comes from skipping the what for whom and why layer and jumping straight to how. /prd produces the lockable product intent contract — what we are building, for which users, against what measurable success — before any engineering plan, exploration, or research begins.
This is the product-intent stage. Upstream of exploration, upstream of /planning:plan, and may run before or alongside /interview depending on task shape:
/prd— answers what should we build, for whom, and why. Outcome-focused. Required for new user-facing features, business-driven changes, cross-team initiatives/interview— answers what is the engineering contract for this task. Constraint and acceptance-criteria focused. Required whenever intent is fuzzy or underspecified, regardless of source- Complementary, not redundant. A product feature usually wants both:
/prd(product intent) →/interview(engineering contract) → exploration → research →/design→/planning:plan. Engineering-internal work skips/prdentirely