From 34de0e4e826576677062b95902cb7d39fea145cf Mon Sep 17 00:00:00 2001 From: lmiranda Date: Mon, 26 Jan 2026 10:23:53 -0500 Subject: [PATCH] [Sprint V04.1.0] feat: Add /proposal-status command for proposal tree view - Create new proposal-status.md command - Shows all proposals with status (Pending, In Progress, Implemented, Abandoned) - Tree view of implementations under each proposal - Links to issues and lessons learned - Update README with new command documentation Phase 4 of V04.1.0 Wiki-Based Planning Enhancement. Closes #164 Co-Authored-By: Claude Opus 4.5 --- plugins/projman/README.md | 12 ++ plugins/projman/commands/proposal-status.md | 121 ++++++++++++++++++++ 2 files changed, 133 insertions(+) create mode 100644 plugins/projman/commands/proposal-status.md diff --git a/plugins/projman/README.md b/plugins/projman/README.md index 264c493..f8e3db1 100644 --- a/plugins/projman/README.md +++ b/plugins/projman/README.md @@ -114,6 +114,17 @@ Check current sprint progress. **When to use:** Daily standup, progress check, deciding what to work on next +### `/proposal-status` +View proposal and implementation hierarchy. + +**What it does:** +- Lists all change proposals from Gitea Wiki +- Shows implementations under each proposal with status +- Displays linked issues and lessons learned +- Tree-style formatted output + +**When to use:** Review progress on multi-sprint features, track proposal lifecycle + ### `/sprint-close` Complete sprint and capture lessons learned. @@ -468,6 +479,7 @@ projman/ │ ├── sprint-start.md │ ├── sprint-status.md │ ├── sprint-close.md +│ ├── proposal-status.md │ ├── labels-sync.md │ ├── initial-setup.md │ ├── project-init.md diff --git a/plugins/projman/commands/proposal-status.md b/plugins/projman/commands/proposal-status.md new file mode 100644 index 0000000..3c1b5b4 --- /dev/null +++ b/plugins/projman/commands/proposal-status.md @@ -0,0 +1,121 @@ +--- +description: View proposal and implementation hierarchy with status tracking +--- + +# Proposal Status + +View the status of all change proposals and their implementations in the Gitea Wiki. + +## Overview + +This command provides a tree view of: +- All change proposals (`Change VXX.X.X: Proposal`) +- Their implementations (`Change VXX.X.X: Proposal (Implementation N)`) +- Linked issues and lessons learned + +## Workflow + +1. **Fetch All Wiki Pages** + - Use `list_wiki_pages()` to get all wiki pages + - Filter for pages matching `Change V*: Proposal*` pattern + +2. **Parse Proposal Structure** + - Group implementations under their parent proposals + - Extract status from page metadata (In Progress, Implemented, Abandoned) + +3. **Fetch Linked Artifacts** + - For each implementation, search for issues referencing it + - Search lessons learned that link to the implementation + +4. **Display Tree View** + ``` + Change V04.1.0: Proposal [In Progress] + ├── Implementation 1 [In Progress] - 2026-01-26 + │ ├── Issues: #161, #162, #163, #164 + │ └── Lessons: (pending) + └── Implementation 2 [Not Started] + + Change V04.0.0: Proposal [Implemented] + └── Implementation 1 [Implemented] - 2026-01-20 + ├── Issues: #150, #151 + └── Lessons: v4.0.0-impl-1-lessons + ``` + +## MCP Tools Used + +- `list_wiki_pages()` - List all wiki pages +- `get_wiki_page(page_name)` - Get page content for status extraction +- `list_issues(state, labels)` - Find linked issues +- `search_lessons(query, tags)` - Find linked lessons + +## Status Definitions + +| Status | Meaning | +|--------|---------| +| **Pending** | Proposal created but no implementation started | +| **In Progress** | At least one implementation is active | +| **Implemented** | All planned implementations complete | +| **Abandoned** | Proposal was cancelled or superseded | + +## Filtering Options + +The command accepts optional filters: + +``` +/proposal-status # Show all proposals +/proposal-status --version V04.1.0 # Show specific version +/proposal-status --status "In Progress" # Filter by status +``` + +## Example Output + +``` +Proposal Status Report +====================== + +Change V04.1.0: Wiki-Based Planning Workflow [In Progress] +├── Implementation 1 [In Progress] - Started: 2026-01-26 +│ ├── Issues: #161 (closed), #162 (closed), #163 (closed), #164 (open) +│ └── Lessons: (pending - sprint not closed) +│ +└── (No additional implementations planned) + +Change V04.0.0: MCP Server Consolidation [Implemented] +├── Implementation 1 [Implemented] - 2026-01-15 to 2026-01-20 +│ ├── Issues: #150 (closed), #151 (closed), #152 (closed) +│ └── Lessons: +│ • Sprint 15 - MCP Server Symlink Best Practices +│ • Sprint 15 - Venv Path Resolution in Plugins +│ +└── (Complete) + +Change V03.2.0: Label Taxonomy Sync [Implemented] +└── Implementation 1 [Implemented] - 2026-01-10 to 2026-01-12 + ├── Issues: #140 (closed), #141 (closed) + └── Lessons: + • Sprint 14 - Organization vs Repository Labels + +Summary: +- Total Proposals: 3 +- In Progress: 1 +- Implemented: 2 +- Pending: 0 +``` + +## Implementation Notes + +**Page Name Parsing:** +- Proposals: `Change VXX.X.X: Proposal` or `Change Sprint-NN: Proposal` +- Implementations: `Change VXX.X.X: Proposal (Implementation N)` + +**Status Extraction:** +- Parse the `> **Status:**` line from page metadata +- Default to "Unknown" if not found + +**Issue Linking:** +- Search for issues containing wiki link in body +- Or search for issues with `[Sprint XX]` prefix matching implementation + +**Lesson Linking:** +- Search lessons with implementation link in metadata +- Or search by version/sprint tags