phase-decomposition
Breaks features into 3-8 manageable phases with clear deliverables and success criteria. Use when planning feature implementation to create testable, independently committable work units.
Discover tools project management skills, compare source repositories and read the instructions for each workflow.
Breaks features into 3-8 manageable phases with clear deliverables and success criteria. Use when planning feature implementation to create testable, independently committable work units.
作業計画を立てたり遂行する際に利用するスキル。作業項目の追加、次のタスク取得、完了マークなどの機能を提供します。
Best practices for managing token usage and budgets
Execute one-off tasks (migrations, refactors, prototypes). Sets up workflow in session.md.
This skill should be used when the user asks to "execute tickets", "work on beads", "do the tickets", "execute ready tasks", "work through the backlog", or wants to execute Beads issue tracker tickets with opti...
Prioritize and align multiple pilot initiatives against strategic goals and resources. Use when evaluating pilot potential, resource constraints, dependencies, and return-on-investment across a portfolio of pro...
Use Taskwarrior v3 as a CLI issue tracker for agent workflows, including task creation, triage, status updates, and completion. Use when organizing local/offline issue tracking without Git integration or runnin...
Standard format for presenting next steps after completing a command or workflow
List pending todos and select one to work on
Writes precise, autonomous-execution-ready tasks using the SMART+ framework (Specific, Measurable, Actionable, Referenced, Testable, +Context). Transforms vague task descriptions into detailed specifications wi...
MoSCoW is a prioritization framework used to categorize requirements based on their importance. The acronym stands for Must have, Should have, Could have, and Won't have. This structured approach helps teams fo...
This skill MUST be invoked before any completion claim, success report, or task transition. Mandates 5-step evidence protocol. Use when about to claim "done", "complete", "working", "fixed", or any success stat...
Development workflow and quality assurance process
Guide through requirements gathering before coding. Creates PROJECT.md with vision, features, tech stack decisions, and success criteria. Asks the key question - does this need a database? Triggers: new project...
This skill should be used when managing the file-based todo tracking system in the .claude/todos/ directory. It provides workflows for creating todos, managing status and dependencies, conducting triage, and in...
作業計画から必要な時間とLLMクオータ(トークン消費量)の見積もりを算出し、コストパフォーマンスを評価する
当你有书面实施计划要在单独会话中执行,并带有审查检查点时使用
作業計画の検証専門家。計画の完全性・明確性を検証し、見落としや曖昧さを指摘。使用場面: (1) 実装計画レビュー、(2) タスク分解の妥当性確認、(3) 依存関係の検証、(4) リスク特定、(5) スコープ確認。トリガー: "plan-revi...
Use this skill to create a PR for a completed task
Export Jira issues with flexible filtering and analyze data using multiple formats (JSON, CSV, JSONL). Use when extracting bulk data from Jira, filtering issues, exporting for external analysis, or analyzing Ji...
Audit milestone completion against original intent before archiving
Determines phase and execution chain based on analysisContext (task type, complexity, signals). Use after uncertainty detection.
Epic design document template. Use when creating new epic documents or need epic structure reference.
Surface Claude's assumptions about a phase approach before planning
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.