finalize

Name: finalize
Availability: InStock
Author: paycrux

Merge Implementation Map into spec.md and remove temporary task documents.

Updated Mar 30, 2026

Search Tags:#documentation #qa #spec #task-management #finalize #project-workflow #implementation-map

Ready to run

npx skills add https://github.com/paycrux/ai-skills --skill finalize-paycrux

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: finalize
Source: https://github.com/paycrux/ai-skills/tree/main/.claude/skills/finalize
Command: npx skills add https://github.com/paycrux/ai-skills --skill finalize-paycrux

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Consolidate and tidy task documents after implementation, evaluation, and QA, producing a minimal, long-lived spec and removing temporary working documents.

Core Features & Use Cases

Merges the Implementation Map into spec.md to keep the behavioral spec and mapping aligned.
Deletes or archives temporary working documents while preserving essential artifacts (README.md, spec.md, ui-spec.md, test-cases.md).
Ensures traceability for completed tasks by updating status and presenting a clean, finalized task folder.

Quick Start

Run /finalize <task-folder> to merge documents and prune temporary files.

Frequently Asked Questions about finalize

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

FAQPage Schema

How do I consolidate task documents into a minimal long-lived spec after QA?▼

To consolidate task documents, merge the Implementation Map into spec.md and remove temporary working files like progress.md. This ensures your behavioral spec stays aligned with the finalized implementation map for completed tasks.

How does merging an implementation map into spec.md work?▼

Merging an implementation map into spec.md extracts source data from findings.md and progress.md, then integrates those details directly into your behavioral specification. This preserves essential project workflow traceability within a single file.

What temporary files are safe to delete when finalizing a project workflow?▼

When finalizing a project workflow, it is safe to delete temporary docs like tasks.md, findings.md, progress.md, and evaluate.md. Essential artifacts including README.md, spec.md, ui-spec.md, and test-cases.md are preserved.

Do I need a spec.md file to finalize task documentation?▼

Yes, a spec.md file must exist in your task folder to finalize documentation. The tool enforces this precondition because it updates the existing behavioral spec rather than generating one from scratch.

What is the best way to tidy task folders marked as complete under docs?▼

The best way to tidy complete task folders is to run a finalize command that merges changes into spec.md, updates the README status, and prunes temporary working documents while preserving essential artifacts for a clean project workflow.

Why does finalizing task docs update the README status?▼

Updating the README status during finalization ensures traceability for completed tasks by reflecting the finalized state. It marks the task folder as complete and presents a clean, organized set of long-lived documentation.