[2.33.1] Add status frontmatter to plan templates

- Plan templates now include `status: active` in YAML frontmatter
- /workflows:work updates plan status to `completed` after shipping
- Agents can grep frontmatter to distinguish current vs historical plans

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
Kieran Klaassen
2026-02-13 09:54:42 -08:00
parent b42163f1c0
commit 134a994c08
4 changed files with 21 additions and 2 deletions

View File

@@ -1,6 +1,6 @@
{ {
"name": "compound-engineering", "name": "compound-engineering",
"version": "2.33.0", "version": "2.33.1",
"description": "AI-powered development tools. 29 agents, 22 commands, 19 skills, 1 MCP server for code review, research, design, and workflow automation.", "description": "AI-powered development tools. 29 agents, 22 commands, 19 skills, 1 MCP server for code review, research, design, and workflow automation.",
"author": { "author": {
"name": "Kieran Klaassen", "name": "Kieran Klaassen",

View File

@@ -5,6 +5,15 @@ All notable changes to the compound-engineering plugin will be documented in thi
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/), The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html). and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
## [2.33.1] - 2026-02-13
### Changed
- **`/workflows:plan` command** - All plan templates now include `status: active` in YAML frontmatter. Plans are created with `status: active` and marked `status: completed` when work finishes.
- **`/workflows:work` command** - Phase 4 now updates plan frontmatter from `status: active` to `status: completed` after shipping. Agents can grep for status to distinguish current vs historical plans.
---
## [2.33.0] - 2026-02-12 ## [2.33.0] - 2026-02-12
### Added ### Added

View File

@@ -178,6 +178,7 @@ Select how comprehensive you want the issue to be, simpler is mostly better.
--- ---
title: [Issue Title] title: [Issue Title]
type: [feat|fix|refactor] type: [feat|fix|refactor]
status: active
date: YYYY-MM-DD date: YYYY-MM-DD
--- ---
@@ -230,6 +231,7 @@ end
--- ---
title: [Issue Title] title: [Issue Title]
type: [feat|fix|refactor] type: [feat|fix|refactor]
status: active
date: YYYY-MM-DD date: YYYY-MM-DD
--- ---
@@ -294,6 +296,7 @@ date: YYYY-MM-DD
--- ---
title: [Issue Title] title: [Issue Title]
type: [feat|fix|refactor] type: [feat|fix|refactor]
status: active
date: YYYY-MM-DD date: YYYY-MM-DD
--- ---

View File

@@ -297,7 +297,14 @@ This command takes a work document (plan, specification, or todo file) and execu
)" )"
``` ```
4. **Notify User** 4. **Update Plan Status**
If the input document has YAML frontmatter with a `status` field, update it to `completed`:
```
status: active → status: completed
```
5. **Notify User**
- Summarize what was completed - Summarize what was completed
- Link to PR - Link to PR
- Note any follow-up work needed - Note any follow-up work needed