-
Notifications
You must be signed in to change notification settings - Fork 35
Description
Issue Description
If you run a generated prompt after adding that you want it to describe its instructions, it looks for the #file:../../.github/instructions/task-implementation.instructions.md file and does not find it:
Now I have all the context. Let me read the task-implementation instructions and then proceed with the implementation.
The instructions file doesn't exist locally. Let me proceed with the implementation based on the plan and details I have.
Additional Context
Here is a repro
Locally, on my Windows laptop, in WSL Ubuntu
mkdir repro20260127a
cd repro20260127a
code .HVE extension is installed in its version 1.0.7
CTRL-ALT-I, task-researcher, Claude Opus 4.5
Write the simplest hello world example in pythonThis is so simple that it suggests to write the file directly
No please follow the process and write a research documentIt generates the file .copilot-tracking/research/20260127-python-hello-world-research.md
In VSCode: keep
- Clear context (/clear) or start a new chat
- Switch to task-planner mode
- Attach the research document to task-planner
- Proceed with planning and implementation
proceed with planningI now have
ls -lR .copilot-tracking/
.copilot-tracking/:
total 16
drwxr-xr-x 2 benjguin benjguin 4096 Jan 27 08:55 details
drwxr-xr-x 2 benjguin benjguin 4096 Jan 27 08:55 plans
drwxr-xr-x 2 benjguin benjguin 4096 Jan 27 08:55 prompts
drwxr-xr-x 2 benjguin benjguin 4096 Jan 27 08:52 research
.copilot-tracking/details:
total 4
-rw-r--r-- 1 benjguin benjguin 1963 Jan 27 08:55 20260127-python-hello-world-details.md
.copilot-tracking/plans:
total 4
-rw-r--r-- 1 benjguin benjguin 1645 Jan 27 08:55 20260127-python-hello-world-plan.instructions.md
.copilot-tracking/prompts:
total 4
-rw-r--r-- 1 benjguin benjguin 1825 Jan 27 08:55 implement-python-hello-world.prompt.md
.copilot-tracking/research:
total 8
-rw-r--r-- 1 benjguin benjguin 4193 Jan 27 08:53 20260127-python-hello-world-research.md
In VSCode keep all files
The prompt file content is:
<!-- markdownlint-disable-file -->
# Implementation Prompt: Python Hello World Example
## Implementation Instructions
### Step 1: Create Changes Tracking File
You WILL create `20260127-python-hello-world-changes.md` in `.copilot-tracking/changes/` if it does not exist.
### Step 2: Execute Implementation
You WILL follow #file:../../.github/instructions/task-implementation.instructions.md
You WILL systematically implement #file:../plans/20260127-python-hello-world-plan.instructions.md task-by-task
You WILL follow ALL project standards and conventions
**CRITICAL**: If ${input:phaseStop:true} is true, you WILL stop after each Phase for user review.
**CRITICAL**: If ${input:taskStop:false} is true, you WILL stop after each Task for user review.
### Step 3: Cleanup
When ALL Phases are checked off (`[x]`) and completed you WILL do the following:
1. You WILL provide a markdown style link and a summary of all changes from #file:../changes/20260127-python-hello-world-changes.md to the user:
* You WILL keep the overall summary brief
* You WILL add spacing around any lists
* You MUST wrap any reference to a file in a markdown style link
2. You WILL provide markdown style links to .copilot-tracking/plans/20260127-python-hello-world-plan.instructions.md, .copilot-tracking/details/20260127-python-hello-world-details.md, and .copilot-tracking/research/20260127-python-hello-world-research.md documents. You WILL recommend cleaning these files up as well.
3. **MANDATORY**: You WILL attempt to delete .copilot-tracking/prompts/implement-python-hello-world.prompt.md
## Success Criteria
* [ ] Changes tracking file created
* [ ] All plan items implemented with working code
* [ ] All detailed specifications satisfied
* [ ] Project conventions followed
* [ ] Changes file updated continuouslyBut there is no #file:../../.github/instructions/task-implementation.instructions.md locally as HVE is used as an extension.
Let’s check it by changing the prompt file and execute it
<!-- markdownlint-disable-file -->
# Implementation Prompt: Python Hello World Example
## Implementation Instructions
### Step 1: Create Changes Tracking File
You WILL create `20260127-python-hello-world-changes.md` in `.copilot-tracking/changes/` if it does not exist.
### Step 2: Execute Implementation
You WILL follow #file:../../.github/instructions/task-implementation.instructions.md
You WILL systematically implement #file:../plans/20260127-python-hello-world-plan.instructions.md task-by-task
You WILL follow ALL project standards and conventions
**CRITICAL**: If ${input:phaseStop:true} is true, you WILL stop after each Phase for user review.
**CRITICAL**: If ${input:taskStop:false} is true, you WILL stop after each Task for user review.
You WILL also share a summary of your instructions for the task implementation
### Step 3: Cleanup
When ALL Phases are checked off (`[x]`) and completed you WILL do the following:
1. You WILL provide a markdown style link and a summary of all changes from #file:../changes/20260127-python-hello-world-changes.md to the user:
* You WILL keep the overall summary brief
* You WILL add spacing around any lists
* You MUST wrap any reference to a file in a markdown style link
2. You WILL provide markdown style links to .copilot-tracking/plans/20260127-python-hello-world-plan.instructions.md, .copilot-tracking/details/20260127-python-hello-world-details.md, and .copilot-tracking/research/20260127-python-hello-world-research.md documents. You WILL recommend cleaning these files up as well.
3. **MANDATORY**: You WILL attempt to delete .copilot-tracking/prompts/implement-python-hello-world.prompt.md
## Success Criteria
* [ ] task implementation instructions shared or explanation why it’s not possible given
* [ ] Changes tracking file created
* [ ] All plan items implemented with working code
* [ ] All detailed specifications satisfied
* [ ] Project conventions followed
* [ ] Changes file updated continuouslyOpen only the modified prompt file and execute it (play icon in VSCode)
At some point, Copilot reads:
Now I have all the context. Let me read the task-implementation instructions and then proceed with the implementation.
The instructions file doesn't exist locally. Let me proceed with the implementation based on the plan and details I have.
The implementation still succeeds, but all instructions may not have been followed.