finalize-phase

Generate finalization packages and update roadmap, artifacts, and documentation after deployment.

Updated Jan 5, 2026
One-click install
npx skills add https://github.com/Sjdjdiejdrirhdkjej/Claude-code-conductor --skill finalize-phase-sjdjdiejdrirhdkjej
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: finalize-phase
Source: https://github.com/Sjdjdiejdrirhdkjej/Claude-code-conductor/tree/main/.claude/skills/finalize-phase
Command: npx skills add https://github.com/Sjdjdiejdrirhdkjej/Claude-code-conductor --skill finalize-phase-sjdjdiejdrirhdkjej

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill closes feature and epic workstreams after deployment by generating comprehensive finalization artifacts, updating the roadmap, archiving artifacts, refreshing documentation, and cleaning up branches to preserve knowledge for future work.

Core Features & Use Cases

  • Epic walkthrough generation: Creates a machine-readable walkthrough for epics (v5.0+), including velocity metrics, sprint results, and lessons learned.
  • Roadmap updates: Moves shipped features to the "Shipped" section with deployment date, version, and links.
  • Artifact archival: Validates and archives all required phase artifacts in specs/NNN-slug/, maintaining a complete audit trail.
  • Documentation updates: Refreshes README and CHANGELOG (and user guides if applicable) to reflect new functionality.
  • Branch hygiene: Cleans up feature branches locally and remotely after successful deployment.
  • Finalization commit: Records the closure as a dedicated, well-described commit to support auditability.

Quick Start

After deployment completes, run the finalization workflow to close out the feature/epic lifecycle, generate artifacts, update docs, and tidy branches. Example actions include updating the roadmap, archiving artifacts, and committing a finalization record.

Frequently Asked Questions about finalize-phase

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I finalize a feature branch after deployment to production?

To finalize a feature branch after deployment, you need to update the roadmap, archive phase artifacts, refresh documentation, and commit a finalization record before cleaning up obsolete local and remote Git branches.

How to update a roadmap after shipping an epic?

Updating a roadmap after shipping an epic involves moving completed features to the 'Shipped' section with deployment dates and version links, generating an epic walkthrough with velocity metrics, and archiving residual artifacts for auditability.

What is the best way to archive project artifacts and clean up Git branches?

The best way to archive artifacts and clean up branches is to validate required phase files in specs/NNN-slug/, commit a well-described finalization record to Git, and then delete obsolete feature branches both locally and remotely.

Do I need Git to generate an epic walkthrough and finalize my project?

Yes, you need Git to commit the finalization record and delete obsolete branches, and you also need access to deployed artifacts like ship-summary and state.yaml to generate the epic walkthrough and complete the finalization process.

Can I automate documentation updates and CHANGELOG generation after a production release?

You can automate documentation updates during finalization by refreshing the README, CHANGELOG, and applicable user guides to reflect new functionality, ensuring all documentation matches the newly deployed production artifacts.

When should I run the finalization workflow for my deployed features?

You should run the finalization workflow immediately after deployments to production or local builds complete, ensuring the feature or epic lifecycle is fully closed and all residual artifacts are properly archived.