ワンクリックで
todo-management
Use when ideas or tasks surface during work and must be captured, tracked, and routed without losing current-task focus.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Use when ideas or tasks surface during work and must be captured, tracked, and routed without losing current-task focus.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | todo-management |
| description | Use when ideas or tasks surface during work and must be captured, tracked, and routed without losing current-task focus. |
Capture out-of-scope ideas immediately, then return to the active task. Review and route them later without turning capture into an unauthorized context switch.
Announce: "I'm using the todo-management skill to capture this for later."
During active execution, load quick capture only. Load the full structure for a durable todo and review/routing only during explicit todo review or planning.
STATE.md Deferred Ideas, and continue the current task immediately.docs/todos/YYYY-MM-DD-<slug>.md with area, priority, source, created date, status, title, description, context, and related paths. Infer ordinary metadata from current context; do not invent product requirements.STATE.md and the todo path aligned. During planning, inspect relevant pending todos and ask which, if any, belong in the new plan./sc-work, exploration to /sc-explore, planning to /sc-plan, deferral to status update, and deletion only when explicitly chosen.Used during executing-plans, brainstorming, code-review, and systematic-debugging. Pair with state-management for deferred ideas and writing-plans for future plan review.
Use when following the Super Compound BRD -> PRD -> FSD -> GOAL -> IMPLEMENTATION -> VERIFICATION delivery path, artifact traceability, FSD authority, optional ADR handling, zero context bloat issue slicing, or OPEN-* stop conditions.
Use when an approved FSD goal or lightweight issue pointer is ready for implementation.
Use when multi-component work needs cross-component verification of API contracts, data flow, events, auth, config, UI, background jobs, or tests.
Use when /sc-plan needs FSD GOAL-* packets turned into lightweight issue pointers, local Markdown Kanban boards, blocker DAGs, or multi-agent task contracts.
Use when a plan or issue board has 2+ independent execution streams whose time saving exceeds coordination overhead. Dispatches agents in isolated git worktrees only after required delivery gates pass.
Use when an FSD and goal issue board need requirement coverage, goal quality, dependency DAG, sizing, and verification validated before execution.