Domains / sdlc-full
SDLC domain
A full software workflow with a tracker mirror, local issues, plans, and a living spec.
Use it when: A team uses a tracker and dispatches implementation to separate developer agents.
cumaru install agent <agent> --domain sdlc-full Pillars
| Pillar | Lifetime | Holds |
|---|---|---|
specs/ | Durable | The living spec and ground truth of the system. |
intake/ | Transient | A flat, tracker-agnostic mirror of work items at intake/<KEY>.md. |
issues/ | Transient | Locally authored bugs, features, and chores. Never loaded by default. |
plans/ | Transient | One plan per active item, with tasks, handoffs, and a delta draft. |
exploring/ | Transient | Pre-plan ideas. Never loaded by default. |
Roles
- Lead: plans work, maintains specs, runs absorption, dispatches Dev agents, owns exploring/ and issues/.
- Dev: implements tasks in the active plan. Writes only its own task, handoff, and the delta draft.
- Ghost: read-only pair agent for ad-hoc help. Never writes in .cumaru/.
Lifecycle
- intake/, issues/, and exploring/ -> plans/ -> specs/.
- After absorption the plan is removed. Sources are removed only when this plan consumed them and nothing else depends on them.
Skills
Domain-specific skills, in addition to the universal ones: cumaru-intake,cumaru-issue,cumaru-explore,cumaru-plan,cumaru-specs,cumaru-absorb.
Bootstrap
No domain bootstrap document. cumaru bootstrap prints the universal rules.
Domain rules
- Roles only read intake/; syncing it is mechanical.
- Dev and Ghost load no shallow indexes; they start from the dispatched plan.
Example: From tracker ticket to spec
- cumaru-intake mirrors ticket AAA-123 into intake/AAA-123.md.
- Lead opens plans/AAA-123/ and dispatches a Dev agent per task.
- Lead absorbs the delta into specs/ and removes the plan and the consumed intake entry.
Source: domain.md, config.yaml, roles, skills at revision 37ad79f. The example is a summary
of the shipped recipes, not CLI output.