GAF Complexity Decomposer
Goal
Apply GAF complexity-tier rules and produce a concrete module plan for implementation.
Use This Skill When
- New automation requirements are unclear in size/scope.
- User asks how to break down a complex task.
- Existing task needs a major "Improve" refactor.
Inputs
- problem statement
- expected outputs
- data sources and dependencies
- operational constraints (SLA, reliability, ownership)
Procedure
- Classify as
SIMPLE,MID_COMPLEX, orCOMPLEXusinggaf-core-knowledge/docs/task-complexity-tiers.md. - For non-simple work, propose module boundaries with clear responsibilities.
- Define interface contract between modules (inputs/outputs, dependencies).
- Sequence modules into incremental delivery steps.
- Identify validation checkpoints for each module.
Output
- chosen complexity tier and rationale
- module breakdown (or single-task plan for SIMPLE)
- phased implementation order
- validation gate per phase/module
Guardrails
- Do not keep a COMPLEX task as a single opaque implementation.
- Prefer decomposition that minimizes cross-module coupling.