skills.rest
stars-end
stars-endOFFICIAL
Explore all skills by this author →
GitHub

finish-feature

Automate epic and feature completion with verification, archiving, and Serena caching.

Updated Aug 27, 2026
Search Tags:#git#workflow#beads#cleanup#archiving#epic management#feature completion
One-click install
npx skills add https://github.com/stars-end/affordabot --skill finish-feature-stars-end
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: finish-feature
Source: https://github.com/stars-end/affordabot/tree/main/.claude/skills/finish-feature
Command: npx skills add https://github.com/stars-end/affordabot --skill finish-feature-stars-end

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Completing large features or epics often involves manual cleanup, documentation archiving, and ensuring all related tasks are properly closed, which can be tedious and error-prone.

Core Features & Use Cases

  • Automated Epic Completion: Verifies all child tasks are closed, archives documentation, caches knowledge to Serena, and formally closes the epic.
  • Atomic Feature Closure Verification: Ensures non-epic issues were closed at PR creation time, maintaining a clean and atomic merge pattern.
  • Knowledge Preservation & Cleanup: Offers to archive documentation and external skill references, caches content for future searchability, and provides options for Git branch cleanup.
  • Use Case: When you've completed an epic or feature, simply say "I'm done with this epic," and this Skill will guide you through the final steps of verification, archiving, and cleanup.

Quick Start

When you've completed an epic or feature and are ready to finalize it, simply say: "I'm done with this epic"

Frequently Asked Questions about finish-feature

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

FAQPage Schema
How do I automate closing an epic with all its child tasks?▼

Automated epic completion verifies all child tasks are closed, archives documentation, caches knowledge to Serena, and formally closes the epic. Say "I'm done with this epic" to trigger verification, archiving, and closure steps automatically.

What happens when I complete a feature—do I need to manually close related tasks?▼

Feature closure verification ensures non-epic issues were closed atomically at PR creation time. The Skill checks completion status across related tasks, maintaining a clean merge pattern without manual tracking.

Can I archive documentation and clean up Git branches when finishing a feature?▼

Yes. The Skill offers optional documentation archiving, external skill reference cleanup, Git branch removal, and Serena caching. This preserves knowledge while removing stale artifacts from your workflow.

How does the Skill handle large epics with many subtasks?▼

It applies completion verification across epics, features, tasks, and bugs. Context setup retrieves current issue state, verifies child closure and commit status, then orchestrates archiving and final closure in one workflow.

What's the difference between feature and epic completion workflows?▼

Epic completion closes all child tasks and archives documentation. Feature completion verifies atomic closure at PR merge and handles branch cleanup. Both cache knowledge to Serena for future searchability.

Related Skills

Explore More Software Engineering Skills→
GGPromptsGGPrompts
147

brainstorming

Convert vague ideas into structured beads workflows with epics and dependencies.

Community
Basic
NEXTAltairNEXTAltair
1

mcp-memory-first-development

Synchronize short-term project memories with long-term design knowledge across development workflows.

Community
Basic
friedbotstudiofriedbotstudio
5

commit

Stage and commit baseline workflow changes with archive synchronization and consent checks.

Official
Advanced
gustavofsantosgustavofsantos

cdd-integrator

Merge completed track knowledge into global specifications and archive tracks.

Community
Intermediate