[Sprint V04.1.0] feat: Add wiki status updates to sprint-close workflow
- Add step 5: Update wiki implementation page status (Implemented/Partial/Failed) - Add step 6: Update wiki proposal page when all implementations complete - Add update_wiki_page to MCP tools in both sprint-close.md and orchestrator.md - Add critical reminders for wiki status updates Implements Phase 2 of V04.1.0 Wiki-Based Planning Enhancement. Closes #162 Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
@@ -383,7 +383,58 @@ create_lesson(
|
||||
)
|
||||
```
|
||||
|
||||
**E. Git Operations**
|
||||
**E. Update Wiki Implementation Page**
|
||||
|
||||
Fetch and update the implementation page status:
|
||||
```
|
||||
get_wiki_page(page_name="Change-V4.1.0:-Proposal-(Implementation-1)")
|
||||
```
|
||||
|
||||
Update with completion status:
|
||||
```
|
||||
update_wiki_page(
|
||||
page_name="Change-V4.1.0:-Proposal-(Implementation-1)",
|
||||
content="""
|
||||
> **Type:** Change Proposal Implementation
|
||||
> **Version:** V04.1.0
|
||||
> **Status:** Implemented ✅
|
||||
> **Date:** 2026-01-26
|
||||
> **Completed:** 2026-01-28
|
||||
> **Origin:** [Proposal](wiki-link)
|
||||
> **Sprint:** Sprint 17
|
||||
|
||||
# Implementation Details
|
||||
[Original content...]
|
||||
|
||||
## Completion Summary
|
||||
- All planned issues completed
|
||||
- Lessons learned: [Link to lesson]
|
||||
"""
|
||||
)
|
||||
```
|
||||
|
||||
**F. Update Wiki Proposal Page**
|
||||
|
||||
If all implementations complete, update proposal status:
|
||||
```
|
||||
update_wiki_page(
|
||||
page_name="Change-V4.1.0:-Proposal",
|
||||
content="""
|
||||
> **Type:** Change Proposal
|
||||
> **Version:** V04.1.0
|
||||
> **Status:** Implemented ✅
|
||||
> **Date:** 2026-01-26
|
||||
|
||||
# Feature Title
|
||||
[Original content...]
|
||||
|
||||
## Implementations
|
||||
- [Implementation 1](link) - ✅ Completed (Sprint 17)
|
||||
"""
|
||||
)
|
||||
```
|
||||
|
||||
**G. Git Operations**
|
||||
|
||||
Offer to handle git cleanup:
|
||||
```
|
||||
@@ -418,7 +469,9 @@ Would you like me to handle git operations?
|
||||
**Lessons Learned Tools (Gitea Wiki):**
|
||||
- `search_lessons(query, tags, limit)` - Find relevant past lessons
|
||||
- `create_lesson(title, content, tags, category)` - Save new lesson
|
||||
- `get_wiki_page(page_name)` - Fetch specific pages
|
||||
- `get_wiki_page(page_name)` - Fetch implementation/proposal pages
|
||||
- `update_wiki_page(page_name, content)` - Update implementation/proposal status
|
||||
- `list_wiki_pages()` - List all wiki pages
|
||||
|
||||
**Validation Tools:**
|
||||
- `get_branch_protection(branch)` - Check merge rules
|
||||
@@ -455,6 +508,8 @@ Would you like me to handle git operations?
|
||||
8. **Auto-check subtasks** - Mark issue subtasks complete on close
|
||||
9. **Track meticulously** - Update issues immediately, document blockers
|
||||
10. **Capture lessons** - At sprint close, interview thoroughly
|
||||
11. **Update wiki status** - At sprint close, update implementation and proposal pages
|
||||
12. **Link lessons to wiki** - Include lesson links in implementation completion summary
|
||||
|
||||
## Your Mission
|
||||
|
||||
|
||||
Reference in New Issue
Block a user