Files
leo-claude-mktplace/plugins/projman/commands/sprint-close.md
lmiranda 2d51df7a42 feat(marketplace): command consolidation + 8 new plugins (v8.1.0 → v9.0.0) [BREAKING]
Phase 1b: Rename all ~94 commands across 12 plugins to /<noun> <action>
sub-command pattern. Git-flow consolidated from 8→5 commands (commit
variants absorbed into --push/--merge/--sync flags). Dispatch files,
name: frontmatter, and cross-reference updates for all plugins.

Phase 2: Design documents for 8 new plugins in docs/designs/.

Phase 3: Scaffold 8 new plugins — saas-api-platform, saas-db-migrate,
saas-react-platform, saas-test-pilot, data-seed, ops-release-manager,
ops-deploy-pipeline, debug-mcp. Each with plugin.json, commands, agents,
skills, README, and claude-md-integration. Marketplace grows from 12→20.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-02-06 14:52:11 -05:00

90 lines
3.8 KiB
Markdown

---
name: sprint close
description: Complete sprint and capture lessons learned to Gitea Wiki
agent: orchestrator
---
# Close Sprint and Capture Lessons Learned
## Skills Required
- skills/mcp-tools-reference.md
- skills/lessons-learned.md
- skills/wiki-conventions.md
- skills/rfc-workflow.md *(conditional — load only when sprint milestone metadata contains `**RFC:**` reference)*
- skills/progress-tracking.md
- skills/git-workflow.md
- skills/sprint-lifecycle.md
## Purpose
Complete the sprint, capture lessons learned to Gitea Wiki, and update documentation. This is critical for preventing repeated mistakes across sprints.
## Invocation
Run `/sprint close` when sprint work is complete.
## Workflow
Execute the sprint close workflow:
0. **Check Lifecycle State** - Execute `skills/sprint-lifecycle.md` check protocol. Expect `Sprint/Reviewing`. Clear all Sprint/* labels (return to idle) at the END of close workflow, after all other steps. Warn if in wrong state (allow with `--force`).
1. **Review Sprint Completion** - Verify issues closed or moved to backlog
2. **Capture Lessons Learned** - Interview user about challenges and insights
3. **Tag for Discoverability** - Apply technology, component, and pattern tags
4. **Save to Gitea Wiki** - Use `create_lesson` with metadata and implementation link
5. **Update Wiki Implementation Page** - Change status to Implemented/Partial/Failed
6. **Update Wiki Proposal Page** - Update overall status if all implementations complete
7. **Update RFC Status (if applicable)** - Skip if sprint is not RFC-linked. Only load `rfc-workflow.md` and execute this step if the milestone description contains `**RFC:**`.
8. **New Command Verification** - Remind user new commands require session restart
9. **Update CHANGELOG** (MANDATORY) - Add changes to `[Unreleased]` section
10. **Version Review** - Review CHANGELOG.md for version bump recommendation (manual)
11. **Git Operations** - Commit, merge, tag, clean up branches
12. **Close Milestone** - Update milestone state to closed
## RFC Status Update (Step 7)
If the sprint was linked to an RFC:
1. **Check Sprint Completion Status:**
- All issues completed → RFC status = Implemented
- Partial completion → RFC status stays Implementing (note progress)
- Blocked/Failed → RFC status reverts to Draft (with notes)
2. **Update RFC Page (if Implemented):**
- Change status: Implementing → Implemented
- Add Completion section with date and release version
- Link to lessons learned page
```python
update_wiki_page(
page_name="RFC-NNNN:-Title",
content="[content with Implemented status and completion details]",
repo="org/repo"
)
```
3. **Update RFC-Index:**
- Remove from "## Implementing" section
- Add to "## Implemented" section with completion date and release
4. **Handle Partial Completion:**
- Keep RFC in Implementing status
- Add progress notes to Implementation section
- Next sprint can continue the work
**Don't skip lessons learned!** Future sprints will benefit from captured insights.
## Visual Output
```
╔══════════════════════════════════════════════════════════════════╗
║ 📋 PROJMAN ║
║ 🏁 CLOSING ║
║ [Sprint Name] ║
╚══════════════════════════════════════════════════════════════════╝
```
## Token Usage Note
Token usage is captured as a `## Token Usage` section in the lessons learned wiki page — no standalone report.