Molloy-Home/minions-template
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: refine downstream onboarding workflow

Browse Source
This commit is contained in:
deamonkai
2026-04-12 13:56:28 -05:00
parent e650ec65d1
commit 7dd35f3975
11 changed files with 93 additions and 32 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
MEMORY.md
View File

@@ -51,6 +51,7 @@ This project uses multiple AI agents ("minions") that coordinate through git:
- Shared truth belongs in `MEMORY.md`
- Template version is tracked in `minion-version.md` and must be bumped when baseline guardrails or workflow conventions change; downstream repos should use `<base-template-version>-<downstream-version>` (example: `1.0.1-1.0.0`)
- Downstream repos should keep an approved vendored template snapshot for upgrade diffing; the recommended live path is `.minions-template/`
- The vendored snapshot should be an export-ready copy of the template, not a full Git clone; exclude `.git/` and `do-not-export` files such as `.mm.md`
- `CHANGELOG.md` is required and should capture template-impacting and project-impacting changes
- `ROADMAP.md` is required and should reflect approved direction and upcoming milestones
- `TODO.md` is required and should track actionable backlog items with current status
@@ -74,7 +75,7 @@ This project uses multiple AI agents ("minions") that coordinate through git:
- Any change to a playbook, role, inventory, or variable file must be reflected in the relevant README.md or docs/ entry
- Any new feature, module, or workflow must include corresponding documentation before the commit is made
- `README.md`, `TODO.md`, and `REQUIREMENTS.md` must be reviewed and updated when scope, status, or design changes
- `README.md`, `ROADMAP.md`, and `TODO.md` must be reviewed and updated when scope, status, or design changes
- AI agents must treat documentation updates as a required part of every task — not optional follow-up
- If a documented item is removed or renamed, all references across all docs must be updated in the same commit
@@ -90,7 +91,7 @@ This project uses multiple AI agents ("minions") that coordinate through git:
## Downstream Onboarding Discipline
- `PM` owns initial downstream onboarding unless the Operator explicitly assigns another owner.
- Initial onboarding should start by vendoring the template into `.minions-template/`, not by blindly copying template files into the live repo.
- Initial onboarding should start by vendoring an export-ready template snapshot into `.minions-template/`, not by blindly copying template files into the live repo.
- Treat onboarding as the first controlled export from `.minions-template/` into the live downstream operating surface.
- Use `docs/downstream-onboarding-playbook.md` and `docs/export-manifest.md` to decide which files are exported directly, manually merged, kept downstream-owned, or not exported.
- `INIT.md`, `MEMORY.md`, `docs/operator-onboarding-checklist.md`, and `minion-version.md` should be treated as manual-merge files during onboarding unless the Operator has explicitly isolated template-managed sections.
@@ -99,7 +100,7 @@ This project uses multiple AI agents ("minions") that coordinate through git:
## Downstream Upgrade Discipline
- `PM` owns downstream template upgrades unless the Operator explicitly assigns another owner.
- Downstream repos should keep the currently approved template snapshot under `.minions-template/`.
- Downstream repos should keep the currently approved export-ready template snapshot under `.minions-template/`.
- During upgrade, stage the incoming template in a temporary sibling path such as `.minions-template.next/` so PM can compare:
- current vendored template
- incoming template