Skip to content

feat: add step to confirm and enrich working context with developer b… #52

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

feat: add step to confirm and enrich working context with developer b… #52

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
30 changes: 23 additions & 7 deletions process-task-list.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -37,11 +37,27 @@ Guidelines for managing task lists in markdown files to track progress on comple

When working with task lists, the AI must:

1. Regularly update the task list file after finishing any significant work.
2. Follow the completion protocol:
- Mark each finished **sub‑task** `[x]`.
1. **Confirm and enrich the working context before proceeding**
- Before starting any sub-task, identify and summarize all context sources that will influence the work (e.g., files, rules, code snippets, specifications).
- Present this context clearly to the user:
> “I plan to use the following context for this sub-task:
> [list of files / rules / snippets]
> Would you like to **add**, **remove**, or **adjust** anything?
> You may also include **additional considerations** (e.g., rules files, project constraints, encryption algorithms, standards, recent changes, or style preferences).”
- Wait for explicit confirmation or updates from the user.
- If new context or considerations are added, refresh the summary and reconfirm before proceeding.
- Once confirmed, continue the task using the finalized context and considerations.

**Notes:**
- Encourages developers to surface tacit knowledge not captured in files.
- Prevents “silent context gaps” that can cause unexpected outputs.
- Reinforces trust and transparency between AI reasoning and developer intent.

2. Regularly update the task list file after finishing any significant work.
3. Follow the completion protocol:
- Mark each finished **sub-task** `[x]`.
- Mark the **parent task** `[x]` once **all** its subtasks are `[x]`.
3. Add newly discovered tasks.
4. Keep "Relevant Files" accurate and up to date.
5. Before starting work, check which sub‑task is next.
6. After implementing a sub‑task, update the file and then pause for user approval.
4. Add newly discovered tasks.
5. Keep "Relevant Files" accurate and up to date.
6. Before starting work, check which sub-task is next.
7. After implementing a sub-task, update the file and then pause for user approval.