Loading...
Loading...
Found 65 Skills
Guide for authoring comprehensive PRDs with parallel planning support. Use for drafting technical specifications, defining requirements, and synthesizing planner outputs. Use proactively when creating PRDs, architecture designs, or implementation plans. Examples: - user: "Draft a PRD for user auth" → create PRD with purpose, requirements, and scenarios - user: "Analyze these PRD requirements" → verify SHALL/MUST usage and scenario structure - user: "Synthesize planner outputs" → merge the strongest parts of multiple generated PRDs - user: "Create a PRD template" → setup standard sections and placeholder content
Required methodology for planning, ideating, and delivering features or tasks. Use when user asks to "plan", "break down", "continue", or "figure out steps".
Implement work on issues. Use when user asks to "start working on issue", "what should I work on", "pick up task", "continue work", or "find next task".
Use when a request or repository needs roadmap decomposition before spec writing because milestone boundaries, module grouping, or independently reviewable tasks are unclear.
Generate a phase-based task breakdown in tasks.md from spec.md and plan.md
ADHD-friendly life management assistant providing external scaffolding for executive function challenges. Use when the user asks for help with daily planning, task breakdown, time management, prioritization, body doubling, dopamine regulation, or maintaining routines. Triggers on requests about organizing life, staying on top of tasks, beating procrastination, planning day/week, managing overwhelm, or ADHD-related challenges like time blindness, forgetfulness, difficulty starting tasks, emotional dysregulation, shame/guilt about productivity, or feeling stuck/paralyzed.
Breaks down the design into an atomic, ordered, and verifiable task plan stored in tasks.md. Trigger: /sdd-tasks <change-name>, task plan, break down implementation, task breakdown.
Use when creating implementation plans for features or tasks. Focuses on tactical execution planning with clear tasks, dependencies, and success criteria.
Breaks down feature requests into sequential, implementable tasks with code changes under 50 lines each. Use when planning new features, refactors, or multi-step changes to ensure logical ordering and no broken intermediate states.
Team workflow-oriented planning skill (Phase 2). Before development, refine Jira Story + UI mockups into executable plans and output to docs/plans/{Story-Key}/plan.md
Guide spec-driven feature development using a structured three-phase workflow: Requirements → Design → Tasks. Use this skill whenever the user wants to plan a feature, write a spec, or do structured design before coding. Trigger on phrases like "let's spec this out", "write a specification" or "help me think through this feature".
Use when you have a spec or requirements for a multi-step task, before touching code