ITSOL Workflow Mode

Resolve the workflow mode before applying planning or implementation gates. Do not resolve or restart a mode for bounded administration that only initializes/updates .itsol.md, inspects repository state, or locally commits an already-produced coherent slice; preserve the preceding task state and perform the bounded operation directly. If that request also introduces code, configuration, product, or behavior changes, resolve mode only for those new changes. Treat this skill as the canonical authority contract; downstream skills must not redefine different mode semantics. Delivery scale is orthogonal: broad multi-phase work uses itsol-initiative-delivery with delivery_scope: initiative, normally layered on autonomous-planned, rather than inventing a fourth authority mode.

Resolve The Mode

Use this precedence:

1. Obey platform-level safety and authority rules.
2. Apply root and most-specific project .itsol.md allowed_modes plus explicit restrictions matching touched paths or operations.
3. Honor an explicit, unambiguous user selection for the current task.
4. Otherwise use the matched .itsol.md default when allowed.
5. Otherwise use governed.

Select:

• governed when the user requests the full planning workflow or does not select another mode.
• autonomous-planned when the user asks the agent to create and review plans, make recommended decisions, and continue without approval pauses.
• direct when the user explicitly asks to work without Business, Technical, or Technical Fix Plans.