Module builds and large feature additions increasingly use a multi-session orchestration pattern: one orchestrator session planning and integrating work, child sessions each owning a single function/doc/fix behind a draft PR into a release branch, and a release PR that only leaves draft once every child PR has merged.
This should be documented under Modules/Process-PSModule/ so it is discoverable alongside Module Bootstrap, and should cover:
- The orchestrator / child session / release branch roles
- Recommended model selection by task type
- The child session coordination protocol (scope, standards references, report-back contents)
- The pre-release checklist (code quality, repository structure, tests, CI) gating the release PR leaving draft
Module builds and large feature additions increasingly use a multi-session orchestration pattern: one orchestrator session planning and integrating work, child sessions each owning a single function/doc/fix behind a draft PR into a release branch, and a release PR that only leaves draft once every child PR has merged.
This should be documented under Modules/Process-PSModule/ so it is discoverable alongside Module Bootstrap, and should cover: