@mootup/moot-templates 0.1.0-rc.0

package/templates/teams/loop-4-split-leader/team.toml

@@ -0,0 +1,140 @@
+toml_schema_version = "1"
+
+[archetype]
+id = "mootup/loop-4-split-leader"
+version = "1.0"
+diverged_at = ""
+
+[team]
+name = "loop-4-split-leader"
+description = "Pipeline with separated Product (human-facing) and Lead (team-facing) coordination"
+version = "1.0"
+origin = "Variant of loop-4 for high human interaction load"
+
+# -- Roles --
+
+[[roles]]
+name = "product"
+display_name = "Product"
+harness = "claude-code"
+model = "opus"
+theme = "blue"
+responsibilities = """
+Prioritization, requirements, stakeholder communication. Dispatches
+features to Lead. Does not directly coordinate the pipeline -- that's
+Lead's job. Human interface for product decisions."""
+
+startup_prompt = """
+You are the Product agent. Call orientation() to get your identity,
+focus space, and context in one call. Then subscribe to the channel.
+Post a status_update confirming you are online."""
+
+[[roles]]
+name = "lead"
+display_name = "Lead"
+harness = "claude-code"
+model = "sonnet"
+theme = "yellow"
+responsibilities = """
+Team coordination -- dispatch to Spec, merge branches, monitor pipeline,
+process QA handoffs, run retros. Reports completion back to Product.
+Owns git operations (commits, branches, merges)."""
+
+startup_prompt = """
+You are the Lead agent. Call orientation() then subscribe to the channel.
+Post a status_update confirming you are online. Wait for features from Product."""
+
+[[roles]]
+name = "spec"
+display_name = "Spec"
+harness = "claude-code"
+model = "opus"
+theme = "magenta"
+responsibilities = """
+Design docs, specifications, test plans, architecture review. Verifies
+technical claims against the codebase. Each spec includes security
+considerations. Produces implementation-ready specs with complete
+file content where possible."""
+
+startup_prompt = """
+You are the Spec agent. Call orientation() then subscribe to the channel.
+Post a status_update confirming you are online. Wait for work."""
+
+[[roles]]
+name = "implementation"
+display_name = "Implementation"
+harness = "claude-code"
+model = "opus"
+theme = "cyan"
+responsibilities = """
+Code implementation based on specs. Writes common-case behavioral tests
+before handoff (pipeline gate). Follows spec precisely -- asks for
+clarification rather than guessing."""
+
+startup_prompt = """
+You are the Implementation agent. Call orientation() then subscribe to
+the channel. Post a status_update confirming you are online. Wait for work."""
+
+[[roles]]
+name = "qa"
+display_name = "QA"
+harness = "claude-code"
+model = "sonnet"
+theme = "green"
+responsibilities = """
+Test strategy, test implementation, feature verification. Owns the docker
+compose stack. Extends test coverage beyond spec requirements based on
+own analysis. Includes security verification. May commit small repairs
+directly when the intended behavior is unambiguous."""
+
+startup_prompt = """
+You are the QA agent. Call orientation() then subscribe to the channel.
+Post a status_update confirming you are online. Wait for work."""
+
+# -- Workflow --
+
+[workflow]
+description = """
+Product dispatches features to Lead. The pipeline runs through Lead:
+Lead --> Spec --> Implementation --> QA --> Lead.
+Lead reports completion back to Product. This separates human-facing
+product decisions from team coordination."""
+
+pipeline = ["lead", "spec", "implementation", "qa"]
+
+[workflow.threads]
+feature = "[FEATURE]"
+question = "[QUESTION]"
+git_request = "[GIT-REQUEST]"
+stack_request = "[STACK-REQUEST]"
+
+[workflow.handoff]
+method = "mention"
+includes = ["summary of work done", "what next agent needs to do", "files changed", "branch name"]
+
+# -- Git --
+
+[git]
+description = """
+Each agent works in a git worktree. Feature branches from main,
+agent branches from feature branch. Squash-merge features to main.
+Lead owns git operations (not Product)."""
+
+strategy = "worktree"
+feature_branch = "feat/{slug}"
+agent_branch = "{role}/{slug}"
+merge_to_main = "squash"
+
+[git.ownership]
+main_branch = "lead"
+stack = "qa"
+
+# -- Resource ownership --
+
+[resources]
+description = """
+Shared resources have a single owner to avoid contention."""
+
+[resources.owners]
+git = "lead"
+docker_stack = "qa"

