This repository stores a versioned family of Planner/Executor and multi-agent orchestration workspace templates.
The templates are designed for project folders where AI agents work with clear role boundaries, validation evidence, review logs, and reusable operating rules. The repository keeps each version as a separate folder so the evolution from the original template to the newest orchestration template can be inspected and compared.
Planner-executor temp oringal ver: original V000 baseline.Planner-executor temp V001 ...throughPlanner-executor temp V011 ...: versioned template copies.VERSION_CONTROL.xlsx: workbook tracking version history, validation notes, change details, and use rules.template_visual_map/index.html: interactive visual map explaining the version evolution, structure, function parts, and current recommendations.
The newest template direction is V011, the stale subagent recovery template. It keeps the no-Explorer structure introduced in V010, keeps quality and run-state layers, and adds checkpoint-based stale spawned-subagent recovery.
The visual map currently reports one important live-state warning: V011's workbook entry says validation passed, but the current live validator flags stale Explorer wording in its README. Treat that warning as the next cleanup item before marking V011 as fully approved.
- Open
template_visual_map/index.htmlto understand the version history. - Choose the template version that matches the workflow you want.
- Copy that version folder into a new project-specific workspace.
- Keep one actual project per copied workspace.
- Run the copied workspace validator before and after meaningful changes.
When changing the templates, update the relevant version folder, record the change in VERSION_CONTROL.xlsx, run the validator, then commit the change with Git.
Basic Git update flow:
git status
git add .
git commit -m "Describe the template change"
git pushUse short commit messages that explain the change in plain language.