Agent skill
complete-idea
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/productivity/complete-idea
SKILL.md
Complete Idea
Mark an accepted idea as completed after all its derived tasks are done.
Note: Since /feed-backlog automatically closes ideas when converting them to tasks, this skill is primarily for edge cases:
- Ideas that were manually converted to tasks (not via
/feed-backlog) - Legacy ideas that predate the auto-close feature
- Cases where an idea needs to be closed but wasn't automatically closed
Instructions
When completing idea #N:
Step 1 - Fetch the Idea
gh issue view N --repo jmlweb/tooling --json number,title,body,labels,state
Verify:
- Has
idea:acceptedlabel - Is still open
Step 2 - Find Related Tasks
gh issue list --repo jmlweb/tooling --search "idea #N in:body" --state all --json number,title,state
Also check the idea's body for task references.
Step 3 - Verify Task Completion
Check if all related tasks are closed. If any are still open, inform user.
Step 4 - Mark as Completed
gh issue edit N --repo jmlweb/tooling \
--remove-label "idea:accepted" \
--add-label "idea:completed"
gh issue comment N --repo jmlweb/tooling --body "## Idea Completed
All tasks derived from this idea have been implemented.
**Completed on:** $(date +%Y-%m-%d)"
gh issue close N --repo jmlweb/tooling
Idea Lifecycle
/add-idea -> Creates idea (idea:pending)
/validate-ideas -> Accepts or rejects (idea:accepted | idea:rejected)
/feed-backlog -> Creates tasks from accepted ideas AND closes the idea automatically
/next-task -> Implements tasks
complete-idea -> Manual closure for edge cases (normally not needed)
Normal Flow: Ideas are automatically closed when converted to tasks via /feed-backlog. This skill is only needed for edge cases.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?