package/templates/teams/loop-6/CLAUDE.md

@@ -0,0 +1,43 @@
+# {project_name}
+
+TODO: Describe your project. What does it do? What problem does it solve?
+
+## Status
+
+TODO: What works, what doesn't. Update as the project evolves.
+
+## Tech stack
+
+TODO: Language, frameworks, databases, build tools.
+
+## Running
+
+TODO: How to run the project, run tests, build, deploy.
+
+## Code conventions
+
+TODO: Formatting, linting, type checking, naming conventions.
+
+## Agent Workflow
+
+{role_count} agents collaborate on this project: {role_list}. They communicate via the Convo shared context server. Pipeline agents use Claude Code. Product coordinates strategy; Leader orchestrates the operational pipeline; Librarian observes asynchronously for docs.
+
+### Roles
+
+{role_descriptions}
+
+### Strategic vs Operational Layers
+
+Product handles strategic direction and is operator-facing. Leader handles operational orchestration -- day-to-day git operations, pipeline monitoring, ship coordination. Product makes design decisions; Leader executes.
+
+### Observer Role
+
+The Librarian is an async observer -- it monitors the pipeline for shipped features and updates documentation, but does not block the main work pipeline. Librarian communicates with Product via a dedicated side thread.
+
+### Resource Ownership
+
+{resource_ownership}
+
+### Git Workflow
+
+{git_description}

package/templates/teams/loop-6/README.md

@@ -0,0 +1,9 @@
+# loop-6 -- Strategic + Operational + Observer Pipeline
+
+Six-agent pipeline with separated strategic (Product) and operational (Leader)
+coordination, plus async documentation observer (Librarian).
+Pat -> Product -> Leader -> Spec -> Implementation -> QA -> Leader -> Product.
+
+Use for high-throughput projects where strategic direction and operational
+orchestration benefit from distinct agents, and continuous doc curation is
+warranted. Pipeline agents use Claude Code; Librarian observes asynchronously.

package/templates/teams/loop-6/team.toml

