feat: add step to confirm and enrich working context with developer b… #52
+23
−7
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…efore sub-task execution Currently, the developer has no visibility into what context (files, rules, snippets, or metadata) is being passed to the LLM when executing a sub-task. This creates a “blind spot” that can lead to unintended reasoning or overlooked constraints. This change introduces a new AI instruction: before performing any sub-task, the AI must summarize the working context and explicitly confirm it with the developer. The developer can review, add, or adjust context sources and considerations before the task proceeds. This ensures transparency, prevents silent context gaps, and builds trust between the developer and the AI’s reasoning process.
|
This is a neat idea, though I would almost want this desired shared context recorded somewhere. This is what the Relevant Files and Notes sections in the plan are for, but I can appreciate your desire to control what goes into the task level. Perhaps an additional research/context file can be introduced, where this newly introduced research file accommodates a particular plan file. or specific task in a plan file? The idea would be to really just house a summary of relevant context and not necessarily couple it to the planning step itself. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…efore sub-task execution
Currently, the developer has no visibility into what context (files, rules, snippets, or metadata) is being passed to the LLM when executing a sub-task. This creates a “blind spot” that can lead to unintended reasoning or overlooked constraints.
This change introduces a new AI instruction: before performing any sub-task, the AI must summarize the working context and explicitly confirm it with the developer. The developer can review, add, or adjust context sources and considerations before the task proceeds.
This ensures transparency, prevents silent context gaps, and builds trust between the developer and the AI’s reasoning process.