scope
Cut scope to ship something meaningful within constraints. Favor a complete small thing over an incomplete big thing.
Step 1: List All Requirements
Collect every feature, requirement, and "wouldn't it be nice if" into a flat list. If the user provided a PRD or feature set, extract items from it. If not, ask.
Each item should be a concrete, shippable unit — not a theme. Break down anything vague ("improve onboarding") into specific deliverables ("add welcome wizard", "send day-1 email", "add progress indicator").
Step 2: Apply the Core Job Test
For each item, ask: "If we shipped without this, would the core job still get done?"
- Yes → Nice-to-have. Move it down.
- No → Must-have candidate. Keep it.
Be honest. "Get done" means the user can complete the primary task, even if it's manual, ugly, or slow. A to-do app without drag-and-drop reordering still lets people track tasks. A to-do app without the ability to add tasks does not.
Step 3: Categorize into Tiers
More from kazdenc/builder-skills
design-brief
One-time setup that gathers design context for your project and saves it to your config file. Run once to establish persistent design guidelines.
30prd
Write a product requirements document from context. Covers problem statement, goals, scope, user stories, success criteria, and edge cases. Use when user says "write a PRD", "product requirements", "requirements doc", "spec this feature", "document requirements", or needs to define what to build and why.
17critique
Evaluate design effectiveness from a UX perspective. Use when user says "critique this design", "review the UX", "give design feedback", "is this good design", "design review", "evaluate this layout", or wants expert evaluative feedback on visual hierarchy, information architecture, and emotional resonance.
14security-scan
Check code for OWASP top 10 vulnerabilities including injection, XSS, auth issues, and secrets exposure. Use when user says "security audit", "check for vulnerabilities", "security scan", "is this secure", "OWASP check", "find security issues", or needs to verify code security before shipping.
13polish
Final quality pass before shipping. Fixes alignment, spacing, consistency, and detail issues. Use when user says "polish this", "final pass", "ready to ship", "fix the details", "pixel-perfect", "almost done", or when a feature is functionally complete but needs refinement.
13api-design
RESTful API design conventions covering URL structure, HTTP methods, error formats, pagination, versioning, and authentication patterns. Use when designing, reviewing, or implementing APIs. Triggers on API design, endpoint structure, REST conventions, or backend architecture tasks.
12