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.).

⭐5stars🔀1forks📁View on GitHub🕐Updated Jan 11, 2026

When & Why to Use This Skill

The 'complete-idea' skill streamlines GitHub-based project workflows by automating the transition of accepted ideas to a completed state. It ensures project backlog integrity by verifying that all derived tasks are finished before updating labels and closing the parent issue, making it an essential utility for maintaining an accurate development roadmap.

Use Cases

  • Legacy Data Cleanup: Manually closing older project ideas that were created before automated lifecycle triggers were implemented.
  • Manual Workflow Reconciliation: Ensuring ideas are properly marked as completed when tasks were linked or created manually outside of standard automation scripts.
  • Project Hygiene & Auditing: Verifying that every sub-task associated with a high-level concept is fully resolved before officially retiring the idea in the repository.
namecomplete-idea
descriptionMark 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:accepted label
  • Is still open
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.