Problem
A task interweaves its design dimensions into a single solution shape. That works while a request touches only a few design axes — those can be turned directly into a task file. When there are too many design dimensions, keeping them apart inside one plan becomes overwhelming: the thoughts can't be held together, and the task format itself starts working against the thinking.
This stayed invisible for a long time because most tasks are simple enough. It surfaced during the browser-dashboard pre-task work (coordination task 260610_browser-dashboard), which only became tractable after the dimensions were identified and split apart.
Proposal
A divide and conquer skill that supports the session job lifecycle at the boundary between chatting and whipping up a plan — invoked when it becomes apparent that notes need to be made before committing to an execution shape with tasks.
What the pattern looked like in practice (the seed for the skill's procedure):
- identify the distinct design dimensions of the request
- create one bounded note file per dimension, numbered in suggested discussion order, plus an index (per-note hook + status) and a living open-questions / truth-gaps list numbered for burn-down
- discuss one note per sitting; write settled answers back into the topic note and strike them from the open-questions list
- only when enough dimensions are settled, cut the task series from the notes — the execution shape is an output of the process, not its starting point
Lifecycle fit
The l-01-session-job-lifecycle skill owns the build-mode decision (chat build vs durable task). This skill sits just before that gate: when reframe/deeper research reveals more design dimensions than a single-page plan can hold, route into divide-and-conquer instead of forcing a premature task shape.
Notes
- Working name "divide and conquer"; final name open.
- Reference implementation of the pattern: the
260610_browser-dashboard notes series (numbered per-dimension notes + index + open-questions burn-down).
Problem
A task interweaves its design dimensions into a single solution shape. That works while a request touches only a few design axes — those can be turned directly into a task file. When there are too many design dimensions, keeping them apart inside one plan becomes overwhelming: the thoughts can't be held together, and the task format itself starts working against the thinking.
This stayed invisible for a long time because most tasks are simple enough. It surfaced during the browser-dashboard pre-task work (coordination task
260610_browser-dashboard), which only became tractable after the dimensions were identified and split apart.Proposal
A divide and conquer skill that supports the session job lifecycle at the boundary between chatting and whipping up a plan — invoked when it becomes apparent that notes need to be made before committing to an execution shape with tasks.
What the pattern looked like in practice (the seed for the skill's procedure):
Lifecycle fit
The
l-01-session-job-lifecycleskill owns the build-mode decision (chat build vs durable task). This skill sits just before that gate: when reframe/deeper research reveals more design dimensions than a single-page plan can hold, route into divide-and-conquer instead of forcing a premature task shape.Notes
260610_browser-dashboardnotes series (numbered per-dimension notes + index + open-questions burn-down).