finish-phase

Update phase.md completion status and commit documented outcomes.

Updated Jan 23, 2026
One-click install
npx skills add https://github.com/cooper538/eshop-demo --skill finish-phase
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: finish-phase
Source: https://github.com/cooper538/eshop-demo/tree/main/.claude/skills/finish-phase
Command: npx skills add https://github.com/cooper538/eshop-demo --skill finish-phase

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill updates a phase's completion status by editing phase.md and documenting the outcome.

Core Features & Use Cases

  • Manual phase completion: Update phase.md status and scope as a final review step.
  • Notes and context: Add notes to capture decisions when auto-detection did not trigger.
  • Auditable commits: Always commits changes to maintain an immutable history.

Quick Start

Use the finish-phase skill to close phase 03 by running the provided command and validating the phase's updated status.

Frequently Asked Questions about finish-phase

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

FAQPage Schema
How do I update a project phase status manually when auto-detection fails?

To update a phase status manually, edit the phase.md file in the specification/phase-XX-* directory to mark completion and document the outcome. This ensures a safe preview and commits the changes to maintain an auditable history.

When do I need to manually mark a phase complete in a workflow?

You need to manually mark a phase complete when the phase requires manual review or when automated detection fails to trigger. This captures final review decisions and adds context notes before committing.

Does finishing a phase generate a git commit automatically?

Yes, finishing a phase always generates a git commit to maintain an immutable history. The process applies a safe preview of the phase.md updates before committing the final status change and notes.

Can I add notes to phase.md when closing a phase?

Yes, you can add optional notes to phase.md when closing a phase to capture decisions and context. This is useful when auto-detection did not trigger and you need to document the final review outcome.

What is the best way to document phase completion for manual review?

The best way to document phase completion is to edit phase.md with the updated status and scope, add optional notes for context, and commit the changes. This provides an auditable record across specification/phase-XX-* directories.