COSMIC Workload Decomposition

Problem

Estimating effort from requirement documents often fails because function points are split inconsistently: one team treats a business scenario as a function point, another misses interface calls, and the final CFP count is hard to audit.

How It Works

The skill turns COSMIC decomposition into a five-step workflow: workspace preparation, function point discovery, user confirmation, decomposition execution, and CSV export. The main flow tracks progress with TodoWrite and infers whether the work is new or resumable from files under results/. Steps 1, 2, and 4 run through Task subagents, while the main agent only reads templates under prompts/, assembles path parameters, starts the task, receives the result, and asks for confirmation. Step 3 requires the user to confirm the function categories and function point list. Step 4 decomposes each function point into sub-process descriptions, limits each subagent batch to 100 function points, and forbids script-generated detail. Step 5 summarizes E, R, W, and X data moves and exports the final detail CSV.

Limits

Use it when you have a .md or .docx requirement document and want a reviewable estimate. It does not clarify ambiguous requirements or replace architecture review; if business rules, interface boundaries, or non-functional constraints are missing, the output may be coarse.