Loading...
Loading...
Found 8 Skills
Use when you have specs or requirements for a multi-step task to break it down into detailed tasks, before executing it
Master skill for parallel subagent-driven execution with automatic fallback to single-agent sequential mode. Use when implementing plans with multiple independent sub-phases (SP1, SP2...) to dispatch parallel subagents, or when requiring code review between implementation and testing.
Create work-order with minimal context for isolated subagent execution, optionally linked to GitHub issue
Use when design is complete and you need detailed implementation tasks for engineers with zero codebase context - creates comprehensive implementation plans with exact file paths, complete code examples, and verification steps assuming engineer has minimal domain knowledge
Use when asked to do a full build, complete build, rebuild, or build everything in a Quarkus project. Runs the full Quarkus build with optimized flags via a subagent to keep the main conversation responsive.
Document and communicate plans clearly. Structures implementation plans with tasks, decisions, and success criteria.
Work agent systems with command arguments: slap (emergency-fix stupid agent behavior and safely drain dumb workflows), analyze, optimize, design, and sub / sub-agents (delegate via subagents). Use when the user says agents, `/agents <command>`, agent loops are thrashing, workflows need draining, or they want agent architecture, analysis, or parallel subagent execution.
You MUST use this, and not the upstream superpowers writing-plans skill, when you have a spec or requirements for a multi-step task, before touching code. The plan review is a checklist you run yourself, and execution hands off to sp-subagent-driven-development or sp-executing-plans.