finalize

Execute approved implementation plans through development, browser testing, and reporting.

17|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/alexiolan/craft-skills --skill finalize-alexiolan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: finalize
Source: https://github.com/alexiolan/craft-skills/tree/main/skills/finalize
Command: npx skills add https://github.com/alexiolan/craft-skills --skill finalize-alexiolan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Finalize automates executing an approved implementation plan and consolidates development, browser testing, and reporting into a single, auditable workflow.

Core Features & Use Cases

  • Execute the develop phase using the provided plan, ensuring tasks are aligned with the agreed design.
  • Run browser tests after a successful build and consolidate test results into the final report.
  • Generate a concise summary of changes, decisions, and any open items, enabling rapid sign-off and traceability.
  • Detect and auto-select the most recent plan when a specific path is not provided, excluding archived specs.
  • Guardrails ensure Phase 1 must complete successfully before Phase 2, and Phase 2 must complete before Phase 3; failures halt the process with actionable feedback.

Quick Start

Provide the path to an approved implementation plan to execute, and I will develop, test in the browser, and generate a final report.

Frequently Asked Questions about finalize

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

FAQPage Schema
How do I automate end-to-end execution of an approved implementation plan?

You can automate end-to-end plan execution by pointing the workflow to your approved plan repository. It coordinates the develop, browser test, and report phases sequentially to ensure tasks align with the agreed design.

What happens if browser testing fails during automated workflow execution?

If browser testing fails during workflow execution, the process halts immediately. Guardrails ensure Phase 2 cannot proceed until Phase 1 succeeds, and failures provide actionable feedback rather than continuing to the final report generation.

Do I need a specific plan format to automate development and testing?

Yes, you need an existing plan stored in the .claude/plans directory. The workflow requires this structured plan repository to execute development tasks, run browser tests, and generate the final summary of changes and open items.

Can I auto-detect the most recent implementation plan to execute?

Yes, the workflow auto-detects and selects the most recent plan when a specific path is not provided. It automatically excludes archived specs during the selection process to ensure only active plans are executed.

What is the best way to generate a final report after development and browser testing?

The best way to generate a final report is using an automated workflow that consolidates development changes and browser test results. It produces a concise summary of decisions and open items, enabling rapid sign-off and full traceability.

Why does the development phase need to complete before browser testing starts?

The development phase must complete first because guardrails enforce a strict pipeline order: Develop, then Browser Test, then Report. This prevents testing incomplete features and ensures the final report accurately reflects successful builds.