Delegate independent tasks to specialized agents working concurrently with isolated context.
Feature Closer
closer
This skill should be used when the user asks to "close feature", "archive feature", "complete feature N", "move feature to completed", or wants to move a finished feature to the _completed/ directory.
SKILL.md
Full skill instructions
Feature Closer
Primary Directive
Close and archive a completed feature, moving it from active backlog to completed.
Input
Feature identifier: ${input:FeatureID (e.g., 003 or 003-my-feature)}
Step 1: Resolve Feature
Determine the feature to close:
- If input provided, use it to find the feature folder
- If no input, try to detect from current branch name (
feature/{NNN}-{slug})
# List active features in backlog (not in completed/)
ls -d backlog/plans/[0-9][0-9][0-9]-*/ 2>/dev/null | head -20
# Get current branch
git branch --show-current
Match the feature ID (NNN or NNN-slug) to a folder in backlog/plans/.
If no matching feature found: Report error and stop.
Step 2: Validate Completion
Read the feature's tasks.md and check for incomplete tasks.
# Check for unchecked tasks (- [ ] pattern)
grep -c '^\s*- \[ \]' backlog/plans/{NNN}-{slug}/tasks.md 2>/dev/null || echo "0"
If incomplete tasks exist: Use the AskUserQuestion tool to ask the user how to proceed:
- "Close anyway (mark as incomplete)"
- "Cancel and finish tasks first"
Only proceed if user chooses to close anyway or all tasks are complete.
Step 3: Move Feature Folder
# Ensure completed/features directory exists
mkdir -p backlog/plans/_completed
# Move the feature folder
mv backlog/plans/{NNN}-{slug} backlog/plans/_completed/
Step 4: Update Documentation References
Search for and update any references to the old path in documentation files.
4a: Find References
# Find files referencing the old backlog path (excluding completed/ and .ai/ logs)
grep -rl "backlog/plans/{NNN}-{slug}" . --include="*.md" 2>/dev/null | grep -v -e "^./backlog/plans/_completed/" -e "^./.ai/"
4b: Update References
For each file found, update paths from:
backlog/plans/{NNN}-{slug}/→backlog/plans/_completed/{NNN}-{slug}/../backlog/plans/{NNN}-{slug}/→../backlog/plans/_completed/{NNN}-{slug}/
Common files to check:
.claude/commands/planner.md(Reference section examples)aidocs/feature-planning-methodology.md- Any README files referencing the feature
Important: Do NOT update paths in:
specs/tests/(spec tests stay in place).ai/(progress logs are historical records)- The feature's own docs (they moved, so relative paths may still work)
Step 5: Commit Changes
Stage and commit all changes from the move and path updates.
# Stage the move and any updated docs
git add -A
# Commit with descriptive message
git commit -m "chore: close feature {NNN}-{slug}
- Move backlog/plans/{NNN}-{slug}/ to backlog/plans/_completed/
- Update documentation references
Co-Authored-By: Claude Sonnet <[email protected]>"
Step 6: Summary
Output a summary:
Feature Closed: {NNN}-{slug}
Actions Taken:
✅ Moved backlog/plans/{NNN}-{slug}/ → backlog/plans/_completed/{NNN}-{slug}/
✅ Updated N documentation references
✅ Committed changes
Spec Tests: specs/tests/{NNN}-{slug}.md (unchanged)
Next Steps:
1. Review the commit: git show HEAD
2. Merge to master when ready: git checkout master && git merge feature/{NNN}-{slug}
3. Delete feature branch after merge: git branch -d feature/{NNN}-{slug}
Error Handling
- Feature not found: List available features and ask user to specify
- Already in completed/: Report that feature is already closed
- Git dirty state: Warn user about uncommitted changes before proceeding
- Move fails: Report error, do not proceed with doc updates
More Other skills
brand-guidelines
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
theme-factory
Toolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors/fonts that you can apply to any artifact that has been creating, or can generate a new theme on-the-fly.
internal-comms
A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).
Fundamental design principles for writing maintainable, testable Python code.
responsive-design
Modern responsive layouts using container queries, fluid typography, CSS Grid, and mobile-first strategies.
Generate Playwright tests from scenarios using interactive browser exploration and validation.
Automated website exploration and test case generation using Playwright.
Modern React state management with Redux Toolkit, Zustand, Jotai, and React Query for every state category.
gdpr-data-handling
GDPR-compliant data handling with consent management, data subject rights, and privacy controls.
Python error handling patterns including input validation, exception hierarchies, and partial failure handling. Use when implementing validation logic, designing exception strategies, handling batch processing failures, or building robust APIs.
refactor-plan
Detailed multi-file refactor planning with safety checks and rollback guidance.
