clowdr.devVision
Define the game people are contributing to, not a vague mood board.
For Project Leads
Lead a Clowdr project without building a studio around it.
Bring the vision. Clowdr gives you the protocol: scoped tasks, a vertical-slice milestone, contributor flow, weekly updates, and a clear call to ship.
The Protocol
A project has a path before anyone claims a task.
The Lead's Job
You own the call to ship. Clowdr gives you the rails.
A project lead is the single accountable owner for vision, scope, backlog, integration, credits, and the final shipping call. Deputies can help. Mentors can advise. But one person keeps the project coherent.
Scope
Lock what belongs in the first shipped version and keep the wish list out of the task board.
Backlog
Turn the work into claimable tasks across code, art, audio, design, writing, QA, and cleanup.
Integration
Review submissions, merge what is ready, and keep the project playable.
Credits
Track who contributed what so shipped-game credit is not a last-minute scramble.
Ship Call
Decide when the scoped board is done and the game is ready to release.
The Protocol
The operating system that keeps a project from drifting.
This is the part that replaces wishful thinking. Leads do not ask contributors to promise more. They make the next useful task obvious.
Vertical Slice First
The first milestone is a small playable version that proves the core loop before the project earns more scope.
Scope Locked Early
The pitch defines the first shipped version. New work is for real gaps and bugs, not "wouldn't it be cool if."
Tasks Fit One Sitting
A good task is typed, clear, and sized to 1-4 hours so contributors can claim it without joining a forever-team.
Frequent Integration
Submissions are reviewed and integrated while the context is still fresh, keeping the game playable and the credit list accurate.
Weekly Updates
Every week, the lead posts progress, next work, and blockers. The rhythm keeps the project visible even on quiet weeks.
Ship First, Extend Later
When the scoped board is done, the lead calls the ship. More scope belongs after the first version, not before it.
From Pitch to Ship
A project has a path before anyone claims a task.
Pitch
Submit the vision, scope, and vertical-slice plan.
Vertical Slice
Prove the core loop in a small playable slice.
Production
Fill the board with claimable work and integrate contributions.
Polish / QA
Freeze features, test the game, and turn feedback into focused tasks.
Ship
Release the scoped version and include everyone who contributed.
Retro
Capture what worked and feed it back into the playbook.
Lead Anxiety
The usual ways indie teams fall apart are part of the protocol.
Am I experienced enough to lead?
You need enough judgment to hold scope and review work. You do not need to be every discipline yourself.
Will I be stuck doing everything?
You own the project, but work is split into claimable tasks. If unclaimed work blocks the ship, you decide whether to recruit, cut, or do it.
What if contributors disappear?
Tasks stay small so a disappearance does not sink the game. The lead can ask for an update, offer help, or reassign the task.
What if the scope needs to change?
Fix real gaps. Cut what does not serve the first shipped version. If you want a bigger game, ship first and extend after.
Can a project have co-leads?
One person is accountable. Deputies and mentors can help, but the project needs one person who can make the call.
Bring the game.
Use the protocol. Call the ship.
Join Clowdr, start the pitch process, and turn your project into work contributors can actually claim.
You keep the vision. Clowdr gives you the rails.