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

[Sprint 5] docs: Document Sprint 4 lessons learned and plugin behavior clarifications #266

New Issue
Closed
opened 2026-01-28 19:11:29 +00:00 by lmiranda · 0 comments
lmiranda commented 2026-01-28 19:11:29 +00:00
Owner
Copy Link

Summary

Capture lessons learned from Sprint 4 execution and document plugin behavior clarifications discovered during sprint planning and execution.

Items to Document

1. MCP Branch Detection Pattern

  • Document that MCP servers run from their installation directory, not the user's project directory
  • Explain the CLAUDE_PROJECT_DIR capture pattern in run.sh scripts
  • Add to troubleshooting docs

2. GITEA_REPO Format

  • ✅ Already fixed in PR #264
  • Ensure all examples show owner/repo format consistently

3. Gitea Auto-Close Behavior

  • Document that Gitea only auto-closes issues when merging to the default branch (main)
  • Merging to development with Closes #XX keywords does NOT auto-close
  • Add workaround: manually close issues or set development as default during sprints

4. Session Restart Requirements

  • Document that MCP server changes require Claude Code session restart
  • Add to docs/DEBUGGING-CHECKLIST.md troubleshooting section

5. Plugin Issues from CLAUDE.md (Pending Issues section)

  • doc-guardian hook incorrectly stops workflow (should not block)
  • doc-guardian hook should spawn agent instead of blocking
  • Hook fired multiple times for related edits in same task
  • Hook blocked edit with overly restrictive URL warning

Acceptance Criteria

  • Add "Gitea Auto-Close Behavior" section to sprint workflow docs
  • Add "MCP Session Restart" note to debugging checklist
  • Create Gitea issue for doc-guardian hook improvements
  • Capture lessons in wiki under lessons-learned/sprints/sprint-4

Context

These items were identified during Sprint 4 but not addressed to avoid scope creep. Scheduled for post-Sprint 5.

## Summary Capture lessons learned from Sprint 4 execution and document plugin behavior clarifications discovered during sprint planning and execution. ## Items to Document ### 1. MCP Branch Detection Pattern - Document that MCP servers run from their installation directory, not the user's project directory - Explain the `CLAUDE_PROJECT_DIR` capture pattern in `run.sh` scripts - Add to troubleshooting docs ### 2. GITEA_REPO Format - ✅ Already fixed in PR #264 - Ensure all examples show `owner/repo` format consistently ### 3. Gitea Auto-Close Behavior - Document that Gitea only auto-closes issues when merging to the **default branch** (main) - Merging to `development` with `Closes #XX` keywords does NOT auto-close - Add workaround: manually close issues or set development as default during sprints ### 4. Session Restart Requirements - Document that MCP server changes require Claude Code session restart - Add to `docs/DEBUGGING-CHECKLIST.md` troubleshooting section ### 5. Plugin Issues from CLAUDE.md (Pending Issues section) - doc-guardian hook incorrectly stops workflow (should not block) - doc-guardian hook should spawn agent instead of blocking - Hook fired multiple times for related edits in same task - Hook blocked edit with overly restrictive URL warning ## Acceptance Criteria - [ ] Add "Gitea Auto-Close Behavior" section to sprint workflow docs - [ ] Add "MCP Session Restart" note to debugging checklist - [ ] Create Gitea issue for doc-guardian hook improvements - [ ] Capture lessons in wiki under `lessons-learned/sprints/sprint-4` ## Context These items were identified during Sprint 4 but not addressed to avoid scope creep. Scheduled for post-Sprint 5.
lmiranda added the Type/DocumentationComplexity/SimplePriority/MediumEffort/M labels 2026-01-28 19:11:29 +00:00
lmiranda changed title from [Backlog] docs: Document Sprint 4 lessons learned and plugin behavior clarifications to [Sprint 5] docs: Document Sprint 4 lessons learned and plugin behavior clarifications 2026-01-28 19:16:37 +00:00
lmiranda added this to the Sprint 5 - Documentation milestone 2026-01-28 19:19:31 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
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 Complexity/Simple Effort/M Priority/Medium Type/Documentation
Milestone
No items
No Milestone Sprint 5 - Documentation
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#266
Delete Branch "%!s()"

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?