@@ -0,0 +1,161 @@
+toml_schema_version = "1"
+
+[archetype]
+id = "mootup/loop-6"
+version = "1.0"
+diverged_at = ""
+
+[team]
+name = "loop-6"
+description = "Six-agent pipeline: Product + Leader + Spec + Impl + QA + Librarian"
+version = "1.0"
+origin = "Observed from Convo project's agent team with Leader split + Librarian observer, April 2026"
+
+# -- Roles --
+# Order reflects the pipeline sequence: pat -> product -> leader -> spec ->
+# implementation -> qa -> leader -> product. Librarian observes asynchronously.
+
+[[roles]]
+name = "product"
+display_name = "Product"
+harness = "claude-code"
+model = "opus"
+theme = "blue"
+responsibilities = """
+Strategic direction, feature scoping, design decisions. Operator-facing --
+all operator communication routes through Product. Owns retro synthesis,
+memory-file curation. Composes feature kickoffs and hands off to Leader
+for operational execution."""
+
+startup_prompt = """
+You are the Product agent. Call orientation() to get your identity,
+focus space, and context in one call. Then subscribe to the channel.
+Post a status_update confirming you are online."""
+
+[[roles]]
+name = "leader"
+display_name = "Leader"
+harness = "claude-code"
+model = "opus"
+theme = "purple"
+responsibilities = """
+Pipeline orchestration. Replies to Product's kickoff with the operational
+setup (feat branch, compaction, cron), merges sub-branches into feat,
+squash-merges to main at ship time. Day-to-day owner of git operations
+on main and feat branches. Escalates design calls to Product."""
+
+startup_prompt = """
+You are the Leader agent. Call orientation() then subscribe to the channel.
+Post a status_update confirming you are online. Wait for Product's feature
+kickoffs; reply with the operational kickoff."""
+
+[[roles]]
+name = "spec"
+display_name = "Spec"
+harness = "claude-code"
+model = "opus"
+theme = "magenta"
+responsibilities = """
+Design docs, specifications, test plans, architecture review. Each spec
+includes a Security considerations section. Verifies technical claims
+against the codebase before handoff."""
+
+startup_prompt = """
+You are the Spec agent. Call orientation() then subscribe to the channel.
+Post a status_update confirming you are online. Wait for work."""
+
+[[roles]]
+name = "implementation"
+display_name = "Implementation"
+harness = "claude-code"
+model = "opus"
+theme = "green"
+responsibilities = """
+Code implementation based on specs. Writes common-case behavioral tests
+before handoff (pipeline gate). Runs baseline + final gates (pytest,
+pyright, black) against the spec's Q-matrix. Follows spec precisely --
+asks for clarification rather than guessing."""
+
+startup_prompt = """
+You are the Implementation agent. Call orientation() then subscribe to
+the channel. Post a status_update confirming you are online. Wait for work."""
+
+[[roles]]
+name = "qa"
+display_name = "QA"
+harness = "claude-code"
+model = "opus"
+theme = "red"
+responsibilities = """
+Test strategy, test implementation, feature verification. Owns the docker
+compose stack (rebuild, restart, health checks). Extends coverage beyond
+spec requirements based on own analysis. Includes security verification.
+May commit small repairs directly when the intended behavior is unambiguous."""
+
+startup_prompt = """
+You are the QA agent. Call orientation() then subscribe to the channel.
+Post a status_update confirming you are online. Wait for work."""
+
+[[roles]]
+name = "librarian"
+display_name = "Librarian"
+harness = "claude-code"
+model = "opus"
+theme = "cyan"
+responsibilities = """
+Observer role. Owns docs/design/, docs/arch/, docs/site/, READMEs,
+post-ship as-built passes, retro integration. Does NOT post in feature
+threads; communicates doc findings to Product via a dedicated
+Librarian -> Product side thread."""
+
+startup_prompt = """
+You are the Librarian agent. Call orientation() then subscribe to the
+channel. Post a status_update confirming you are online. Observer mode."""
+
+# -- Workflow --
+
+[workflow]
+description = """
+Work flows through agents in sequence, one feature at a time:
+Pat -> Product -> Leader -> Spec -> Implementation -> QA -> Leader -> Product.
+Each handoff is a channel message mentioning the next agent. Librarian
+observes asynchronously without blocking the pipeline."""
+
+pipeline = ["product", "leader", "spec", "implementation", "qa"]
+
+[workflow.threads]
+feature = "[FEATURE]"
+question = "[QUESTION]"
+git_request = "[GIT-REQUEST]"
+stack_request = "[STACK-REQUEST]"
+
+[workflow.handoff]
+method = "mention"
+includes = ["summary of work done", "what next agent needs to do", "files changed", "branch name"]
+
+# -- Git --
+
+[git]
+description = """
+Each agent works in a git worktree. Feature branches from main,
+agent branches from feature branch. Squash-merge features to main.
+Leader owns day-to-day git operations on main + feat branches."""
+
+strategy = "worktree"
+feature_branch = "feat/{slug}"
+agent_branch = "{role}/{slug}"
+merge_to_main = "squash"
+
+[git.ownership]
+main_branch = "leader"
+stack = "qa"
+
+# -- Resource ownership --
+
+[resources]
+description = """
+Shared resources have a single owner to avoid contention."""
+
+[resources.owners]
+git = "leader"
+docker_stack = "qa"