task-list
Skill9 starsChanged 3 months agoMITView on GitHub
rdd.mdからSprint計画を作成し、GitHub MilestoneとIssueを一括生成する。スプリント計画、タスク分解で使う。
2 other projects use a version of this.
Adopted by
Most recently taken up by
- NVIDIA/SkillEvaluatortheir own version, first seen Oct 13, 2026
- LeoFuso/blainetheir own version, first seen Oct 13, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- NVIDIA/SkillEvaluator★ 656same name
- LeoFuso/blaine★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository57 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- accessibility-engineerSkill
- agent-browserSkill
- animation-principlesSkill
- architecture-expertSkill
- art-directionSkill
- auto-bugSkill
- auto-buildSkill
- auto-designSkill
- auto-taskSkill
- basic-reviewSkill
- biz-researcherSkill
- bug-fixSkill
- bug-investigateSkill
- bug-newSkill
- bug-proposeSkill
- build-context-siteSkill
- creative-coderSkill
- deep-reviewSkill
- design-assembleSkill
- design-componentsSkill
- design-critiqueSkill
- design-htmlSkill
- design-mockSkill
- design-ssotSkill
- design-uiSkill
- developer-specialistSkill
- docs-reverseSkill
- experience-planSkill
- frontend-implementationSkill
- image-prepSkill
- judgment-harnessSkill
- keyboard-shortcutsSkill
- manual-genSkill
- manual-guideSkill
- official-source-firstSkill
- pairSkill
- persona-designerSkill
- project-design-languageSkill
- project-initSkill
- proposition-reviewerSkill
- proto-loopSkill
- proto-mediumSkill
- pr-respondSkill
- repo-tourSkill
- security-expertSkill
- sensory-designSkill
- session-endSkill
- session-startSkill
- setupSkill
- task-detailSkill
- task-runSkill
- template-feedbackSkill
- template-inboxSkill
- testingSkill
- ui-designerSkill
- usability-psychologistSkill
The file
Files
[タスク] 1. Sprint計画(Milestone + Issue一括作成)
入力: $ARGUMENTS
- コンテキストファイル(例:
doc/input/rdd.md)
🎯 目的
- doc/input/rdd.md を根拠に、Sprint(Milestone)とタスク(Issue)を一括作成する
- 組み込みTask(TaskCreate)にも登録し、セッション中の並行・依存管理を可能にする
- GitHub と 組み込みTask の対応関係を維持する
GitHub との対応関係
Repository = プロダクト
└── Project = カンバンボード(任意)
└── Milestone = Sprint
└── Issue = タスク実行手順
1. RDD読み込み・Sprint計画
# RDDを読み込み、Sprint単位でタスクを設計- 目標/非目標、技術スタック、非機能要件を確認
- MVP優先でSprintを設計(1 Sprint = 1 Milestone)
2. Milestone作成(Sprint単位)
# Milestone存在確認
gh api repos/{owner}/{repo}/milestones --jq '.[] | select(.title=="sprint-1")'
# 存在しなければ作成(⚠️ 確認あり)
gh api repos/{owner}/{repo}/milestones -f title="sprint-1" -f description="Sprint 1: {目的}"3. Issue一括作成
# 各タスクをIssueとして作成(⚠️ 確認あり)
gh issue create \
--title "TASK-1: {タスク概要}" \
--body "## 目的
{タスクの目的}
## RDD参照
- doc/input/rdd.md §{セクション}
## 検証ゲート
\`\`\`bash
pnpm lint --fix && pnpm type-check
pnpm test
\`\`\`
## 依存
- なし(または #XX)
## 決定理由
{なぜこのタスクが必要か}" \
--milestone "sprint-1" \
--label "task"4. 組み込みTask登録
Issue作成後、組み込みTaskにも登録する:
TaskCreate:
subject: "TASK-1: {タスク概要}"
description: "{タスクの詳細}"
activeForm: "{タスク概要}を実装中"
metadata:
issueNumber: 123
milestone: "sprint-1"5. 一覧表示
📋 Sprint: sprint-1
┌────┬─────────────────────┬──────────┬─────────────┐
│ # │ Title │ Issue │ Status │
├────┼─────────────────────┼──────────┼─────────────┤
│ 1 │ ユーザー認証実装 │ #123 │ pending │
│ 2 │ ログイン画面作成 │ #124 │ pending │
│ 3 │ API設計 │ #125 │ pending │
└────┴─────────────────────┴──────────┴─────────────┘
次のステップ: /task-detail sprint-1出力
GitHub
- Milestone:
sprint-{n} - Issues: タスクごとに1 Issue(ラベル:
task)
組み込みTask
- TaskCreate: 各Issueに対応するTask(metadata.issueNumber で紐づけ)
品質チェックリスト
- RDD/Architecture の整合性
- Milestone が正しく作成されている
- Issue に RDD参照・検証ゲートが含まれている
- 組み込みTask に issueNumber が設定されている
- 一覧表示で対応関係が確認できる
自己評価
- 成功自信度: (1-10)
- 一言理由: {短く理由を記載}
次のステップ
/task-detail sprint-1 # Issue詳細化 + 依存関係設定全体フロー(ゴールまでの地図)
/task-list(全Sprint計画・Issue一括作成)← いまここ
└─ Sprintごとに:
/task-detail sprint-N(Issue詳細化 + sprint/* ブランチ作成)
└─ タスク(Issue)ごとに:
/auto-task #issue(task/* ブランチ作成 → 実装 → レビュー → task→sprint 自律マージ)
※ 途中で bug 検知時は問題解決志向の bug-* 連鎖で自己修復してタスクに復帰
└─ Sprint 全タスク完了時:
AI が sprint → main の PR を作成 → 人間がマージ判断(ここだけ人間の関所)この地図全体(要件定義〜エビデンスレポート提示まで)を1コマンドで自律実行したい場合は
/auto-buildを使う。
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

