From d22f9c1b3d0aff793d16e8be8ecc18771d824c20 Mon Sep 17 00:00:00 2001
From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com>
Date: Tue, 2 Dec 2025 16:45:29 +0000
Subject: [PATCH 1/2] Initial plan


From dac0aed6fbd7f99cc34c306efb07459de82fca0d Mon Sep 17 00:00:00 2001
From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com>
Date: Tue, 2 Dec 2025 16:52:27 +0000
Subject: [PATCH 2/2] docs: Fix incorrect README statements about task file
 matching

Tasks are matched by filename (not .md extension), not by task_name
in frontmatter. The task_name field is optional metadata.

Fixes:
- Line 107: "Find a task file with task_name: fix-bug" -> "Find a task file named fix-bug.md"
- Line 138: "The <task-name> is the value of the task_name field" -> "corresponds to the filename"
- Line 148: Removed incorrect reference to task_name in frontmatter
- Line 168: "matching task_name in frontmatter" -> "matches filename without .md extension"
- Lines 239-241: Removed claim that "filename doesn't matter" and "task_name is required"

Co-authored-by: alexec <1142830+alexec@users.noreply.github.com>
---
 README.md | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/README.md b/README.md
index 44fa86eb..96cf9db1 100644
--- a/README.md
+++ b/README.md
@@ -104,7 +104,7 @@ coding-context -p jira_issue_key=PROJ-1234 /fix-bug | llm -m gemini-pro
 ```
 
 This command will:
-1. Find a task file with `task_name: fix-bug` in its frontmatter.
+1. Find a task file named `fix-bug.md` in the task search paths.
 2. Find all rule files in the search paths.
 3. Filter the rules based on selectors.
 4. Execute any associated bootstrap scripts.
@@ -135,7 +135,7 @@ The `-d` flag supports various protocols via go-getter:
 
 ### Example Tasks
 
-The `<task-name>` is the value of the `task_name` field in the frontmatter of task files. Here are some common examples:
+The `<task-name>` corresponds to the filename (without the `.md` extension) of task files. Here are some common examples:
 
 - `triage-bug`
 - `review-pull-request`
@@ -145,7 +145,7 @@ The `<task-name>` is the value of the `task_name` field in the frontmatter of ta
 - `remove-feature-flag`
 - `speed-up-build`
 
-Each of these would have a corresponding `.md` file with `task_name` in the frontmatter (e.g., a file with `task_name: triage-bug`).
+Each of these would have a corresponding `.md` file (e.g., `triage-bug.md`, `fix-broken-build.md`).
 
 ## How It Works
 
@@ -165,7 +165,7 @@ The tool assembles the context in the following order:
 The tool looks for task and rule files in the following locations, in order of precedence:
 
 **Tasks:**
-- `./.agents/tasks/*.md` (any `.md` file with matching `task_name` in frontmatter)
+- `./.agents/tasks/*.md` (task name matches filename without `.md` extension)
 - `./.agents/commands/*.md`
 - `./.cursor/commands/*.md`
 - `./.opencode/command/*.md`
@@ -238,7 +238,7 @@ coding-context \
 
 ### Task Files
 
-Task files are Markdown files with a required `task_name` field in the frontmatter. The filename itself doesn't matter - only the `task_name` value is used for selection. Task files can contain variables for substitution and can use selectors in frontmatter to provide different prompts for the same task.
+Task files are Markdown files located in task search directories (e.g., `.agents/tasks/`). Tasks are matched by filename (without the `.md` extension), not by frontmatter fields. The `task_name` field in frontmatter is optional metadata. Task files can contain variables for substitution and can use selectors in frontmatter to filter between multiple task files with the same filename in different locations.
 
 **Example (`.agents/tasks/fix-bug.md`):**
 ```markdown