complete

Generate 5-final.md and commit ticket closure with standardized Git messages.

Updated Jan 4, 2026
One-click install
npx skills add https://github.com/jayprimer/pmc-marketplace --skill complete-jayprimer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: complete
Source: https://github.com/jayprimer/pmc-marketplace/tree/main/plugins/pmc/skills/complete
Command: npx skills add https://github.com/jayprimer/pmc-marketplace --skill complete-jayprimer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Finalize a completed ticket by generating the final documentation and recording a formal commit, ensuring traceability and closure.

Core Features & Use Cases

  • Generate 5-final.md with Status: COMPLETE or BLOCKED to capture closing rationale.
  • Update 4-progress.md frontmatter to reflect the final state and learning.
  • Create a standardized Git commit message, e.g., "T0000N: complete", to finalize the ticket in version control.
  • Enforce prerequisites like verifying ticket-status and passing required tests before closure.

Quick Start

Run /pmc:complete T0000N to finalize a ticket by creating 5-final.md and updating 4-progress.md.

Frequently Asked Questions about complete

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

FAQPage Schema
How do I finalize a project ticket with documentation and a commit?

To finalize a project ticket, generate a 5-final.md document capturing the closing rationale and create a standardized Git commit like "T0000N: complete" to ensure traceability and closure.

What is the best way to update progress frontmatter when completing a ticket?

Updating progress frontmatter involves modifying the 4-progress.md file to reflect the final ticket status, such as COMPLETE or BLOCKED, and documenting any final learnings before committing changes.

Do I need existing ticket metadata to generate finalization documents?

Yes, existing ticket metadata and access to 4-progress.md are required prerequisites. The finalization process enforces verifying ticket-status and passing required tests before generating 5-final.md.

Can I mark a ticket as BLOCKED instead of COMPLETE during finalization?

Yes, the finalization workflow supports generating 5-final.md with a Status set to BLOCKED to capture the closing rationale when a ticket cannot be fully completed.

What's the standardized commit message pattern for finalizing a ticket?

The standardized commit message pattern for finalizing a ticket follows a specific format like "T0000N: complete", ensuring consistent traceability and formal closure within version control.

Why does ticket finalization require passing tests before generating final docs?

Ticket finalization requires passing tests to enforce prerequisites before closure. This ensures code quality and proper ticket-status verification before generating the 5-final.md document and committing changes.