Design.md has Open Questions at the end #1296
-
|
I just noticed my new spec created a design.md file with Open Questions at the end. Isn't this supposed to be asked by the Agent harness before creating the design.md file? or is it because i'm using the experimental opsx:continue workflow? My previous specs has None at the end of design.md (Using propose -> apply -> archive flow) Lastly, should we address this Open Questions before we proceed to the next step (spec creation) or opxs:continue will handle this for us and choose the most recommended solution? Thanks in advance, I'm new to this. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
Hi @lance2k-da, thanks for flagging this — you found a real gap, not something you did wrong. To answer your questions directly:
I've opened #1366 to fix the underlying gap: the design instruction now tells the agent to resolve anything that would change the specs, approach, or task breakdown with you instead of parking it under Open Questions (which is now reserved for genuinely deferrable unknowns), and the tasks instruction adds a matching check so blocking questions get raised even when tasks are generated in a later session. |
Beta Was this translation helpful? Give feedback.
Hi @lance2k-da, thanks for flagging this — you found a real gap, not something you did wrong.
To answer your questions directly:
design.mdwith an "Open Questions" section, but it never said what to do with those questions. So some runs list them and some write "None" — and either way nothing in the workflow resolves them./opsx:continuewon't do it for you today — it goes straight to the next artifact, and the agent quietly picks its own answers to any open questions along the way. Answering them yourself (editde…