feature-done

Validate acceptance criteria and archive completed features to ~/.claude/features/done/.

1|Updated May 6, 2023
One-click install
npx skills add https://github.com/TobiasLaross/dotfiles --skill feature-done
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature-done
Source: https://github.com/TobiasLaross/dotfiles/tree/main/agentic/skills/feature-done
Command: npx skills add https://github.com/TobiasLaross/dotfiles --skill feature-done

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill verifies that a completed feature meets all acceptance criteria and safeguards against loose ends by archiving it into the designated done folder.

Core Features & Use Cases

  • Validate acceptance criteria in story.md and verify review status in review-fixes.md.
  • Move the finished feature directory to ~/.claude/features/done/<name>, creating the destination if needed.
  • Clean up associated worktrees and tmux sessions when present, reporting what was removed.

Quick Start

Run the feature-done workflow when a feature is ready to be archived.

Frequently Asked Questions about feature-done

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

FAQPage Schema
How do I archive a completed feature and verify its acceptance criteria?

To archive a completed feature, this workflow validates acceptance criteria in story.md and review-fixes.md, then moves the feature directory to ~/.claude/features/done/. It ensures all checklist requirements are satisfied before safe archival.

What is the best way to clean up git worktrees and tmux sessions after finishing a feature?

Cleaning up git worktrees and tmux sessions after finishing a feature is handled during the archival process. The workflow detects associated worktrees and tmux sessions, reports what was removed, and preserves source worktrees.

Does the feature archival process delete my source git worktrees?

No, the feature archival process performs safe archival without deleting source git worktrees. It moves the finished feature directory to the done folder and only cleans up associated optional worktrees and tmux sessions.

How do I validate review status before archiving a feature directory?

To validate review status before archiving a feature directory, the workflow checks review-fixes.md alongside story.md and design.md artifacts to verify all acceptance criteria are met before moving the directory.

Can I use this workflow to manage feature stories across story.md and design.md artifacts?

Yes, you can use this workflow to manage feature completion across story.md, design.md, and review-fixes.md artifacts. It validates acceptance criteria across these files and handles optional worktrees and tmux sessions during cleanup.

What happens if acceptance criteria validation fails during feature archival?

If acceptance criteria validation fails during feature archival, built-in guardrails prevent the move to the done folder and a final status report indicates which checklist validations or file presence requirements were not met.