Loading...
Loading...
Found 443 Skills
This skill should be used when a user wants to decompose an Epic into its complete set of Features all at once, invoked automatically after write-epic completes, or triggered by phrases like "create all features for this epic", "walk me through all the features", "let's break down this epic", or "plan the features for epic
Fast Track for Feature Process - When requirements are clear and scope is small, skip the complete design process, write a compact {slug}-design.md, and proceed directly to implementation after one confirmation from the user. What is compressed is divergent discussions and phased reviews, not quality standards - code pointers, acceptance criteria, etc., must not be omitted. Trigger scenarios: User says "quick mode", "fastforward", "cut the steps", "just start working". Not suitable for complex features involving cross-subsystem integration, new terminology sorting, or more than 4 promotion steps - in these cases, proactively inform the user to revert to the complete process.
Used when users want to analyze task scheduling, personnel distribution, man-hours, and risk status under a specific TAPD requirement.
Help a PhD student set and revise a realistic 3-month research plan that connects to their longer-term goals. Use this skill whenever the user wants to plan a new quarter, review how the last quarter went, set research goals for the next few months, think about what papers to aim for, or reorient after things drift off course. Trigger on phrases like "quarterly plan", "next 3 months", "plan my quarter", "what should I work on this quarter", "review last quarter", "my research goals", or whenever the user talks about mid-range planning (longer than a week, shorter than a year). Also trigger if the user is feeling directionless about what to focus on next.
Zoho Bugtracker integration. Manage Projects. Use when the user wants to interact with Zoho Bugtracker data.
Creates/selects project; creates or selects an application only when scope or task requires it—not for simple website/function-only work.
Lane integration. Manage data, records, and automate workflows. Use when the user wants to interact with Lane data.
Triage complet RTK : exécute issue-triage + pr-triage en parallèle, puis croise les données pour détecter doubles couvertures, trous sécurité, P0 sans PR, et conflits internes. Sauvegarde dans claudedocs/RTK-YYYY-MM-DD.md. Args: "en"/"fr" pour la langue (défaut: fr), "save" pour forcer la sauvegarde.
Prioritize sprint and backlog work with explicit tradeoffs. USE when choosing what fits next, sequencing backlog items, or balancing value, effort, and risk.
TrackingTime integration. Manage data, records, and automate workflows. Use when the user wants to interact with TrackingTime data.
Markdown チェックリスト・YAML タスクリスト・要件定義書などからプロジェクトアイテムを一括作成する。タイトル・本文・Priority・Size をパースして `gh project item-create` + `item-edit` でフィールド設定。「要件書からアイテム作って」「タスクをプロジェクトに追加」「ロードマップを取り込んで」などで使用。
Pre-sprint diagnostic that determines whether a team should run a Foundation Sprint now, postpone it, or do prerequisite work first. Produces a Go / Conditional Go / Wait verdict with diagnosis, recommended preconditions, attendee list, and pre-sprint activities. Use when a team is considering starting a Foundation Sprint and wants a fast yes/no diagnosis before committing two days of facilitated work.