Loading...
Loading...
Found 5,651 Skills
Persist learnings to memory or maintain existing memories. Triggers on "extract learnings", "save this for next time", "remember this pattern", "consolidate memories", "dream", "clean up memories".
Leap integration. Manage Organizations, Pipelines, Projects, Users, Goals, Filters. Use when the user wants to interact with Leap data.
Scaffold and maintain a reusable research → design → plan → orchestrate → act folder for any non-trivial work — software features, marketing campaigns, org changes. Drops a domain-agnostic spine (00-README · 01-plan · 02/03 research · 04-discussion newest-first · 05-tracking · 09-orchestration · artifact/board.html plan-board) plus stateless action-skills that augment the docs in place without clobbering hand-written prose. Composes ikenga-artifact-builder, huashu-design, frontend-design, ikenga-pkg-builder when present; degrades gracefully when not. Profile-driven: `software` (rich default, code work), `general` (lean, non-code — campaigns, org changes), and `content` (editorial/marketing with key art). TRIGGER when the user asks to start a real plan for non-trivial work ("plan a feature," "scaffold a plan folder," "set up groundwork for…"), references an existing plans/ folder by groundwork structure, or runs any of these actions: groundwork init / research / design / review / clarify / orchestrate / refresh-board / refresh-living-spec / status. DO NOT TRIGGER for one-off code changes, single-document writeups, ADRs, or content that fits in a single markdown file — those don't need a multi-doc plan folder. If the user just wants a single artifact (dashboard, mockup), route to ikenga-artifact-builder instead.
Creates a new Linear issue from a free-form description. Drafts a structured title and body, picks team/project/labels/priority from the connected workspace, shows the draft to the user for approval, then creates the ticket. Use when the user asks to "create a Linear ticket", "file an issue", "make a ticket", "open an issue in Linear", or any request to log a new bug/feature/task.
Document session work with explicit commands. Use /start to begin tracking, /end to finalize session, /clear to reset. Tracks decisions, file changes, and context for continuity.
Extract learnings from completed work. Trigger phrases: "run a retrospective", "extract learnings", "what did we learn", "capture lessons", "create a retro".
Review open issues, selecting an issue to work on, filtering issues by area, pulling GitHub issues, or deciding what to work on next. Triggers include "check issues", "list issues", "what issues", "open issues", "show issues", "view issues", "select issue to work on", "github issues", "backlog issues", "pull issues", "check todos" (deprecated), "list todos" (deprecated), "pending todos" (deprecated).
LangGraph supervisor-worker pattern. Use when building central coordinator agents that route to specialized workers, implementing round-robin or priority-based agent dispatch.
Requirements Discovery Specification, applicable to exploratory scenarios, helps users identify high-ROI functional directions when they are confused through role-playing. Automatically triggered, purely conversational inspiration.
Explain what Nexus is and how it works. Load when user says "explain nexus", "what is nexus", "how does nexus work", "nexus overview", "about nexus", or asks for help understanding the system.
Execute the same task repeatedly with clean context via handoff. Triggers on: recursive loop, repeat until, keep doing until, loop until done. REQUIRES a finish condition to stop.
Intelligent code cleanup with mainline detection, stale artifact discovery, and safe execution. Supports targeted cleanup and confirmation.