Domains / sdlc-light
SDLC Light domain
A simplified software workflow: explorations become plans, and plans are absorbed into a living spec.
Use it when: One lead, human or agent, owns planning and specs for a software project.
cumaru install agent <agent> --domain sdlc-light Pillars
| Pillar | Lifetime | Holds |
|---|---|---|
specs/ | Durable | The living spec: what is true now. Areas nest subareas. |
plans/ | Transient | One plans/<PLAN-ID>/ per tracker-backed or maintenance item, with tasks, handoffs, and a delta draft. |
exploring/ | Transient | Pre-plan ideas. Never loaded by default. |
Roles
- Lead: the only role. Reads and writes the whole tree; owns planning, specs, exploration, and absorption.
Lifecycle
- exploring/ -> plans/ -> specs/.
- Tracker items feed plans through the key: field; there is no intake pillar.
- On close, cumaru-absorb updates the spec owners and removes the plan. An exploration is removed only when actually consumed.
Skills
Domain-specific skills, in addition to the universal ones: cumaru-explore,cumaru-plan,cumaru-specs,cumaru-absorb.
Bootstrap
No domain bootstrap document. cumaru bootstrap prints the universal rules; the cumaru-install skill then maps components and hands off to cumaru-specs.
Domain rules
- Slug plans use the maintenance- prefix.
- A plan declares scope: paths under specs/, which form the loading entry for plan work.
Example: Close a maintenance plan
- cumaru-plan opens plans/maintenance-<slug>/ with acceptance criteria and tasks.
- Each task records a handoff with evidence; the plan gets a delta-draft.md.
- cumaru-absorb verifies the criteria, writes the delta into the owning specs/ areas, and removes the plan after a Git recovery point.
Source: domain.md, config.yaml, roles, skills at revision 37ad79f. The example is a summary
of the shipped recipes, not CLI output.