メニュー
Generate a dependency-ordered, phase-based task list from spec.md and plan.md. Run after spec-kit-plan and before spec-kit-analyse.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/aircury/ai-framework --skill spec-kit-tasksコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Distil reusable engineering rules from code changes and record them in docs/rules/. Use whenever the user wants to extract rules, conventions, or lessons from a diff, a commit, or the current uncommitted changes — e.g. "extract the rule from these changes", "what convention does this commit establish", "record this as a rule", or after a correction during review that should become a durable guideline for future work.
Read-only cross-artifact consistency check across spec.md, plan.md, and tasks.md. Detects gaps, conflicts, and FRAMEWORK.md violations before implementation begins.
Create a technical implementation plan from a feature spec. Documents architecture, data models, and interface contracts without generating code. Run after spec-kit-clarify.
SOC 職業分類に基づく
SKILL.md を表示中
| name | spec-kit-tasks |
| description | Generate a dependency-ordered, phase-based task list from spec.md and plan.md. Run after spec-kit-plan and before spec-kit-analyse. |
| license | MIT |
| compatibility | No external workflow CLI required. |
| metadata | {"author":"Aircury","version":"1.0"} |
Generate an actionable, dependency-ordered task list from the feature spec and plan.
Input: Optionally specify a change name. If omitted, infer from context or ask.
Steps
Load artifacts
Required: specs/changes/<name>/plan.md and specs/changes/<name>/spec.md.
Optional (also load if present): specs/changes/<name>/checklists/.
If plan.md is missing, prompt to use the spec-kit-plan skill first.
Generate specs/changes/<name>/tasks.md
Structure tasks in phases:
# Tasks: <Feature Name>
## Phase 1: Setup & Foundations
- [ ] [T01] Description with exact file path
## Phase 2: Domain & Application Layer
- [ ] [T02] Description with exact file path
- [ ] [T03] [P] Description (parallel — can run concurrently with T02)
## Phase 3: Infrastructure & Adapters
- [ ] [T04] [P] Description with exact file path
## Phase 4: Integration & Validation
- [ ] [T05] Description with exact file path
## Dependency Graph
T01 → T02 → T04 → T05
↘ T03 ↗
## MVP Scope
<Minimum set of tasks for a working, deployable slice.>
Task format: - [ ] [TaskID] [P?] [Story?] Description with exact file path
[P] marks tasks safe to run in parallel.Validate
Before finishing:
Output
After writing tasks.md:
spec-kit-analyse skill to validate consistency and user-story coverage before implementation."Guardrails