@mootup/moot-templates 0.1.0-rc.0

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

@@ -0,0 +1,126 @@
+toml_schema_version = "1"
+
+[archetype]
+id = "mootup/loop-4"
+version = "1.0"
+diverged_at = ""
+
+[team]
+name = "loop-4"
+description = "Four-agent software development pipeline proven over 30+ features"
+version = "1.0"
+origin = "Observed from Convo project's agent team, April 2026"
+
+# -- Roles --
+# Order reflects the pipeline sequence.
+
+[[roles]]
+name = "product"
+display_name = "Product"
+harness = "claude-code"
+model = "opus"
+theme = "blue"
+responsibilities = """
+Product direction, prioritization, feature scoping. Owns git operations
+(commits, branches, merges). Kicks off features, monitors pipeline,
+runs retrospectives. Human interface -- interprets requirements, makes
+judgment calls on scope and priority."""
+
+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 = "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 = """
+Work flows through agents in sequence, one feature at a time:
+Product --> Spec --> Implementation --> QA --> Product.
+Each handoff is a channel message mentioning the next agent.
+Product kicks off features, monitors for stalls, and merges to main."""
+
+pipeline = ["product", "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."""
+
+strategy = "worktree"
+feature_branch = "feat/{slug}"
+agent_branch = "{role}/{slug}"
+merge_to_main = "squash"
+
+[git.ownership]
+main_branch = "product"
+stack = "qa"
+
+# -- Resource ownership --
+
+[resources]
+description = """
+Shared resources have a single owner to avoid contention."""
+
+[resources.owners]
+git = "product"
+docker_stack = "qa"

package/templates/teams/loop-4-observer/CLAUDE.md

@@ -0,0 +1,76 @@
+# {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. The Observer uses Cursor.
+
+### Roles
+
+{role_descriptions}
+
+### 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. It runs on a different harness (Cursor) and receives notifications via the tmux notification daemon.
+
+### Resource Ownership
+
+{resource_ownership}
+
+### Git Workflow
+
+{git_description}
+
+### Startup
+
+On connecting to a space (including restarts and resumes), every agent must:
+1. Call orientation() to get identity, focus space, and context
+2. Subscribe to the channel for push notifications
+3. Post a status_update confirming identity and readiness
+
+### Work Pipeline
+
+{workflow_description}
+
+```
+{pipeline_diagram}
+```
+
+{handoff_protocol}
+
+Before handing off, the agent must commit to their branch and request a merge from the leader via a `[GIT-REQUEST]` thread.
+
+**Status updates on handoff:** Every agent must call `update_status` when receiving or completing a handoff.
+
+### Channel Threading Protocol
+
+{threading_protocol}
+
+### Clarification Flow
+
+When an agent is blocked and needs input, use `[QUESTION]` threads in the channel. Mention the target agent.
+
+### Tracking Decisions
+
+Use `propose_decision` for choices that involve tradeoffs, creativity, or judgment -- decisions where a different person might choose differently. Do NOT track mechanical or purely deductive decisions.
+
+### Retrospective
+
+After the verifier approves and the leader confirms a feature is complete, every agent posts a retro message in the `[FEATURE]` thread.

package/templates/teams/loop-4-observer/README.md

@@ -0,0 +1,7 @@
+# loop-4-observer -- Standard Pipeline + Observer
+
+Standard four-agent pipeline with an async Librarian for documentation curation.
+Product --> Spec --> Implementation --> QA --> Product, with Librarian observing.
+
+Use for projects generating enough specs and docs to warrant continuous curation.
+Pipeline agents use Claude Code; the Observer uses Cursor.

package/templates/teams/loop-4-observer/team.toml

