agents: discussion mode — devs talk in threads, build only on explicit signal #102
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: gitea/agents#102
Reference in New Issue
Block a user
Mentioning a dev = conversation (in-thread reply, no branch/PR). Building starts only on: PR-thread resume, pm's please proceed with issue… delegation (humans can write it too), or qa's bounce. @pm gains
ASK: @<dev> <question>to consult devs before planning. Unit-tested phrase routing + ASK parsing.Mentioning a dev agent no longer spawns a branch + PR machinery. It is a CONVERSATION by default: the dev reads what it needs and replies in-thread. - route.sh: workmode=build|discuss for mode=pr agents. Build ONLY on the explicit signals: PR-thread comments (resume), the pm delegation template ("please proceed with issue …" — a human can write it too), or the qa bounce ("please address my review …"). Everything else = discuss: no branch prep, no "🔨 Building" notice. - run-agent.sh: discussion ACTION for devs (read-only consult, no edits/ commits/markers). @pm gains 'ASK: @<dev> <question>' to consult devs before planning — gather feasibility/effort input, then DELEGATE when enough is known. One ASK per reply; never ASK+DELEGATE together. - publish.sh: pm ASK handler posts the question as a discussion trigger; dev discuss path posts the reply (+run report) and skips ALL git/PR machinery (stray edits discarded). ASK marker stripped from visible replies. - agent.yml: WORKMODE threaded to Run-agent + Publish. README documents it. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>