Atomic Breakdown
Break complex requirements into atomic tasks — the most granular, indivisible processing steps.
Core Three Elements
Each atomic task must include:
- Input: All structured info needed to start
- Data type, source, constraints, boundary values
- Process: Single core task
- LLM good at: classification, extraction, summarization, generation, translation, rewriting
- Code good at: exact computation, rigid logic, DB queries, external API calls
- Output: Structured result
- Success: type + structure
- Failure: error code + message
Decomposition Levels
Requirement → Module → Task → Sub-task → Atomic Operation
Atomic Criteria (all 6 must pass)
- Single responsibility: Explainable in one sentence
- Explicit input: Type, source, boundary values all listed
- Complete processing: Every branch and exception covered
- Clear output: Success and failure states defined
- Indivisible: Cannot split into smaller independent units
- Independently testable: Verifiable without context
Decomposition Method Selection
| Task Type | Approach |
|---|---|
| Data flow | Follow input → validate → process → store → return |
| Feature module | Split exception handling and edges first, then core logic |
| Composite task | Split all atoms first, then单独 list orchestration atoms |
Output Structure (5 parts)
1. Hierarchy Diagram
Tree structure showing full decomposition
2. Module Division
2-5 core modules, each with clear responsibility
3. Atomic Task List
In execution order, each using standard format:
### Atom N: [verb + noun]
- Input:
- Data type:
- Source:
- Constraints:
- Boundary values:
- Process:
- Steps:
- Branch logic:
- Exceptions:
- Output:
- Success: {type, structure}
- Failure: {error code, message}
4. Dependency Diagram
Mermaid flowchart with:
- Normal flow (solid lines)
- Exception branches (dashed/red)
- Parallel tasks (sync nodes)
5. Acceptance Checklist
- [ ] Every atom's input type and boundary values explicit?
- [ ] Every atom's processing branches covered?
- [ ] Every atom's success and failure states defined?
- [ ] All atoms indivisible?
- [ ] Dependencies complete?
- [ ] All ambiguity eliminated?
Prohibited
❌ Vague descriptions: "process data" → must specify what data, how
❌ Merged exceptions: error handling can't be absorbed into main flow
❌ Orchestration atoms writing business logic: they only coordinate
Execution Flow
- Understand requirements — ask if unclear
- Identify modules — 2-5 core modules
- Per-module decomposition — identify atomic tasks
- Define three elements — explicit IPO for each atom
- Draw dependency graph — Mermaid flowchart
- Self-check — verify all 6 acceptance criteria
流程衔接
拆解完成后：
- 整体方案设计 → 用 方案设计
- 想从零散需求整理出 PRD → 先回 需求转PRD
- 进入开发落地 → PRD转开发规范 → 工程交付
