Loading...
Loading...
Found 95 Skills
Use the DRI Text Analysis Method (Data-Rule-Interaction) to perform word-by-word decomposition and domain modeling on natural language requirement descriptions. Reduce unstructured business requirement texts to structured architectural abstractions in three dimensions: Data (D), Rule (R), and Interaction (I), and directly generate conceptual tables usable for system design. It is suitable for requirement analysis, ubiquitous language extraction, text parsing before architecture design, and converting long requirement documents into clear development task decompositions.
Turn a spec or requirements into a bite-sized implementation plan. File-structure-first (deep modules), embedded grill to stress-test, no forced sub-skill chains. Use when you have a spec or clear requirements and are ready to plan execution.
Task generation skill based on the speckit workflow, used to generate actionable, dependency-ordered tasks.md from available design documents. Use this skill when you need to generate detailed task lists for feature development based on design documents such as spec.md, plan.md, data-model.md, contracts/, etc. Trigger words include "speckit tasks", "generate tasks", "task planning", "feature task decomposition", "create tasks.md", etc.
Use when deciding how big a fix should be, when scope is drifting mid-task, when a plan is being quietly trimmed to fit, or when "while you're at it" appears in any form. Encodes size-to-trigger, decompose-not-descope, and drive-to-completion. Use whenever the work is about to grow past its cause or shrink below its promise.
You MUST use this when an approved design or settled requirements need a detailed multi-step implementation plan before code changes begin.
Phase 分割された GitHub Issue ツリーを新規作成するスキル。「イシューツリー作って」「タスクを Phase 別に Issue 化」「Issue ツリーを起票して」で使用。 要件・タスク一覧を受け取り、タスク分解（4h 粒度）→ Phase 分割 → ルート（トラッキング）issue → Phase 親 issue → 子 issue の階層を sub_issues API で紐付け。 phase ラベル付与・ルート issue 本文の Phase 別表生成まで自動化。任意の phase 指定で部分起票にも対応。 ツリーの棚卸し・更新は update-issue-tree、実装消化は implement-issue-tree を参照。
Convert one approved idea into an executable project when probe next routes project_setup.
Software implementation planning with file-based persistence (.plan/). Use when planning code changes touching 3+ files or with ambiguous scope. Skip for typos, single-file fixes, and research/scanning/audit work that produces reports rather than code.
Task decomposition, goal-oriented planning, and adaptive execution strategies for AI agents. Use when facing complex multi-step tasks that require structured approach.
Default task orchestrator for all development and investigation work. Classifies tasks, decomposes into parallel workstreams if appropriate, and routes execution through the recipe runner. Replaces ultrathink-orchestrator.
Use quando o usuário quer quebrar ou decompor a especificação em tarefas, preencher ou atualizar a seção `14. Tarefas` de `spec.md`, ordenar dependências, planejar fatias verticais ou preparar a execução. Use também quando uma transição automática pedir planejamento, replanejamento ou retomada após RED. Use somente para editar o backlog dentro da fonte única; não crie tasks.md, não escreva código nem marque trabalho como concluído.
Create implementation task plans in `_/local-plans/<plan-name>.md`. First investigate the codebase using the Explore Agent, then document it in verifiable granularity and parallel-executable units, following the standard format (Background & Purpose, Current Status, Design, File Structure Tree, Implementation Steps, Verification Methods) that can be validated by the plan-verifier Agent. Used for requests like "Make a plan", "Design", "Task decomposition", "Think about implementation approach". plan, planning, design, implementation plan, task decomposition, create-plan