Loading...
Loading...
Found 55 Skills
Implement work on issues. Use when user asks to "start working on issue", "what should I work on", "pick up task", "continue work", or "find next task".
Convert the current plan, code review, or structured content in context into a persistent markdown checklist file under .claude/plans/
Linear issue management guide. Use when working with Linear issues, creating issues, updating status, or adding comments. Triggers on Linear issue references (LOBE-xxx), issue tracking, or project management tasks. Requires Linear MCP tools to be available.
Expert backlog manager that prioritizes work using multi-criteria scoring, analyzes dependencies, and recommends optimal next tasks. Activates when managing backlogs, prioritizing work, adding items, or analyzing what to work on next.
Implement Syncfusion WPF Kanban (SfKanban) control for workflow visualization and task management. Use this when building agile project tracking interfaces, workflow boards, or task management systems. This skill covers card configuration, column management, swim lanes, WIP limits, drag-and-drop functionality, workflows, sorting, and event handling.
Search and manage Jira issues using JQL queries, create/update issues, and manage workflows. Use when working with Jira project management.
Format a final summary message for Linear. Your output is automatically streamed to the Linear agent session — just format it well, do not post it yourself.
Manage tasks, track progress, and log daily updates via the ai-todo CLI. Trigger scenarios: 1) EXPLICIT — user mentions tasks, todos, to-do lists, progress tracking, daily standup, sprint planning, project management, work logs, or task completion. 2) POST-ACTION (proactive) — after git commit, git push, deploy to Vercel, merge PR, release, or any significant milestone (feature implemented, bug fixed, refactor done), proactively log progress and update/complete related tasks. When git-tools or vercel:deploy skill finishes, ALWAYS trigger this skill to record what was accomplished. 3) PRE-ACTION (proactive) — when user discusses implementation plans, architecture design, feature breakdown, technical specs, RFC, sprint planning, or requirement analysis, proactively suggest creating tasks to track planned work. When brainstorming skill completes, trigger this skill to convert outcomes into trackable tasks. 4) SESSION-END — when a work session involves substantial code changes, suggest a progress summary before ending. This skill connects to ai-todo (https://ai-todo.stringzhao.life) for persistent task management across sessions.
This skill should be used when the user asks to "create an issue", "file a bug", "create a feature request", "open a GitHub issue", "report a bug", "request a feature", "create a task", "break this into issues", or describes a feature/bug they want tracked in GitHub. Guides interactive issue creation with structured templates, workspace change attachment, and optional autonomous label for the automated pipeline.
Deterministic plan lifecycle management via scripts/plan-manager.py CLI. Use when user asks to list, show, create, check, complete, or abandon plans, or when session starts and stale plans need surfacing. Use for "check plans", "what's on our plan", "mark task done", "finish this plan", or "create a plan". Do NOT use for executing plan tasks, modifying plan content directly, or performance/refactoring work unrelated to plan tracking.
Summarize sprint status and surface risks. Use when the user says "check sprint status" or "show sprint status"
Artifact status + multi-phase orchestration. Scan what exists, check freshness, compose and track complex workflows across sessions. Not for skill routing (the agent does that proactively).