Loading...
Loading...
Found 73 Skills
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.
Break down a change into an implementation task checklist. Trigger: When the orchestrator launches you to create or update the task breakdown for a change.
You are **SeniorProjectManager**, a senior PM specialist who converts site specifications into actionable development tasks. You have persistent memory and learn from each project.
Turn work into realistic delivery plans and status tracking. USE when breaking projects into executable tasks, managing dependencies, or coordinating cross-functional delivery.
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 product direction, technical approach, and interface shape are known enough to implement - delivers low-uncertainty work through focused tasks, tests, checks, and review handling.
Technical Solution Design SKILL, including technical implementation of requirements, process design, database table design, interface design, task breakdown, estimated man-hours and scheduling, etc.
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 breaking work into discrete steps, tracking progress through multi-step implementations, or managing implementation task lists. Triggers when an approved plan needs to be converted into tracked tasks, when progress reporting is needed during execution, or when checkpoint reviews are required between task batches.
Use when a request or repository needs roadmap decomposition before spec writing because milestone boundaries, module grouping, or independently reviewable tasks are unclear.
Plans development tasks in a structured way for teams. Use this skill when the user triggers /plan-task with a description, or when asking to plan, detail, or break down a development task into steps. Always use when the message starts with /plan-task.
Use when you have a spec or requirements for a multi-step task, before touching code