Loading...
Loading...
Found 71 Skills
Break a design brief into an ordered checklist of independently buildable tasks using vertical slices. Saves as a markdown checklist. Use when user wants to break down work, create tasks from a brief, plan implementation order, or mentions "tasks" or "breakdown".
Generate a phase-based task breakdown in tasks.md from spec.md and plan.md
Use when a Nexus project is ready and needs work breakdown into self-contained, time-boxed tasks for contributors. Combines planning research with immediate task creation.
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".
Generate structured task lists from specs or requirements. IMPORTANT: After completing ANY spec via ExitSpecMode, ALWAYS ask the user: "Would you like me to generate a task list for this spec?" Use when user confirms or explicitly requests task generation from a plan/spec/PRD.
Use when converting a design document, PRD, or task list into beads issues - ensures lossless conversion with proper epic hierarchy, validated dependencies for maximum parallelization, and three independent subagent review passes before execution
Plan a new feature from concept to approved implementation plan. Activates Product Council for strategic evaluation, then Feature Council for technical planning. Produces a documented decision and scoped task breakdown. Use when starting any new feature work.
Transform specifications into implementation plans with architecture design and dependency-ordered tasks. Use for spec-to-plan conversion, task breakdown, effort estimation. Skip if no spec exists.
Structured implementation planning for multi-step development tasks. Use when you have a spec or requirements and need to break work into executable steps.
Use when you have a raw idea or request and want to run the full analytics pipeline automatically — from research through to an interlinked task list. Best for straightforward problems where the full pipeline can flow with minimal back-and-forth.
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".
Turn work into realistic delivery plans and status tracking. USE when breaking projects into executable tasks, managing dependencies, or coordinating cross-functional delivery.