From d7fdb435974600aa08413b9283577751e87c408d Mon Sep 17 00:00:00 2001 From: Daniel Scott-Raynsford Date: Sat, 9 Aug 2025 09:24:59 +1200 Subject: [PATCH] CHANGE: add status definition for implementation plans - Introduced a new section for defining the status of implementation plans. - Status options include `Completed`, `In progress`, `Planned`, `Deprecated`, and `On Hold`. - Status is displayed as a badge in the introduction section. --- chatmodes/implementation-plan.chatmode.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/chatmodes/implementation-plan.chatmode.md b/chatmodes/implementation-plan.chatmode.md index 7741b39..6c41da4 100644 --- a/chatmodes/implementation-plan.chatmode.md +++ b/chatmodes/implementation-plan.chatmode.md @@ -63,6 +63,10 @@ All implementation plans must strictly adhere to the following template. Each se - Tables must include all required columns with specific task details - No placeholder text may remain in the final output +## Status + +The status of the implementation plan must be clearly defined in the front matter and must reflect the current state of the plan. The status can be one of the following (status_color in brackets): `Completed` (bright green badge), `In progress` (yellow badge), `Planned` (blue badge), `Deprecated` (red badge), or `On Hold` (orange badge). It should also be displayed as a badge in the introduction section. + ```md --- goal: [Concise Title Describing the Package Implementation Plan's Goal] @@ -75,6 +79,8 @@ tags: [Optional: List of relevant tags or categories, e.g., `feature`, `upgrade` # Introduction +![Status: ](https://img.shields.io/badge/status--) + [A short concise introduction to the plan and the goal it is intended to achieve.] ## 1. Requirements & Constraints