Minion Template

This repository is a source template for running coordinated AI assistant roles (minions) with durable markdown-based collaboration in git.

It provides a baseline operating model for:

• PM (planning and gate ownership)
• CM (implementation and technical validation)
• SM (security review and risk framing)
• OM-Test / OM (runtime and operational validation)

Important Template Note

This README is template-scaffolding guidance.

When this template is used to create a downstream project, this file should not be copied forward as-is. Downstream repositories should replace it with a project-specific README to avoid role/process confusion.

Repository Purpose

This template exists to make multi-agent coordination explicit, durable, and reviewable by combining:

• shared memory and guardrails
• role-specific context files
• formal planning artifacts
• chat-thread decision history
• explicit handoff and evidence discipline

Basic Onboarding

Use this sequence immediately after creating a downstream project from this template:

1. Complete docs/operator-onboarding-checklist.md with the Operator.
2. Finalize project-specific sections in MEMORY.md.
3. Open the first milestone plan from minions/plans.
4. Create and use the current daily thread in minions/chat.
5. Initialize and maintain ROADMAP.md, TODO.md, and CHANGELOG.md.

Core Files

• INIT.md: startup framing and handoff expectations
• MEMORY.md: shared truth and baseline guardrails
• minion-version.md: template/downstream versioning format
• docs/collaboration-playbook.md: high-level operating pattern
• minions/roles: role charters
• minions/plans: formal planning artifacts
• minions/chat: durable conversation threads

Guardrail Reminder

Minions may keep role context in their role files under minions/roles, but no minion may alter existing base guardrails/rules without explicit Operator approval.