finalize-phase

Automate end-of-cycle closure for features and epics after deployment.

Updated Feb 14, 2026
One-click install
npx skills add https://github.com/DYAI2025/MOD_shark-engine --skill finalize-phase-dyai2025
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: finalize-phase
Source: https://github.com/DYAI2025/MOD_shark-engine/tree/main/sharkengine/.claude/skills/finalize-phase
Command: npx skills add https://github.com/DYAI2025/MOD_shark-engine --skill finalize-phase-dyai2025

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

After deployment, teams need a clean, auditable closure that updates roadmaps, archives artifacts, updates documentation, and removes obsolete branches, ensuring knowledge is preserved for future work.

Core Features & Use Cases

  • Epic Walkthrough Generation (NEW in v5.0): generates a comprehensive walkthrough and audit report for epics to capture velocity, lessons learned, and improvement opportunities.
  • Update Roadmap: moves shipped features to the Shipped section with version and deployment details.
  • Archive Artifacts: ensures all specs, plans, and reports are preserved in specs/NNN-slug/.
  • Update Documentation: updates README, CHANGELOG, and user guides for shipped features.
  • Clean Up Branches: deletes feature branches post-merge or deployment.
  • Commit Finalization: creates a concise finalization commit documenting changes and state.yaml updates.
  • State Tracking: updates finalization status in state.yaml.
  • Quality & Compliance: produces artifacts that support post-mortem analysis and compliance.

Quick Start

After deployment completes, run the finalization workflow to close out the feature and seal the project state.

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 workflow after deployment to ensure clean branch cleanup?

Feature finalization after deployment automates branch cleanup by deleting merged feature branches, creating a concise finalization commit, and updating state.yaml to seal the project state.

What is the best way to archive feature artifacts and update documentation post-merge?

The best way to archive artifacts post-merge is to preserve specs, plans, and reports in specs/NNN-slug/ directories while simultaneously updating README, CHANGELOG, and user guides for the shipped features.

How do I update a roadmap to reflect shipped features and deployment details?

Updating a roadmap to reflect shipped features involves moving completed items to the Shipped section, appending version numbers, and logging deployment details to maintain an accurate project trajectory.

Can I generate an epic walkthrough to capture velocity and lessons learned after deployment?

Yes, you can generate an epic walkthrough after deployment to produce a comprehensive audit report that captures team velocity, lessons learned, and actionable improvement opportunities for future cycles.

Does feature finalization support post-mortem analysis and compliance audits?

Feature finalization supports post-mortem analysis and compliance audits by producing preserved artifacts, finalization commit records, and state.yaml updates that document changes and final project state.

What is included in an end-of-cycle closure for epics and features?

End-of-cycle closure for epics and features includes epic walkthrough generation, roadmap updates, artifact archival in specs directories, documentation changes, branch cleanup, and finalization commits.