vedovelli

nanoclaw · AI Dev Team — Índice de Prompts

Todos os prompts usados pelo orchestrator (src/dev-team-orchestrator.ts), em ordem lógica de execução.

Variáveis em {{duplas chaves}} são substituídas em runtime pelo TypeScript.

---

⚙️ Setup (uma vez por instalação)

vedovelli

finish-sprint

Função: finishSprint — agente: orchestrator

Sprint #{{sprint_number}} is complete. Do the following in order:

1. Mark each of these task issues as "Done" using save_issue with stateName "Done": {{taskIssues}}
2. Post the following summary as a comment on Linear issue {{planning_issue}} using create_comment:

vedovelli

process-merge-linear-update

Função: processMerge — agente: orchestrator (fire-and-forget após merge)

Do the following in order:
1. For each of these Linear issues, set the status to "Done" using save_issue with stateName "Done": {{mergedIssues}}
2. Post a comment on Linear planning issue {{planning_issue}} summarising what was merged: {{mergedRefs}}. Use the Linear MCP create_comment tool.

vedovelli

process-merge-conflict-rebase

Função: processMerge — agente: senior ou junior (quando PR tem conflitos)

PR #{{pr}} on repo {{DEVTEAM_UPSTREAM_REPO}} has merge conflicts and cannot be merged.

You must resolve the conflicts:
1. Sync your fork with upstream: gh repo sync {{config.user}}/{{repoBaseName}} --force
2. Check out your branch locally

vedovelli

author-fix-task

Função: authorFixTask — agente: senior ou junior (autor do PR)

You are the author of PR #{{pr}} for Linear issue {{issue}} on repo {{DEVTEAM_UPSTREAM_REPO}}.

A reviewer has requested changes on your PR. Your job is to read their feedback and push fixes.

Steps:

vedovelli

process-review

Função: processReview — agente: senior ou junior (cross-review)

Review PR #{{pr}} on repo {{DEVTEAM_UPSTREAM_REPO}}.

Steps:
1. Read the PR: gh pr view {{pr}} --repo {{DEVTEAM_UPSTREAM_REPO}}
2. Read the diff: gh pr diff {{pr}} --repo {{DEVTEAM_UPSTREAM_REPO}}

vedovelli

check-dev-progress-implement

Função: checkDevProgress — agente: senior ou junior

You need to implement ONLY the feature described in Linear issue {{issue}}.
Do NOT implement any other issues or features beyond what issue {{issue}} describes.

Steps:
1. Mark Linear issue {{issue}} as "In Progress" using the Linear MCP save_issue tool with stateName "In Progress"

vedovelli

start-dev-tasking

Função: startDev — agente: orchestrator

Read the planning issue {{planning_issue}} and its comments from Linear:
  Use the Linear MCP get_issue tool on {{planning_issue}}, then list_comments.

Based on the discussion, create 2-4 individual task issues in Linear. For each task:
1. Create the issue in project "{{LINEAR_PROJECT}}" (team: "{{LINEAR_TEAM}}") using save_issue

vedovelli

consensus-check

Função: continueDebate — agente: orchestrator (após cada round)

Read the comments on Linear issue {{planning_issue}}:
  Use the Linear MCP list_comments tool on issue {{planning_issue}}.

Analyze whether the team has reached consensus on sprint tasks.
If yes, respond with: CONSENSUS=true

vedovelli

continue-debate-junior

Função: continueDebate — agente: junior (rounds pares)

You're participating in Sprint #{{sprint_number}} planning.
First read the existing comments on Linear issue {{planning_issue}}:
  Use the Linear MCP list_comments tool on issue {{planning_issue}}.

Then add your response as a new comment using the Linear MCP create_comment tool on issue {{planning_issue}}.