personal-projects/leo-claude-mktplace
Template
0
1
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

[V04.1.0] feat: Wiki-Based Planning Workflow Enhancement #165

Merged
lmiranda merged 4 commits from feat/v04.1.0-wiki-planning-workflow into development 2026-01-26 15:28:00 +00:00
Conversation 0 Commits 4 Files Changed 6 +473 -69
lmiranda commented 2026-01-26 15:27:14 +00:00
Owner
Copy Link

Summary

  • Add wiki proposal/implementation page creation to /sprint-plan
  • Add wiki status updates to /sprint-close
  • Add cross-linking between issues, wiki, and lessons learned
  • Add new /proposal-status command for viewing proposal tree

Related Issues

Closes #161, #162, #163, #164

Changes

Phase 1: Wiki workflow in sprint-plan

  • Flexible input source detection (file, wiki, conversation)
  • Wiki proposal and implementation page creation
  • Wiki reference in created issues

Phase 2: Wiki status updates in sprint-close

  • Update implementation page status on sprint close
  • Update proposal page when all implementations complete

Phase 3: Cross-linking

  • Metadata section in lessons with implementation link
  • Bidirectional traceability

Phase 4: Proposal status command

  • /proposal-status command for tree view of proposals

Testing

  • Manual verification of command documentation
  • Wiki pages created and updated successfully

🤖 Generated with Claude Code

## Summary - Add wiki proposal/implementation page creation to `/sprint-plan` - Add wiki status updates to `/sprint-close` - Add cross-linking between issues, wiki, and lessons learned - Add new `/proposal-status` command for viewing proposal tree ## Related Issues Closes #161, #162, #163, #164 ## Changes ### Phase 1: Wiki workflow in sprint-plan - Flexible input source detection (file, wiki, conversation) - Wiki proposal and implementation page creation - Wiki reference in created issues ### Phase 2: Wiki status updates in sprint-close - Update implementation page status on sprint close - Update proposal page when all implementations complete ### Phase 3: Cross-linking - Metadata section in lessons with implementation link - Bidirectional traceability ### Phase 4: Proposal status command - `/proposal-status` command for tree view of proposals ## Testing - Manual verification of command documentation - Wiki pages created and updated successfully --- 🤖 Generated with [Claude Code](https://claude.ai/code)
lmiranda added 4 commits 2026-01-26 15:27:15 +00:00
feat(projman): add wiki-based planning workflow to sprint-plan 842ce3f6bc 
Phase 1 implementation for Change V04.1.0:
- Add flexible input source detection (file, wiki, conversation)
- Add wiki proposal and implementation page creation
- Add wiki reference to created issues
- Add cleanup step to delete local files after migration
- Update planner agent with wiki workflow responsibilities

Closes #161

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
[Sprint V04.1.0] feat: Add wiki status updates to sprint-close workflow 30b379b68c 
- 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>
[Sprint V04.1.0] feat: Add cross-linking between issues, wiki, and lessons 1a0f3aa779 
- Add Metadata section to lesson structure with Implementation link
- Update lesson examples to include metadata with wiki reference
- Enable bidirectional traceability: lessons ↔ implementation pages

Phase 3 of V04.1.0 Wiki-Based Planning Enhancement.
Closes #163

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
[Sprint V04.1.0] feat: Add /proposal-status command for proposal tree view 34de0e4e82 
- 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>
lmiranda merged commit 896cdcfa0f into development 2026-01-26 15:28:00 +00:00
lmiranda deleted branch feat/v04.1.0-wiki-planning-workflow 2026-01-26 15:28:00 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
Component/API
API endpoints, contracts, and integration
 Component/Auth
Authentication and authorization
 Component/Backend
Backend service code and business logic
 Component/Database
Database schemas, migrations, queries
 Component/Deploy
Deployment, infrastructure, DevOps
 Component/Docs
Documentation and guides
 Component/Frontend
User interface and client-side code
 Component/Infra
Infrastructure and system configuration
 Component/Testing
Test infrastructure and frameworks
 Tech/Docker
Docker containers and compose
 Tech/FastAPI
FastAPI backend framework
 Tech/JavaScript
JavaScript/Node.js code
 Tech/PostgreSQL
PostgreSQL database
 Tech/Python
Python language and libraries
 Tech/Redis
Redis cache and pub/sub
 Tech/Vue
Vue.js frontend framework
Complexity/Complex
High uncertainty or many dependencies
 Complexity/Medium
Some unknowns or dependencies
 Complexity/Simple
Straightforward, well-understood
 Effort/L
3-5 days
 Effort/M
1-2 days
 Effort/S
2-4 hours
 Effort/XL
> 1 week
 Effort/XS
< 2 hours
 Priority/Critical
Immediate attention required
 Priority/High
Important, needs attention soon
 Priority/Low
Nice to have, can wait
 Priority/Medium
Normal priority
 Type/Bug
Something isn't working
 Type/Chore
Maintenance tasks
 Type/Documentation
Documentation improvements
 Type/Feature
New feature or request
 Type/Refactor
Code refactoring without changing behavior
 Type/Test
Testing related
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
lmiranda
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: personal-projects/leo-claude-mktplace#165
Delete Branch "feat/v04.1.0-wiki-planning-workflow"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?