delimit
SolidDelimit a large body of work into right-sized execution units before its method is conducted. Searches for the cut-set over an external work-breakdown structure such that each unit fits one execution span, every cut falls at a natural joint, and coverage is complete with no work orphaned — then emits a WorkUnitMap that references the WBS without owning it, ready to flow into /conduct. Type: (GranularityUnderdetermined, Hybrid, DELIMIT, ExternalWBS × ExecutionHorizon × ContextLifecycle) → WorkUnitMap. Alias: Diairesis(διαίρεσις).
Install
Quality Score: 84/100
Skill Content
Details
- Author
- jongwony
- Repository
- jongwony/epistemic-protocols
- Created
- 8 months ago
- Last Updated
- today
- Language
- JavaScript
- License
- MIT
Bundled in these plugins
Similar Skills
Semantically similar based on skill content — not just same category
planning-the-work
Use when a plan, unit breakdown, task list, or milestone list is in hand and work is about to start against it — including when asked whether to begin the first unit. Also use when turning an approved approach into units. DO NOT invoke to decide whether the work is worth doing at all — route that to ledger:qualifying-a-request. DO NOT invoke once a unit is underway and the question is whether it is finished — route that to ledger:running-a-bounded-loop.
dispatch-work
Send a bounded, isolated worker to carry out authorised work in this repository — briefed from an active item's brief, from that item's current phase, or from the outcome and boundary established live when there is no item — returning a pull request. Use whenever the practitioner directs that work be carried out by someone other than you, in whatever words — "send a worker on it", "put someone on this", "get it built", "dispatch it", "have an agent do X", "go build <item>" — and whenever isolation, a particular model, elapsed time, or keeping this context clean makes a worker the right means. Carrying the work out yourself is equally valid and needs no dispatch.
deepwork
Runs a migration, rewrite or cross-cutting refactor as staged execution: a written stage map, parallel lanes, one failable check per stage, and a gate between stages.