planning and task breakdown

Engineering Community

Skill notes

Overview

Decompose work into small, verifiable tasks with explicit acceptance criteria. Good task breakdown is the difference between an agent that completes work reliably and one that produces a tangled mess. Every task should be small enough to implement, test, and verify in a single focused session.

When to Use

You have a spec and need to break it into implementable units A task feels too large or vague to start Work needs to be parallelized across multiple agents or sessions You need to communicate scope to a human The implementation order isn't obvious

Step 2: Identify the Dependency Graph

Map what depends on what: Implementation order follows the dependency graph bottom-up: build foundations first.

Step 3: Slice Vertically

Instead of building all the database, then all the API, then all the UI — build one complete feature path at a time: Bad (horizontal slicing): Good (vertical slicing): Each vertical slice delivers working, testable functionality.

Step 4: Write Tasks

Each task follows this structure:

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Engineering
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@addyosmani · no license declared
Token usage
Lean
Setup complexity
Plug-and-play
External API key
Not required
Operating systems
Windows
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
Network behavior
External requests
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Step 1: Enter Plan Mode

Before writing any code, operate in read-only mode: Read the spec and relevant codebase sections Identify existing patterns and conventions Map dependencies between components Note risks and unknowns

02
Step 2: Identify the Dependency Graph

Map what depends on what: Implementation order follows the dependency graph bottom-up: build foundations first.

03
Step 3: Slice Vertically

Instead of building all the database, then all the API, then all the UI — build one complete feature path at a time: Bad (horizontal slicing): Good (vertical slicing): Each vertical slice delivers working, testable functionality.

04
Step 4: Write Tasks

Each task follows this structure:

05
Step 5: Order and Checkpoint

Arrange tasks so that: Dependencies are satisfied (build foundation first) Each task leaves the system in a working state Verification checkpoints occur after every 2-3 tasks High-risk tasks are early (fail fast)

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.