Using ITSOL Powers

Choose the smallest sufficient context. Skill descriptions are the routing index; do not preload family checklists.

1. Classify

Bounded administration: repository inspection/status, .itsol.md initialization or update, and a local commit of an already verified slice. Load itsol-repo-memory only when repository policy is involved. Reuse prior evidence for commit-only work; do not create plans, delegation, review, QA, or a new completion gate. Push, release, deployment, and other external effects remain separately authorized.

Engineering: identify the current stage—initiative/intake, requirements, planning, implementation, debugging, migration, review, QA, or current-tech research—before selecting skills.

2. Resolve authority only when relevant

Load itsol-workflow-mode when planning, implementation, bugfix, delegation, or a mode transition needs authority. Do not load it for ordinary read-only review, research, QA, or bounded administration unless the request changes governed state.

Its canonical contract resolves governed, autonomous-planned, or direct and owns workflow_mode, mode_source, decision_authority, scope, artifact_state, execution_mode, and protected_constraints. Preserve canonical values including draft, approved, ready-for-execution, not-required, pending, inline, subagents, and auto; never reinterpret delegated readiness as user approval.

3. Select one primary process