task-decomposition

스타9

포크0

업데이트2026년 4월 27일 19:11

Task Decomposition

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

출처

exoad

exoad/bibo

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Task Decomposition

Before taking ANY tool action, reply with a short decomposition:

GIVEN: <one line — what the prompt already states> UNKNOWN: <one or two items — what you need to find out> PLAN:

<first tool action, concrete>

Rules:

Keep UNKNOWN to 1–2 items. If it grows past 2, split the task further in step 1.
Resolve one unknown fully before moving to the next — do NOT interleave.
After each tool call, check: did this resolve an UNKNOWN? If yes, strike it. If no, revise the PLAN.

이 저장소의 다른 Skills

같은 저장소

cleanup-memory

exoad/bibo

Consolidate and clean up existing brain memory. Run this periodically (like a sleep cycle) to dedupe, decay, merge, and relocate memories to vault.

2026-05-109

cleanup-sessions

exoad/bibo

Remove old pi session files to reclaim disk space

2026-05-109

code-assist-testing

exoad/bibo

Testing-focused coding workflow. Extends code-assist with enhanced test generation, coverage analysis, and test quality gates.

2026-05-109

debug-assist

exoad/bibo

Systematic debugging workflow for diagnosing and fixing issues. Follows a structured approach to isolate problems, form hypotheses, and verify fixes.

2026-05-109

docs-generate

exoad/bibo

Generate documentation from code or scratch - READMEs, API docs, changelogs, and user guides. Complements codebase-summary which analyzes existing code.

2026-05-109

extract-memory

exoad/bibo

Extract durable learnings and preferences from the current conversation for memory capture. Use this after a conversation to capture what should be remembered.

2026-05-109

name	task-decomposition
description	Task Decomposition
type	workflow
triggers	["/decompose"]
when_to_use	when the task has multiple unknowns or clearly requires multi-step reasoning
context	inline
token_cost	140
user_invocable	false

Task Decomposition

Before taking ANY tool action, reply with a short decomposition:

GIVEN: <one line — what the prompt already states> UNKNOWN: <one or two items — what you need to find out> PLAN:

<first tool action, concrete>

Rules:

Keep UNKNOWN to 1–2 items. If it grows past 2, split the task further in step 1.
Resolve one unknown fully before moving to the next — do NOT interleave.
After each tool call, check: did this resolve an UNKNOWN? If yes, strike it. If no, revise the PLAN.