Completes feature/epic workflows after deployment with comprehensive walkthrough generation for epics (v5.0+), roadmap updates, artifact archival, documentation, and branch cleanup. Use after /ship-prod, /deploy-prod, or /build-local completes, or when user asks to finalize. (project)
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.
Instruções da origem · Visualização somente leitura
name
finalize-phase
description
Completes feature/epic workflows after deployment with comprehensive walkthrough generation for epics (v5.0+), roadmap updates, artifact archival, documentation, and branch cleanup. Use after /ship-prod, /deploy-prod, or /build-local completes, or when user asks to finalize. (project)
Complete feature/epic workflow, generate walkthrough (epics only), update roadmap, archive artifacts, and preserve knowledge after deployment. Ensures clean workflow closure with self-improving workflow system.
This skill orchestrates the /finalize phase, the final step after successful deployment to production, direct-prod, or local build.
For Epic Workflows (v5.0+):
Generate comprehensive walkthrough.md with velocity metrics, sprint results, lessons learned
Run post-mortem audit with pattern detection (after 2-3 epics)
Offer workflow healing with improvement recommendations
Detect patterns for custom skills/commands generation
For Feature Workflows:
Standard finalization (roadmap, artifacts, docs, branches)
# List all artifacts in feature directoryls -la specs/NNN-slug/
# Should see all required files# No temporary files (.tmp, .bak, etc.)
If artifacts missing:
Check for artifacts in wrong locations (root directory, temp folders)
Regenerate missing artifacts if possible
Document missing artifacts in finalization commit message
See reference.md for complete artifact checklist.
Update user-facing documentation for shipped feature.
README.md updates (if user-facing feature):
## Features-**Student Progress Dashboard** - Track student completion rates and time spent
- View individual student progress
- Filter by class, subject, or time period
- Export progress reports to CSV
CHANGELOG.md updates:
## [1.3.0] - 2025-10-21### Added- Student progress dashboard with completion tracking
- CSV export for progress reports
- Filtering by class, subject, and time period
### Changed- Improved dashboard load time from 3s to 1.2s
### Fixed- Fixed timeout issue with large datasets (pagination added)
Ship feature, skip README update
3 months later: User asks "Do we have progress tracking?"
Answer: "Yes, we shipped that 3 months ago" (not documented)
Example (good):
Ship feature, update README immediately
README: "Student Progress Dashboard - Track completion"
User discovers feature organically from README
Why: Branch clutter makes it hard to find active work.
Impact:
Git branch list becomes unusable (100+ stale branches)
Hard to identify active development
Wastes storage (remote branches)
Example (bad):
git branch -a
# Shows 87 feature branches (only 3 active)
# Which branches are safe to delete? Unknown.
Example (good):
git branch -a
# Shows 3 feature branches (all active)
# Clear signal: current work only
Why: Finalization changes should be tracked in git history.
Impact:
Changes not backed up
No clear signal when workflow closed
Hard to audit finalization process
Example (bad):
Update roadmap, README, CHANGELOG
Git status: 3 modified files
Never commit (lose changes on machine wipe)
Issue: Missing artifacts (spec.md, plan.md, etc.)
Solution: Check root directory, temp folders, or regenerate if possible. Document missing in commit.
Issue: Feature branch won't delete (not merged)
Solution: Verify feature deployed successfully, then force delete with git branch -D. Document in commit.
Issue: Unclear what version to use
Solution: Check CHANGELOG for next version number, or use deployment date as version (v2025.10.21)
Issue: Don't know what to put in CHANGELOG
Solution: Review ship-summary.md and release-notes.md for user-facing changes. Focus on Added/Changed/Fixed.
<reference_guides>
Finalization procedures:
Roadmap Update Checklist (reference.md#roadmap-updates) - Required information and format
Artifact Archival Guide (reference.md#artifact-archival) - Complete checklist and validation
Documentation Standards (reference.md#documentation-updates) - README, CHANGELOG, user guide formats
Examples:
Complete Finalization (examples.md#complete-finalization) - All steps done correctly
Rushed Cleanup (examples.md#rushed-cleanup) - What happens when steps skipped
Workflow closure:
After finalization completes, feature workflow is closed. Retrospective analysis can begin to learn from past work.
</reference_guides>
