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
Based on suggested videos on YouTube from Den Delimarsky and other authors I still don’t quite understand the concept of clarifying implementation details - how is the model supposed to know that tasks.md or plan.md contain inaccuracies/errors or require clarification.
I can interact with the model directly in the chat, but it’s more convenient to do this through a file where I describe all the necessary clarifications for the new plan. It seems that a separate files can make it more simple:
clarifications.md would be useful - the single source of corrections/clarifications for the plan and tasks
(optional) decisions.md as the decision log
(optional) questions.md for open questions (if you don’t want to keep them in clarifications.md).
Then, using commands like /update scope=plan or /update scope=tasks, we can ask the model to make clarifications or apply corrections based on clarifications.md / decisions.md / questions.md, which contain the user input.
Additionally, the command /validate will be useful to validate integrity (check for contradictions, dangling task references, etc).
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.
-
Hi all,
Based on suggested videos on YouTube from Den Delimarsky and other authors I still don’t quite understand the concept of clarifying implementation details - how is the model supposed to know that
tasks.mdorplan.mdcontain inaccuracies/errors or require clarification.I can interact with the model directly in the chat, but it’s more convenient to do this through a file where I describe all the necessary clarifications for the new plan. It seems that a separate files can make it more simple:
Then, using commands like
/update scope=planor/update scope=tasks, we can ask the model to make clarifications or apply corrections based onclarifications.md/decisions.md/questions.md, which contain the user input.Additionally, the command
/validatewill be useful to validate integrity (check for contradictions, dangling task references, etc).Beta Was this translation helpful? Give feedback.
All reactions