When is the right time to use the complete skill?

You should use it once all implementation is done, unit tests are passing, and you are ready to move from the 'in-progress' state to a finalized state.

What information is captured in the final report?

The 5-final.md report includes a summary of accomplishments, a list of modified files, test pass counts, discovered user intents, and retrospective lessons learned.

Can I use this skill if a ticket cannot be finished?

Yes, the skill supports a BLOCKED status which allows you to document the reasons for the stoppage and what is required to unblock the task.

Does it automatically commit my code changes?

Yes, after generating the documentation and passing linting checks, the skill performs a Git commit with a standardized 'TXXXX: complete' message.

PMC Ticket Completion

Name: PMC Ticket Completion
Author: jayprimer

byjayprimer

Productivity & Workflow

Finalizes project tasks by generating standardized documentation, verifying test results, and automating git commits.

About

The PMC Complete skill is a vital workflow utility for the Project Manager Claude (PMC) ecosystem, designed to ensure every development task is closed with professional-grade documentation. It guides the user through a multi-step verification process: checking ticket readiness, validating that all tests pass, and generating a comprehensive 5-final.md report. By capturing 'revealed intent' and lessons learned, it transforms a simple code change into a rich knowledge base entry. This skill eliminates manual documentation drudgery and ensures your repository history remains clean, consistent, and informative.

Key Features

Knowledge Base integrity linting to prevent documentation drift
Automated 5-final.md generation with structured sections for changes and tests
Pre-completion validation ensuring all requirements and tests are met
Support for both COMPLETE and BLOCKED status workflows
0 GitHub stars
Standardized Git commit automation for consistent project history

Use Cases

Capturing project insights and user preferences discovered during the development cycle
Closing out a feature ticket with a full summary of changes and test verification
Documenting why a specific task was blocked and outlining the steps to resume

About

Key Features

Knowledge Base integrity linting to prevent documentation drift
Automated 5-final.md generation with structured sections for changes and tests
Pre-completion validation ensuring all requirements and tests are met
Support for both COMPLETE and BLOCKED status workflows
0 GitHub stars
Standardized Git commit automation for consistent project history

Use Cases

Capturing project insights and user preferences discovered during the development cycle
Closing out a feature ticket with a full summary of changes and test verification
Documenting why a specific task was blocked and outlining the steps to resume