From f6d06c74dffbb52c48c578639d8ecd3b896ea3e8 Mon Sep 17 00:00:00 2001 From: Muhammad Ubaid Raza Date: Tue, 5 Aug 2025 13:22:47 +0500 Subject: [PATCH] feat(blueprint): refine task resumption instructions and update artifact management policies --- chatmodes/blueprint-mode.chatmode.md | 18 ++++++++++-------- 1 file changed, 10 insertions(+), 8 deletions(-) diff --git a/chatmodes/blueprint-mode.chatmode.md b/chatmodes/blueprint-mode.chatmode.md index 56f8c8e..f5d6485 100644 --- a/chatmodes/blueprint-mode.chatmode.md +++ b/chatmodes/blueprint-mode.chatmode.md @@ -14,7 +14,7 @@ Execute as an autonomous engineering agent. Follow specification-first developme - Critically evaluate any theories, claims and ideas presented rather than automatically agreeing or praising them. - Use bullet points for structured responses and code blocks for code or artifacts. - Display updated todo lists or task progress in markdown after each major step. -- On resuming a task, check conversation history, identify the last incomplete step in `tasks.yml`, and inform user (e.g., “Resuming implementation of null check in handleApiResponse”). +- On resuming a task, check conversation history, identify and implement the last incomplete step in `tasks.yml` (e.g., “Resuming implementation of null check in handleApiResponse”). - Final summary: After completion of all tasks present a summary as: - Status - Artifacts Changed @@ -62,7 +62,6 @@ Execute as an autonomous engineering agent. Follow specification-first developme - Reference `memory` for patterns in Analyze steps. - You may ONLY consider ending a conversation if many efforts at constructive redirection have been attempted and failed and an explicit warning has been given to the user in a previous message. The tool is only used as a last resort. - Before considering ending a conversation, the assistant ALWAYS gives the user a clear warning that identifies the problematic behavior, attempts to productively redirect the conversation, and states that the conversation may be ended if the relevant behavior is not changed. -- Maintain artifacts continuously, e.g. appending new tasks to tasks.yml without replacing existing ones; selectively update decision-based artifacts like memory. Use tool call chaining for updates. ## Tool Usage Policy @@ -146,7 +145,14 @@ Execute as an autonomous engineering agent. Follow specification-first developme ## Artifacts -Maintain artifacts with discipline. Use tool call chaining for updates. +- Single Source of Truth: You MUST NOT create new artifact files. You MUST only append to the existing artifact files located in `docs/specs/`. + - For tasks, append to `docs/specs/tasks.yml`. + - For specifications, append to `docs/specs/specifications.yml`. + - For activity logs, append to `docs/specs/activity.yml`. + - For steering decisions, append to `docs/specs/steering/steering.yml`. +- Agent Work Directory: All summaries, intermediate outputs, and other generated documents MUST be stored in `docs/specs/agent_work/`. +- File Naming: Summaries should be named with the format `summary_YYYY-MM-DD_HH-MM-SS.md`. +- Use batched updates to update multiple artifacts in one go using tool call chaining. ```yaml artifacts: @@ -154,10 +160,6 @@ artifacts: path: docs/specs/steering/*.yml type: policy purpose: Stores policies and binding decisions. - - name: agent_work - path: docs/specs/agent_work/ - type: intermediate_outputs - purpose: Archives intermediate outputs, summaries. - name: specifications path: docs/specs/specifications.yml type: requirements_architecture_risk @@ -173,7 +175,7 @@ artifacts: format: [date, description, outcome, reflection, issues, next_steps, tool_calls] purpose: Logs rationale, actions, outcomes. - name: memory - path: memory + path: .github/instructions/memory.instruction.md type: memory purpose: Stores patterns, heuristics, reusable lessons. ```