The practice of decomposing any role, project, or workflow into its smallest atomic tasks before evaluating automation potential. One of the three mindset pillars in the Three M’s of AI framework.
Key points
- Works at any granularity: a YouTube channel, a client project, a role on your team [src-013]
- The decomposition reveals which sub-tasks are deterministic (fully automatable), which benefit from AI assistance, and which require human judgment [src-013]
- Example: a YouTube video is a monolith that “cannot be automated” — but broken down into ideation, scripting, packaging, description, comment replies — many chunks are independently automatable [src-013]
- Reusability: once a sub-task is automated as a skill, it can be triggered from multiple contexts [src-013]
Related concepts
- Three M’s of AI — parent framework
- Default Shift Habit — first habit
- Curiosity Rule — third habit
- Six-Step Skill Building Framework — what to do once you’ve identified a sub-task worth automating
- 60-30-10 Automation Ratio — how to allocate automation coverage across decomposed tasks
Source references
- [src-013] Nate Herk — “Build & Sell Claude Code Operating Systems (2+ Hour Course)” (2026-05-01)
Recommended next
Keep reading from this thread
From 491 indexed pages and articles.
- Wiki concept Skill Feedback Cycle An iterative quality loop for improving Claude Code skills: invoke → watch → give feedback → skill updates itself → repeat. Related by framework
- Wiki concept Four C’s of an AI Operating System Four C's of an AI Operating System The sequential framework Nate Herk uses to build and teach a personal AI Operating System (AIOS) in Claude Code Related by framework
- Insight AI Beyond POCs How enterprise AI moves beyond proofs of concept through ownership, governance, measurement, adoption, and production operating models Readers have engaged with this next