
Create new agents and roles. Use when the user wants to define a new agent, role, or assistant persona — covers discovery prompt, trigger documentation, and codebase updates.
Design and break down large work into actionable pieces. Use when tackling a big goal—creates design doc, GitHub issues, and hands off to PM for prioritization. Start with the most straightforward chunk.
Create or modify Cursor lifecycle hooks. Use when adding a beforeSubmitPrompt, beforeShellExecution, beforeReadFile, stop, or other hook; or when the user wants to intercept Cursor agent actions.
Execute development work from a pool of GitHub issues. Take one at a time, implement via act-dev, close the issue when done. Use when architect/PM has produced a backlog of issues to implement in parallel.
Run an existing AI crew/committee workflow. Use when the user wants to execute a KaibanJS crew, pass inputs, or invoke a crew script (e.g. prd-review).
Architect-led workflow when expert reply produced multiple solutions. Use when narrowing options, deep-diving, iterating with user, then creating tracked work packages via GitHub issues.
Create skills from an existing project's patterns. Use when introducing an agent to a new project, onboarding to a codebase, or capturing recurring patterns so the agent won't ignore them.
Adversarial reviewer that independently checks completed work for incomplete output, non-holistic approach, glaring issues, and skill discovery.
Configure which projects are connected to a root repo via nested git clones. Applies when the repo has shared .cursor/ and imported projects as normal clone folders. Use when adding, removing, or soft/hard switching projects. Soft switch = toggle .gitignore (no push, WIP stays). Hard switch = remove/add clone folders. Handles progress storage and window reload reminders.
Create an AI crew/committee workflow in KaibanJS. Use when the user wants to assemble a virtual team of AI agents to review, analyze, or synthesize documents from multiple expert perspectives.
Evaluate whether the current task reveals a pattern worth capturing as a reusable skill. Runs at the end of every substantive interaction.
Conventions for creating and organizing skills in this project. Use when creating, writing, updating, modifying, or changing a skill; renaming skills; or reviewing the skill directory structure. Prefer this skill over create-skill when the context is this project's skills.
Project manager agent for capture, triage, and prioritization. Use when capturing ideas, going over inbox (elevate/drop/prioritize), triaging backlog, asking "what's next?", or restoring context. First local, then GitHub — never auto-create issues.