orchestrator-agent
8ddae78551
Co-authored-by: orchestrator-agent <orchestrator@cubecraftlabs.com> Co-committed-by: orchestrator-agent <orchestrator@cubecraftlabs.com>
1.2 KiB
Reusing the development cycle prompt
ORCHESTRATOR-PROMPT.template.md is the current NestQuest controller
prompt with project-specific names, models, branches, identities, and launcher
paths replaced by placeholders. nestquest.profile.json is the working
example. Render a concrete prompt with:
scripts/render-cycle-prompt templates/nestquest.profile.json --output /tmp/opencode/nestquest-prompt.md
For another project, copy the profile and set its project name, tracker, context store, models, branch names, release owner, example IDs, review account, and installed launcher paths. Review the rendered result section by section, especially task/feature semantics, release rules, permissions, review gates, and the host runtime section. The template assumes an OpenCode controller, a feature/task tracker, a versioned context store, a code host, and a separate reviewer and approver. Adapt those sections when the project's systems differ.
Publish the reviewed rendered prompt into that project's context store with its version check. Give the project its own agent definitions, service unit, broker, and OpenCode start/stop commands. The template itself does not start a controller or register another project.