[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 <noreply@anthropic.com>
This commit is contained in:
2026-01-26 10:23:53 -05:00
parent 1a0f3aa779
commit 34de0e4e82
2 changed files with 133 additions and 0 deletions

View File

@@ -114,6 +114,17 @@ Check current sprint progress.
**When to use:** Daily standup, progress check, deciding what to work on next **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` ### `/sprint-close`
Complete sprint and capture lessons learned. Complete sprint and capture lessons learned.
@@ -468,6 +479,7 @@ projman/
│ ├── sprint-start.md │ ├── sprint-start.md
│ ├── sprint-status.md │ ├── sprint-status.md
│ ├── sprint-close.md │ ├── sprint-close.md
│ ├── proposal-status.md
│ ├── labels-sync.md │ ├── labels-sync.md
│ ├── initial-setup.md │ ├── initial-setup.md
│ ├── project-init.md │ ├── project-init.md

View File

@@ -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