📖 [Docs]: Coordinate substantial module work across focused sessions - #455
Merged
Marius Storhaug (MariusStorhaug) merged 4 commits intoSep 4, 2026
Merged
Conversation
Document parent and child session coordination, draft PR targeting, integration, and release readiness for substantial module work.\n\nCo-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Add the orchestration guide to the documentation landing page and Zensical navigation.\n\nCo-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Super-linter summary
All files and directories linted successfully For more information, see the GitHub Actions workflow run Powered by Super-linter |
Limit integration branches to module bootstrap, align existing-module guidance with the repository trunk-based development standard, and update the guidance-source link after the documentation repository migration.\n\nCo-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Marius Storhaug (MariusStorhaug)
marked this pull request as ready for review
September 4, 2026 19:54
Marius Storhaug (MariusStorhaug)
requested a review
from a team
as a code owner
September 4, 2026 19:54
Marius Storhaug (MariusStorhaug)
deleted the
document-orchestration-pattern
branch
September 4, 2026 19:56
Marius Storhaug (MariusStorhaug)
added a commit
that referenced
this pull request
Sep 4, 2026
…stently (#533) Agents and contributors can now coordinate substantial module work across focused sessions and author reusable PSModule plugin skills with consistent process guidance. ## New: Module development orchestration skill The `psmodule-module-development-orchestration` skill guides a parent session through decomposition, branch selection, child-session handoffs, review, integration, stop conditions, and report-back. It follows trunk-based development for existing modules and reserves integration branches for the documented bootstrap exception. ## New: Plugin skill authoring guidance The documentation now explains how to write focused plugin skills and the `psmodule-skill-authoring` skill points authors to that shared guidance. Common process rules remain linked to the canonical Process-PSModule and MSX ways of working instead of being duplicated across skills. --- <details> <summary>Technical details</summary> - Added `.github/plugin/psmodule/skills/psmodule-module-development-orchestration/SKILL.md`. - Added `.github/plugin/psmodule/skills/psmodule-skill-authoring/SKILL.md`. - Added `docs/content/guides/writing-plugin-skills.md`. - Updated `.github/plugin/README.md`, `docs/content/index.md`, and `docs/zensical.toml` for discoverability. - Corrected stale MSX documentation paths and verified the live destinations. - Kept orchestration and skill-authoring procedures focused on agent-specific behavior; organization-wide process rules remain linked to canonical MSX guidance. - Implementation plan progress: orchestration skill, skill-authoring guidance, plugin discoverability, documentation navigation, branch-policy decisions, canonical-link migration, and repository-native validation guidance are complete; no follow-up implementation work is included. - Standards and framework alignment: | Changed surface | Standards checked | Framework docs checked | Result | | --- | --- | --- | --- | | `.github/plugin/**` (Copilot plugin skills and README) | MSX agentic development and Markdown | Process-PSModule plugin conventions and orchestration guide | Aligned | | `docs/content/**`, `docs/zensical.toml` (documentation) | MSX Markdown and natural-language guidance | Process-PSModule documentation model and site navigation | Aligned | - Validation: `git diff --check`, metadata and navigation review, strict Zensical build, 26 unique MSX URL checks with all responses in the 2xx range, Analyze, Lint, Lint code base, Build, and CodeQL passed. Publish was skipped as expected for this draft. - Issue convergence sweep: this change implements the agent-operational and skill-authoring portions of the orchestration guidance; no additional open issues were fully satisfied by the diff. </details> <details> <summary>Relevant issues (or links)</summary> ### Related work - Depends on #455 - References #482 </details> --------- Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Contributors can now coordinate substantial module work across an orchestrator session and focused child sessions while keeping each change reviewable and aligned with Process-PSModule's trunk-based flow.
New: Module development orchestration
The guide explains how a parent session plans work, gives each child a narrowly scoped outcome, and verifies each draft pull request before integration. It also defines the handoff and completion report, the bootstrap-only integration-branch exception, dependent stacked pull requests, and release-readiness checks for the coordinated change.
The guidance links to the canonical Process-PSModule and MSX practices instead of duplicating organization-wide rules. Existing modules use short-lived branches targeting
main; an integration branch is reserved for the documented module-bootstrap workflow.Technical details
docs/content/guides/module-development-orchestration.md.docs/content/index.mdanddocs/zensical.toml.docs/content/**(Markdown)docs/zensical.tomlzensical build --clean --strict,git diff --check, and HTTP checks for the changed external documentation links passed. The branch contains the latestmain.Relevant issues (or links)
Related work