fix: pass the issue title+body to the dev agent so agent/dev works without a plan #20
No reviewers
Labels
No labels
agent
coordinate
agent
dev
agent
plan
agent
reflect
agent
test
agent
triage
ai/off
blocked
night
blocked
usage
loop
1
loop
2
loop
3
needs/approval
needs/human
needs/input
needs/review
plan/approved
run/night
state
blocked
state
building
state
passed
state
planning
state
testing
tier
fable
tier
haiku
tier
local
tier
opus
tier
sonnet
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
valssi-public/agent-workflows!20
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/dev-prompt-includes-issue"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem
dev.yamlbuilds the model prompt from two sources only: the## Implementation plan (agent)comment and the tester's## Test findingscomment. The issue's own title and body are never passed.
That is fine on the designed path (
agent/plan→plan/approved→ implement),but it makes
agent/devunusable as a standalone trigger. Label a fresh issueagent/devand$PLANis empty, so the agent is told "implement the approvedplan below" with nothing below it and no other statement of the task. It
produces no commit, the
progress=nobranch fires, and the issue is parked toneeds/human.This matters for queueing work ahead of a usage reset:
agent/devis the labelyou would reach for to queue a small, already-understood change without spending
a planning run on it.
Change
=== ISSUE #N ===section, ahead of the plan.$PLANis empty, substitute an explicit instruction to work from theissue text and keep the change tightly scoped, instead of emitting an empty
section.
CHECKPOINTnow logs the issue title, so the run log shows what the agent wasactually given.
No behaviour change on the
plan/approvedpath — the plan is still the primaryinstruction there, now with the issue as framing.
Merge order
Cut from
main. It touches only the build step's prompt region, so it mergescleanly with
feat/runner-injected-credentials(which touches the credentialsregion of the same file) in either order. Note that until that branch is merged,
no route runs at all — every route file on
mainstill carries thesecrets:block under
on.workflow_callthat makes the file unparseable.