Say whether going without approval covers design's decisions #140

Open
opened 2026-10-18 21:57:06 +02:00 by motoko · 0 comments
Collaborator

Where

.agents/skills/get-approval/SKILL.md step 2 and .agents/skills/design/SKILL.md step 3, at 88f3ec6.

Evidence

get-approval lets the user go without approval for a task, the tasks, or the session. For approval through a pull request it adds that "design still asks its decisions". For a plain instruction to go without approval, it says nothing about design. design step 3 asks the user each open decision, one at a time, with no exception.

Scenario

A user says "go alone, take the recommended decisions" and leaves. One agent reads the instruction as covering only the gates, so it stops at design and waits for an answer that won't come until the user is back. Another reads it as covering decisions too, so it picks its own recommendations. Both readings fit the text, so the same instruction gives different runs.

Smallest fix

Say in get-approval step 2 whether an instruction to go without approval also covers design's decisions. One option is to cover them only when the user says so, as in "take the recommended decisions", with each choice recorded in Decisions as the agent's choice under that instruction. Either way, the design workflow page should match.

## Where `.agents/skills/get-approval/SKILL.md` step 2 and `.agents/skills/design/SKILL.md` step 3, at 88f3ec6. ## Evidence `get-approval` lets the user go without approval for a task, the tasks, or the session. For approval through a pull request it adds that "`design` still asks its decisions". For a plain instruction to go without approval, it says nothing about `design`. `design` step 3 asks the user each open decision, one at a time, with no exception. ## Scenario A user says "go alone, take the recommended decisions" and leaves. One agent reads the instruction as covering only the gates, so it stops at `design` and waits for an answer that won't come until the user is back. Another reads it as covering decisions too, so it picks its own recommendations. Both readings fit the text, so the same instruction gives different runs. ## Smallest fix Say in `get-approval` step 2 whether an instruction to go without approval also covers `design`'s decisions. One option is to cover them only when the user says so, as in "take the recommended decisions", with each choice recorded in Decisions as the agent's choice under that instruction. Either way, the `design` workflow page should match.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
claudiomaradonna/agent-foundry#140
No description provided.