complete-idea
Mark an idea as completed when all its derived tasks are done. Note: Ideas are automatically closed when converted to tasks via /feed-backlog. Use this skill only for edge cases (manually created tasks, legacy ideas, etc.).
When & Why to Use This Skill
This Claude skill automates the lifecycle management of project ideas within GitHub repositories. It streamlines the transition from 'accepted' to 'completed' by verifying that all dependent tasks are resolved, updating labels, and adding status comments. It is specifically designed to handle edge cases and maintain backlog integrity in developer workflows.
Use Cases
- Legacy Backlog Maintenance: Efficiently closing older project ideas that were created before automated triggers were implemented.
- Manual Workflow Correction: Marking ideas as completed when tasks were manually linked or moved outside of standard automation scripts.
- Project Integrity Auditing: Ensuring that high-level concepts are only archived after a programmatic verification that every associated sub-task is fully closed.
- GitHub Issue Organization: Maintaining a clean repository by automatically transitioning labels from 'idea:accepted' to 'idea:completed' with standardized timestamps.
| name | complete-idea |
|---|---|
| description | Mark an idea as completed when all its derived tasks are done. Note: Ideas are automatically closed when converted to tasks via /feed-backlog. Use this skill only for edge cases (manually created tasks, legacy ideas, etc.). |
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.