Project-specific instructions
Document conventions where they will be found before the task starts.
Move between client repositories with deliberate project context, useful handoff notes and review that stays attached to the work.
Find your starting pointTEAM · PLANNED
A small studio may handle maintenance, product work and urgent fixes across several repositories. The challenge is not simply running more agents. It is knowing which project, environment and decision each task belongs to.
Qodarium's shared-project direction can support a compact internal development workflow. It is not a claim of multi-tenant client isolation, customer portals or compliance certification.
Choose the right repository, host and credentials before an agent begins.
Describe the requested outcome and the files or systems that should remain untouched.
Give the next developer the changed surface, checks performed and unresolved questions.
Review and release through the client's established repository and deployment workflow.
Document conventions where they will be found before the task starts.
Do not let convenience blur the boundary between client environments.
A task waiting for review should have an identifiable next owner.
Keep a concise account of what changed and why for future maintenance.
Guest and external-client roles are not part of the initial validation scope.
Production deployment orchestration is outside the initial product scope.
A workspace that holds the context while you focus on what comes next.