Loading...
Loading...
Found 53 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".
Create work-order with minimal context for isolated subagent execution, optionally linked to GitHub issue
Generate a status report with KPIs, risks, and action items. Use when writing a weekly or monthly update for leadership, summarizing project health with green/yellow/red status, surfacing risks and decisions that need stakeholder attention, or turning a pile of project tracker activity into a readable narrative.
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."
Simplified state file management with consolidated FLOW.md (project) and ITEM-XXX.md (per-item) files
Create a TODO or initiative task in One Horizon. Use when asked "log this task", "create a todo", "track this small task", "create an initiative", "plan this project", or "start a roadmap initiative". For bugs or feature requests, use report-issue instead. Requires One Horizon MCP.
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".
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.
Convert the current plan, code review, or structured content in context into a persistent markdown checklist file under .claude/plans/
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'.
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.