Scaffold and build EasyAgentTeam template bundles from a reusable workspace, with required plan alignment before generation, Markdown Mermaid workflow confirmation before final workflow output, and built-in check/publish commands through the local template bundle guard runtime. Use when the user wants to create or update an EasyAgentTeam template workspace, define reusable agents and workflow templates, import skills into a template bundle, validate a bundle, or publish it to the EasyAgentTeam backend.
scripts/init_eat_workspace.py <target-dir>..agent-tools/agents/roles/skills/bundles/reports/workspace/Do not write the final bundle or run check/publish until planning is aligned with the user.
Clarify and lock:
If a workflow is involved, present a Markdown Mermaid flowchart and get explicit user confirmation before generating the final workflow template, workflow run, or bundle.
Read references/planning-checklist.md when details are still fuzzy.
Follow the generated workspace contract in AGENTS.md and keep the six-step evidence flow closed:
goalrolesagentsproject/workflowbundlesubmitEach step must leave evidence under reports/step-0X-* before moving forward.
artifacts under workspace/ and make write_set cover them without cross-task overlap.workflow_run.auto_start false.skills/ directory is allowed during planning; local skill import stays skipped until real skill packages are added.Read references/workspace-contract.md if you need the detailed constraints.
Use only these entrypoints inside the copied workspace:
node .agent-tools/scripts/template_bundle_guard.mjs checknode .agent-tools/scripts/template_bundle_guard.mjs publishpublish must remain check-first and must not auto-start runs.
references/planning-checklist.mdreferences/workspace-contract.md