ITSOL Functional Planning

Resolve and preserve the task state through itsol-workflow-mode before applying discovery or planning gates. Do not duplicate the canonical mode contract here.

Proportionate Plan Review

After self-review, follow the effective review trigger. With adaptive, the main agent decides whether isolated review is worth its cost from the plan's scale, uncertainty, novelty, blast radius, and verification strength. Skip it for small, conventional plans; use it for broad or materially risky plans. When selected, the read-only reviewer is pre-authorized. Resolve only concrete material findings and never rerun for suggestions, wording, optional detail, or speculative edge cases.

Shared Process

If the source describes a whole application, module, migration, or multi-phase capability, load itsol-initiative-delivery first. Build complete initiative traceability and a reviewed roadmap; then apply this Business/Technical planning process within outcome-oriented phases. Do not reduce the source to one phase and hand off as though the full request were complete.

1. Inspect the request, repo context, and applicable .itsol.md policy; record and propagate all seven workflow-state fields.
2. Load itsol-requirements-review and inspect enough code, contracts, tests, and conventions to avoid asking questions the repository answers.
3. Ask one targeted question only when an unresolved material ambiguity cannot be resolved safely. Never invent product scope from internet defaults.
4. Keep applicable current-tech research, TDD/replacement verification, implementation review, and protected-action authority independent of planning ceremony.

Governed