Loading...
Loading...
Found 296 Skills
Route engineering work to the right next workflow from natural-language intent and current project state. Use when the user asks what to work on, wants to start something new, continue existing work, pick up a project, decide what comes next, or needs help choosing between research, wayfinding, specification, ticketing, implementation, testing, or review. Infer the lightest safe route, inspect repository and GitHub state when useful, visualise progress top-to-bottom, and stop before execution until the user explicitly authorises the recommended next action.
Systematic Fishbone analysis exploring problem causes across six categories
[BETA] Transform feature descriptions or requirements into structured implementation plans grounded in repo patterns and research. Use when the user says 'plan this', 'create a plan', 'write a tech plan', 'plan the implementation', 'how should we build', 'what's the approach for', 'break this down', or when a brainstorm/requirements document is ready for technical planning. Best when requirements are at least roughly defined; for exploratory or ambiguous requests, prefer ce:brainstorm first.
Use when modifying an existing em plan or task files. Triggers on: "update em", "change plan", "modify epic", "add task", "remove task", "rename phase", "apply annotations", "edit plan". Applies inline > and >> annotations or accepts conversational changes to plan.md or task milestone files.
Discuss phase details and approach
Task Breakdown - generates an implementation plan with tracked tasks based on requirements and design documents. Use when breaking down a design into actionable work items.
Create Linear tickets or GitHub issues following n8n conventions. Use when the user asks to create a ticket, file a bug, open an issue, or says /create-issue.
Requirement Clarification. When user requirements are vague, unclear, lack boundary conditions or acceptance criteria, clarify requirements through multiple rounds of questions and output structured requirement specification documents. Use when requirements are vague, ambiguous, or lack acceptance criteria before implementation.