Template

Files

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

3.8 KiB

Raw Blame History

name, description, agent

name	description	agent
sprint close	Complete sprint and capture lessons learned to Gitea Wiki	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:

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).
Review Sprint Completion - Verify issues closed or moved to backlog
Capture Lessons Learned - Interview user about challenges and insights
Tag for Discoverability - Apply technology, component, and pattern tags
Save to Gitea Wiki - Use create_lesson with metadata and implementation link
Update Wiki Implementation Page - Change status to Implemented/Partial/Failed
Update Wiki Proposal Page - Update overall status if all implementations complete
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:**.
New Command Verification - Remind user new commands require session restart
Update CHANGELOG (MANDATORY) - Add changes to [Unreleased] section
Version Review - Review CHANGELOG.md for version bump recommendation (manual)
Git Operations - Commit, merge, tag, clean up branches
Close Milestone - Update milestone state to closed

RFC Status Update (Step 7)

If the sprint was linked to an RFC:

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)

Update RFC Page (if Implemented):

Change status: Implementing → Implemented
Add Completion section with date and release version
Link to lessons learned page

update_wiki_page(
    page_name="RFC-NNNN:-Title",
    content="[content with Implemented status and completion details]",
    repo="org/repo"
)

Update RFC-Index:
- Remove from "## Implementing" section
- Add to "## Implemented" section with completion date and release
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.

3.8 KiB Raw Blame History