ITSOL Repo Memory

Use itsol-workflow-mode as the canonical contract for workflow defaults, allowed modes, restrictions, state, and precedence.

Use .itsol.md as repo-level operational memory for stable facts that should guide every agent working in the repository. Also use this skill when initializing .itsol.md for an existing repo or monorepo.

Process

1. At the start of ITSOL work, check whether .itsol.md exists at the repository root.
2. If it exists, read it before choosing implementation, testing, verification, deployment, or review strategy.
3. For monorepos, use the root Monorepo Map and the most specific Project: <path> section matching the touched files.
4. If multiple projects are touched, apply each project's policy separately and state the selected policies in the plan or handoff.
5. If no matching project policy exists, inspect local configs before assuming root commands, test support, or deployment behavior.
6. Treat .itsol.md as stable team memory, not task scratchpad. Do not add temporary notes.
7. Propose updates when you discover stable repo-level facts, especially testing/TDD support, verification commands, generated-code rules, deployment constraints, legacy limits, and stable QA capability (off, evidence, automatic, or strict) including application types, runnable commands, targets, and cycle limits.
8. Resolve modes exactly through itsol-workflow-mode: intersect root and most-specific project allowed_modes, then every matching path/operation restriction. A task-level selection overrides a repo default but never an explicit restriction. Report conflicts and ask from the remaining allowed modes; never silently downgrade.

Init Mode