Loading...
Loading...
Found 43 Skills
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.
Summarize sprint status and surface risks. Use when the user says "check sprint status" or "show sprint status"
Show a dashboard of all projects in the Claude Brain graph. Triggers: "brain status", "show projects", "show brain", "what's in my brain", "project dashboard", "brain overview", "list projects", "summary". Don't fire for loads (use brain-load) or saves (use brain-save).
Show status of all features in .dev/. Scans feature folders using parallel agents, generates a status report, and offers to archive completed features.
Search and manage Jira issues using JQL queries, create/update issues, and manage workflows. Use when working with Jira project management.
Kanban / task board with columns (To do / In progress / In review / Done), draggable-looking cards, assignee avatars, swimlanes, and a top filter bar. Use when the brief mentions "kanban", "task board", "sprint board", "trello", "看板".
Decompose requirements into structured task lists and build a task management system for long-running Agents (based on the Anthropic Effective harnesses methodology). Automatically trigger when users need to manage multi-session development tasks, track feature completion progress, or request "task decomposition", "task management", or "project planning".
State-machine driven orchestrator for structured software development. Invoke when user wants to develop features, fix bugs, or refactor code. Triggers: 'build a feature', 'fix this bug', 'implement', 'develop', 'refactor'.
Define well-structured user stories with acceptance criteria, sizing, and dependencies from project context. Use when breaking down features into implementable stories, refining a backlog, turning requirements or ideas into actionable tickets, preparing stories for sprint planning, or when someone says "create stories for this feature" or "break this down into tickets."
Provides a comprehensive status overview of the Conductor project. Use when the user wants to know the current progress, active tasks, next steps, or overall health of the project tracks and plans.
Records research provenance as a post-task epilogue, scanning conversation history at the end of a coding or research session to extract decisions, experiments, dead ends, claims, heuristics, and pivots, and writing them into the ara/ directory with user-vs-AI provenance tags. Use as a session epilogue — never during execution — to maintain a faithful, auditable trace of how a research project actually evolved.
Analyze a feature or sprint for scope creep by comparing current scope against the original plan. Flags additions, quantifies bloat, and recommends cuts. Use when user says 'any scope creep', 'scope review', 'are we staying in scope'.