Documentation

Concepts / Disciplines

Authority, recipes, and working rules.

Roles define responsibility. Skills supply workflows. Disciplines govern how applicable work is performed.

A role sets the boundaries

A domain declares its roles and their initial context. Loading a role gives the agent its responsibilities and restrictions. It does not grant capabilities outside that role or override the user's authorization and environment permissions.

SDLC Light has a single Lead role. Other domains can declare different roles. Loading a new role is an explicit context operation; the agent must not silently combine roles to gain more authority.

Sources: SDLC Light Lead and role loading.

A skill carries a recipe

A skill describes a repeatable workflow: discover relevant knowledge, author a plan, reconcile references, or close completed work. Its applicability and domain determine which recipe to use.

A skill is not a CLI subcommand. For example, cumaru-plan is an agent skill; cumaru plan is not a native command. Some adapters provide slash-command launchers that forward arguments to a skill. Others invoke native skills directly.

Same-named skills can have domain-specific recipes. Read the installed variant instead of substituting another domain's workflow.

Sources: adapter invocation and the SDLC Light planning skill.

A discipline governs applicable work

Every installed discipline is delivered at context start, with the discipline index first. Eager loading keeps the working rules available. It does not mean every rule applies to every task.

Each discipline declares an applies-when: trigger and a strictness: value. The trigger determines applicability. Strictness determines how aggressively the agent must consider that trigger and comply when it matches.

10/10
Evaluate on every task and material transition; comply when applicable.
7-9/10
Evaluate when there is a reasonable trigger signal; a deviation needs a concrete reason.
4-6/10
Evaluate on a direct trigger; apply by default and adapt with justification.
1-3/10
Consult when clearly useful; application is discretionary.
0/10
Optional reference without an operational obligation.

Missing strictness is invalid metadata and is treated as 0/10. Evaluate cumaru-first first. Apply every matching discipline rather than selecting a single preferred rule.

Source: the discipline evaluation contract.

The CLI performs bounded operations

The CLI supplies commands for discovery, validation, and explicit changes. The agent composes those commands through skills and follows the relevant role and discipline rules. A command's success does not prove the larger workflow is complete.

For example, a valid plan file is not completion evidence. Its acceptance criteria and the domain's close workflow still decide whether work can be absorbed.

Source: verified direct absorption.

Back to concepts or set up your project.