Files
leo-claude-mktplace/plugins/projman/commands/project-close.md
lmiranda 035cd00f4b fix(projman): align command names with git-flow pattern
All projman command names now start with 'projman' prefix to match
git-flow behavior and avoid forced plugin namespace in autocomplete.

Before: /projman:sprint-plan, /projman:project-status
After: /projman sprint plan, /projman project status

This matches git-flow which shows /gitflow commit, /gitflow status.

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
2026-02-08 22:57:42 -05:00

43 lines
1.0 KiB
Markdown

---
name: projman project close
description: Close a completed project — retrospective, archive, lessons learned
agent: orchestrator
---
# /project close
## Purpose
Run project-level retrospective, capture lessons learned, and archive project artifacts.
## Prerequisites
- All sprints in roadmap are closed
- Project status is `Executing`
## Skills Required
- skills/project-charter.md — to update status
- skills/wiki-conventions.md — page naming
- skills/visual-output.md — output formatting
## Workflow
### Step 1: Verify Completion
Check that all sprints in `Roadmap: {Name}` are marked complete.
Check that all epic-labeled issues are closed.
### Step 2: Project Retrospective
Create a retrospective section in the project charter:
- What went well
- What didn't go well
- Key learnings
- Metrics: total sprints, total issues, duration
### Step 3: Archive
Update `Project: {Name}` status → `Closed`
Update `Risk-Register: {Name}` status → `Archived`
### Step 4: Final Report
Display project summary with key metrics.