feature-complete

Finalize feature docs, update ROADMAP, and close related issues on feature branches.

Updated Apr 26, 2026
One-click install
npx skills add https://github.com/oletizi/writingcontrol.org --skill feature-complete
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature-complete
Source: https://github.com/oletizi/writingcontrol.org/tree/main/.claude/skills/feature-complete
Command: npx skills add https://github.com/oletizi/writingcontrol.org --skill feature-complete

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manages feature-complete handoffs by ensuring docs are moved to the 003-COMPLETE location, ROADMAP is updated to reflect completion, and related issues are closed automatically on feature branches.

Core Features & Use Cases

  • Move docs from the in-progress area to 003-COMPLETE to reflect finished work.
  • Update ROADMAP entries to mark the feature as Complete and guide next steps.
  • Close related GitHub issues and PRs with a completion note to maintain project hygiene.
  • Generate a concise completion report detailing what was moved, what ROADMAP sections changed, and which issues were closed.

Quick Start

Run the feature-complete workflow on your feature branch to finalize docs, refresh the ROADMAP, and close related issues.

Frequently Asked Questions about feature-complete

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

FAQPage Schema
How do I automate feature release hygiene on a git branch?

Automate feature release hygiene by finalizing docs, updating ROADMAP, and closing related issues on the feature branch. This workflow moves docs to the complete location, marks ROADMAP entries as complete, and closes GitHub issues with a completion note.

What's the best way to update a project ROADMAP when a feature is complete?

Update a project ROADMAP when a feature is complete by running an automated workflow that marks entries as Complete and guides next steps. It also moves corresponding docs to the 003-COMPLETE area to reflect finished work.

How does branch workflow issue closing work for completed features?

Branch workflow issue closing works by identifying the feature, verifying the corresponding PR, and closing related GitHub issues with a completion note. It maintains project hygiene by automatically resolving tracked items tied to the branch.

Do I need a corresponding PR to finalize feature docs?

Yes, you need a corresponding PR to finalize feature docs. The workflow implements steps to identify the feature and verify its corresponding PR before moving docs, updating the feature README, and committing changes.

Can I generate a completion report after moving docs and closing issues?

Yes, you can generate a completion report after moving docs and closing issues. The workflow produces a concise report detailing what docs were moved, what ROADMAP sections changed, and which issues were closed.

Why does feature-complete require a branch-based workflow?

Feature-complete requires a branch-based workflow because it is designed for software projects that formalize documentation moves, ROADMAP updates, and issue closing directly on feature branches when features are completed.