You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I understand that the LLM's limited context should be carefully crafted. That is the purpose of OpenSpec.
I love the manual separation between "proposal" and "apply" commands. Because it give me a chance to evaluate whether me and the AI or on the same page.
However, I find it strange the OpenSpec does not use these manual commands to its advantage. Why not, setup a different context for each command which is focused on the current purpose of the command? Would that not be more efficient for a limited LLM?
I do not understand why the command files are tiny (23-28 lines), but the AGENTS.md file large (456 lines). Should this not be the other way around?
Instead of having a complex explanation trying to inform the LLM how the workflow works and what should happen at each step, why not instruct the LLM, when done with your step, call openspec next ... to get the next instruction. Then let the openspec app deal with what should be loaded from which file, instead of expecting the LLM to make multiple tool calls just to figure out what should be read. Or am I misunderstanding something?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I understand that the LLM's limited context should be carefully crafted. That is the purpose of OpenSpec.
I love the manual separation between "proposal" and "apply" commands. Because it give me a chance to evaluate whether me and the AI or on the same page.
However, I find it strange the OpenSpec does not use these manual commands to its advantage. Why not, setup a different context for each command which is focused on the current purpose of the command? Would that not be more efficient for a limited LLM?
I do not understand why the command files are tiny (23-28 lines), but the AGENTS.md file large (456 lines). Should this not be the other way around?
Instead of having a complex explanation trying to inform the LLM how the workflow works and what should happen at each step, why not instruct the LLM, when done with your step, call
openspec next ...to get the next instruction. Then let the openspec app deal with what should be loaded from which file, instead of expecting the LLM to make multiple tool calls just to figure out what should be read. Or am I misunderstanding something?Beta Was this translation helpful? Give feedback.
All reactions