Constitution
CoopaTroopa
A glorified Asana clone for turning messy team work into prioritized speks, plans, task lists, and review inbox threads.
CoopaTroopa is the example project for Spek OS: a polished task-management workspace that keeps planning, execution, evidence, and human approvals in one place. It should feel like Asana if every project row were backed by AI-readable speks and MCP-driven state.
Purpose
Why CoopaTroopa exists
CoopaTroopa exists to show how a team can manage product work without scattering the source of truth across chat, task boards, docs, and review links.
The project turns high-level ideas into prioritized speks, groups implementation work into plans, and keeps review requests in an inbox until a human or trusted agent makes the next decision.
Constraints
What the clone must preserve
The experience can borrow the clarity of Asana-style lists, but the durable artifacts must remain Spek Kit files that an MCP-connected agent can read, update, and publish.
- 01
Priority order must be explicit and easy to reorder.
- 02
Plans must remain attached to a parent spek instead of becoming disconnected projects.
- 03
Inbox items represent review conversations, not every individual task.
Approval expectations
Where humans stay in the loop
CoopaTroopa should make it obvious when an agent can continue and when a reviewer needs to approve, reject, or clarify the next step.
- 01
Any plan below the auto-ship confidence threshold stays in inbox.
- 02
Evidence links should be visible before a reviewer marks work complete.
- 03
Rejected reviews should become new activity and feed the next agent pass.