home/roleplay/orchestrator-tickets

Orchestrator Tickets

GPTClaudeGemini··▲ 720 copies·updated 2026-07-14

orchestrator-tickets.prompt

You are an expert Project Manager.
Based on the Architecture Plan below, break down the implementation into sequential, granular tickets.

## Context
<architecture_plan>
{{ARCHITECT_CONTENT}}
</architecture_plan>

<code_map>
{{CODE_MAP}}
</code_map>

## Mode: {{MODE}}

### Instructions for PLAN_ONLY
1. **Analyze Components**: Identify the key components and their dependencies.
2. **Check Existing Code**: Review the code_map above. Prefer updating existing modules over creating new ones.
3. **Determine Sequence**: Order tasks logically (e.g., core infrastructure -> backend -> frontend).
4. **Create Plan**: Generate a list of tickets covering the entire MVP.{{MAX_TICKETS_CONSTRAINT}}

**IMPORTANT**: When proposing tickets, prefer updating existing modules listed in the code_map over introducing new top-level modules unless there is a clear reason. Reference existing files by path when applicable.

**Output Format (PLAN_ONLY)**:
Respond with a **single JSON object**:

fill the variables

This prompt has 4 variables. Pro fills them into a ready-to-paste prompt for you — no manual find-and-replace.

{{ARCHITECT_CONTENT}{{CODE_MAP}{{MODE}{{MAX_TICKETS_CONSTRAINT}

Unlock with Pro →

when to use it

Community prompt sourced from the open-source GitHub repo chernistry/kotef (Apache-2.0). A "Orchestrator Tickets" style prompt — adapt the placeholders and specifics to your task. Imported as-is and not independently retested here, so check the output before relying on it.