@vheins/local-memory-mcp 0.5.17 → 0.5.18
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
@@ -21,13 +21,14 @@ Please follow this strict execution flow:
|
|
|
21
21
|
1. **Identify Repository**: Determine the current repository name (e.g., from git config or workspace context).
|
|
22
22
|
2. **Fetch Tasks**: Call `local-memory-mcp` MCP tools `task-list` for the identified repository for statuses 'pending' and 'in_progress'.
|
|
23
23
|
3. **Filter Stale**: Identify 'in_progress' tasks that are **stale** (stale is defined as > 30 Minutes without update, often because an agent stopped or crashed).
|
|
24
|
-
4. **
|
|
24
|
+
4. **Task Execution Loop**: You MUST process tasks EXACTLY ONE AT A TIME (STRICT) unless your agent environment supports sub-agent orchestration and parallel execution. If sub-agent features are unavailable, DO NOT update multiple tasks to 'in_progress' simultaneously. For each task you select:
|
|
25
25
|
- **Start**: Call `local-memory-mcp` MCP tools `task-update` to set status='in_progress' for this task ONLY. Provide current agent/role information in the metadata.
|
|
26
26
|
- **Execute**: Perform the work described in the task title and description.
|
|
27
27
|
- **Inspect Codebase Logic & Documentation First (MANDATORY)**: Before marking anything done, inspect the relevant code paths, call sites, configs, tests, and affected modules in the repository. Also read the relevant documentation, as it might need to be updated or fixed. Do not infer correctness from file presence alone.
|
|
28
28
|
- **Validate Behavior (MANDATORY)**: Ensure the implementation logic satisfies the task intent and follows project standards. Validation must focus on behavior, control flow, data flow, and integration points, not just whether a file/class/function exists.
|
|
29
29
|
- **Complete Only With Evidence**: Call `local-memory-mcp` MCP tools `task-update` to set status='completed' only after recording concrete evidence in the 'comment' field. The comment must include: files inspected, logic verified, checks/tests run (or why they could not run), and the exact reason the task is considered complete.
|
|
30
30
|
- **Compact Context**: Summarize key learnings, decisions, and patterns discovered during task execution. Store critical insights as memory entries (type: 'code_fact' or 'pattern') using `local-memory-mcp` MCP tools `memory-store`.
|
|
31
|
+
- **Retrospective**: Invoke the `learning-retrospective` skill. If the skill is unavailable, use the `learning-retrospective` prompt from `local-memory-mcp` to extract and store durable knowledge (mistakes, decisions, patterns) from this task.
|
|
31
32
|
- **Commit**: Perform an atomic git commit and push for the changes made in the task.
|
|
32
33
|
- **Handoff**: Use `local-memory-mcp` MCP tools `task-update` to document **detailed fix steps**, milestones, project-specific knowledge gained during execution, and validation evidence. If complex, decompose into smaller tasks using `local-memory-mcp` MCP tools `task-create`.
|
|
33
34
|
- **Next**: Repeat this loop for the next 'pending' or 'stale' task.
|