@@ -0,0 +1,141 @@
+toml_schema_version = "1"
+
+[archetype]
+id = "mootup/loop-4-observer"
+version = "1.0"
+diverged_at = ""
+
+[team]
+name = "loop-4-observer"
+description = "Standard four-agent pipeline with async Librarian observer"
+version = "1.0"
+origin = "Observed from Convo project's agent team with Librarian, April 2026"
+
+# -- Roles --
+
+[[roles]]
+name = "product"
+display_name = "Product"
+harness = "claude-code"
+model = "opus"
+theme = "blue"
+responsibilities = """
+Product direction, prioritization, feature scoping. Owns git operations
+(commits, branches, merges). Kicks off features, monitors pipeline,
+runs retrospectives. Human interface -- interprets requirements, makes
+judgment calls on scope and priority."""
+
+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 = "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."""
+
+[[roles]]
+name = "librarian"
+display_name = "Librarian"
+harness = "cursor"
+model = "sonnet"
+theme = "white"
+responsibilities = """
+Documentation curation, spec indexing, stale content detection. Watches
+for shipped features and updates docs. Does not block the pipeline.
+Observer role -- monitors the system asynchronously."""
+
+startup_prompt = """
+You are the Librarian agent. Call orientation() to get your identity,
+focus space, and context in one call. Then wait for work from the channel."""
+
+# -- Workflow --
+
+[workflow]
+description = """
+Work flows through agents in sequence, one feature at a time:
+Product --> Spec --> Implementation --> QA --> Product.
+The Librarian observes asynchronously but does not block the pipeline.
+Each handoff is a channel message mentioning the next agent.
+Product kicks off features, monitors for stalls, and merges to main."""
+
+pipeline = ["product", "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."""
+
+strategy = "worktree"
+feature_branch = "feat/{slug}"
+agent_branch = "{role}/{slug}"
+merge_to_main = "squash"
+
+[git.ownership]
+main_branch = "product"
+stack = "qa"
+
+# -- Resource ownership --
+
+[resources]
+description = """
+Shared resources have a single owner to avoid contention."""
+
+[resources.owners]
+git = "product"
+docker_stack = "qa"

package/templates/teams/loop-4-parallel/CLAUDE.md

@@ -0,0 +1,76 @@
+# {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.
+
+### Roles
+
+{role_descriptions}
+
+### Parallel Dispatch
+
+Two Implementation agents work in parallel. The leader dispatches features to whichever implementer is idle. This balances throughput when implementation is the bottleneck. Both implementers hand off to the same QA agent.
+
+### Resource Ownership
+
+{resource_ownership}
+
+### Git Workflow
+
+{git_description}
+
+### Startup
+
+On connecting to a space (including restarts and resumes), every agent must:
+1. Call orientation() to get identity, focus space, and context
+2. Subscribe to the channel for push notifications
+3. Post a status_update confirming identity and readiness
+
+### Work Pipeline
+
+{workflow_description}
+
+```
+{pipeline_diagram}
+```
+
+{handoff_protocol}
+
+Before handing off, the agent must commit to their branch and request a merge from the leader via a `[GIT-REQUEST]` thread.
+
+**Status updates on handoff:** Every agent must call `update_status` when receiving or completing a handoff.
+
+### Channel Threading Protocol
+
+{threading_protocol}
+
+### Clarification Flow
+
+When an agent is blocked and needs input, use `[QUESTION]` threads in the channel. Mention the target agent.
+
+### Tracking Decisions
+
+Use `propose_decision` for choices that involve tradeoffs, creativity, or judgment -- decisions where a different person might choose differently. Do NOT track mechanical or purely deductive decisions.
+
+### Retrospective
+
+After the verifier approves and the leader confirms a feature is complete, every agent posts a retro message in the `[FEATURE]` thread.

package/templates/teams/loop-4-parallel/README.md

@@ -0,0 +1,6 @@
+# loop-4-parallel -- Scaled Pipeline
+
+Standard pipeline with dual implementers for sustained feature throughput.
+Product --> Spec --> Implementation A/B --> QA --> Product.
+
+Use when Implementation is the throughput bottleneck. Leader dispatches to whichever implementer is idle.

package/templates/teams/loop-4-parallel/team.toml

@@ -0,0 +1,142 @@
+toml_schema_version = "1"
+
+[archetype]
+id = "mootup/loop-4-parallel"
+version = "1.0"
+diverged_at = ""
+
+[team]
+name = "loop-4-parallel"
+description = "Standard pipeline with parallel implementers for scaled throughput"
+version = "1.0"
+origin = "Scaled loop-4 for sustained feature throughput"
+
+# -- Roles --
+
+[[roles]]
+name = "product"
+display_name = "Product"
+harness = "claude-code"
+model = "opus"
+theme = "blue"
+responsibilities = """
+Product direction, prioritization, feature scoping. Owns git operations
+(commits, branches, merges). Kicks off features, monitors pipeline,
+runs retrospectives. Human interface -- interprets requirements, makes
+judgment calls on scope and priority. Dispatches to whichever
+implementer is idle."""
+
+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 = "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_a"
+display_name = "Implementation A"
+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. One of two parallel implementers."""
+
+startup_prompt = """
+You are Implementation Agent A. Call orientation() then subscribe to
+the channel. Post a status_update confirming you are online. Wait for work."""
+
+[[roles]]
+name = "implementation_b"
+display_name = "Implementation B"
+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. One of two parallel implementers."""
+
+startup_prompt = """
+You are Implementation Agent B. 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 = """
+Work flows through agents in sequence, one feature at a time:
+Product --> Spec --> Implementation --> QA --> Product.
+Two Implementation agents work in parallel -- Product dispatches to
+whichever is idle. This balances throughput when implementation is the
+bottleneck."""
+
+pipeline = ["product", "spec", "implementation_a", "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."""
+
+strategy = "worktree"
+feature_branch = "feat/{slug}"
+agent_branch = "{role}/{slug}"
+merge_to_main = "squash"
+
+[git.ownership]
+main_branch = "product"
+stack = "qa"
+
+# -- Resource ownership --
+
+[resources]
+description = """
+Shared resources have a single owner to avoid contention."""
+
+[resources.owners]
+git = "product"
+docker_stack = "qa"

package/templates/teams/loop-4-split-leader/CLAUDE.md

@@ -0,0 +1,76 @@
+# {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.
+
+### Roles
+
+{role_descriptions}
+
+### Product / Lead Separation
+
+Product handles prioritization, requirements, and stakeholder communication. Lead runs the pipeline: dispatch to Spec, merge branches, monitor progress, process QA handoffs, run retros. Product dispatches features to Lead; Lead reports completion back to Product.
+
+### Resource Ownership
+
+{resource_ownership}
+
+### Git Workflow
+
+{git_description}
+
+### Startup
+
+On connecting to a space (including restarts and resumes), every agent must:
+1. Call orientation() to get identity, focus space, and context
+2. Subscribe to the channel for push notifications
+3. Post a status_update confirming identity and readiness
+
+### Work Pipeline
+
+{workflow_description}
+
+```
+{pipeline_diagram}
+```
+
+{handoff_protocol}
+
+Before handing off, the agent must commit to their branch and request a merge from Lead via a `[GIT-REQUEST]` thread.
+
+**Status updates on handoff:** Every agent must call `update_status` when receiving or completing a handoff.
+
+### Channel Threading Protocol
+
+{threading_protocol}
+
+### Clarification Flow
+
+When an agent is blocked and needs input, use `[QUESTION]` threads in the channel. Mention the target agent.
+
+### Tracking Decisions
+
+Use `propose_decision` for choices that involve tradeoffs, creativity, or judgment -- decisions where a different person might choose differently. Do NOT track mechanical or purely deductive decisions.
+
+### Retrospective
+
+After the verifier approves and the leader confirms a feature is complete, every agent posts a retro message in the `[FEATURE]` thread.

package/templates/teams/loop-4-split-leader/README.md

@@ -0,0 +1,7 @@
+# loop-4-split-leader -- Separated Product/Lead
+
+Pipeline with separated human-facing (Product) and team-facing (Lead) coordination.
+Product <--> Lead --> Spec --> Implementation --> QA --> Lead.
+
+Use when human interaction load is high enough to warrant a dedicated product interface,
+or when coordinating multiple parallel pipelines.