Skip to content

📖 [Docs]: Module development orchestration pattern documented#92

Draft
Marius Storhaug (MariusStorhaug) wants to merge 3 commits into
mainfrom
reimagined-dollop
Draft

📖 [Docs]: Module development orchestration pattern documented#92
Marius Storhaug (MariusStorhaug) wants to merge 3 commits into
mainfrom
reimagined-dollop

Conversation

@MariusStorhaug

Copy link
Copy Markdown
Member

Building a module from scratch, or adding a significant feature set to one, now has definitive guidance for coordinating the work across multiple sessions instead of one long session trying to do everything serially.

New: Module Development Orchestration page

A new page under Process-PSModule documents the orchestrator/child session pattern: one orchestrator session plans work and integrates results, child sessions each own one function, doc update, or fix behind a draft pull request targeting a release branch, and the release branch's own pull request into main only leaves draft once every child pull request has merged.

It also documents:

  • Recommended model selection by task type (orchestration, complex implementation, simple implementation, documentation, standards review, test writing, research).
  • The child session coordination protocol - what the orchestrator hands each child, and what each child must do and report back before the orchestrator verifies and merges it.
  • The pre-release checklist gating the release pull request leaving draft: code quality, repository structure, tests, and CI.

The page is linked from the Process-PSModule section index and navigation, alongside the existing Module Bootstrap page it complements.


Technical details
  • Added src/docs/Modules/Process-PSModule/module-development-orchestration.md.
  • Linked the new page from src/docs/Modules/Process-PSModule/index.md and the nav table in src/zensical.toml.
  • Markdown-linted against .github/linters/.markdown-lint.yml with zero issues.
Relevant issues (or links)

Documents the orchestrator/child session pattern for building modules
from scratch or adding significant feature sets: one orchestrator
session planning and integrating work, child sessions each owning one
function, doc, or fix behind a draft PR targeting the release branch,
and a release branch/PR that only leaves draft once every child has
merged. Includes model selection guidance by task type, the child
session coordination protocol, and the pre-release checklist covering
code quality, repository structure, tests, and CI.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
@github-actions

github-actions Bot commented Jul 26, 2026

Copy link
Copy Markdown

Super-linter summary

Language Validation result
CHECKOV Pass ✅
GITHUB_ACTIONS Pass ✅
GITHUB_ACTIONS_ZIZMOR Pass ✅
GITLEAKS Pass ✅
GIT_MERGE_CONFLICT_MARKERS Pass ✅
HTML Pass ✅
JAVASCRIPT_ES Pass ✅
JAVASCRIPT_PRETTIER Pass ✅
MARKDOWN Pass ✅
NATURAL_LANGUAGE Fail ❌
POWERSHELL Pass ✅
PRE_COMMIT Pass ✅
SPELL_CODESPELL Pass ✅
TRIVY Pass ✅
YAML Pass ✅

Super-linter detected linting errors

For more information, see the GitHub Actions workflow run

Powered by Super-linter

NATURAL_LANGUAGE

/github/workspace/src/docs/Modules/Process-PSModule/module-development-orchestration.md
  72:4  ✓ error  Incorrect term: “Pre-release”, use “Prerelease” instead  terminology

✖ 1 problem (1 error, 0 warnings, 0 infos)
✓ 1 fixable problem.
Try to run: $ textlint --fix [file]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Document module development orchestration pattern

1 participant