Complete Idea

VerifiedSafe

Mark an accepted idea as completed after all its derived tasks are done. This skill handles edge cases where ideas weren't automatically closed during the conversion process.

Sby Skills Guide Bot
ProductivityIntermediate
306/2/2026
Claude CodeCursorWindsurfCopilotCodex
#idea-management#task-tracking#github-issues#project-workflow

Recommended for

Our review

Marks an accepted idea as completed after verifying all its derived tasks are closed.

Strengths

  • Automates manual idea closure for edge cases not handled by the normal workflow.
  • Verifies that all related tasks are actually closed before closing the idea.
  • Updates labels and adds a structured closing comment.

Limitations

  • Requires the idea to have the `idea:accepted` label.
  • Only handles ideas with tasks referenced in the body or through search.
  • Depends on the `gh` tool to interact with GitHub.
When to use it

Use this skill to manually close an accepted idea whose all derived tasks are done, but which wasn't automatically closed by `/feed-backlog`.

When not to use it

Do not use if the idea is still being validated or if any derived tasks are still open.

Security analysis

Safe
Quality score88/100

The skill only uses GitHub CLI commands to view, label, and close issues within a specific repository. There are no external network calls, destructive system commands, or credential exposure.

No concerns found

Examples

Complete idea #42
Complete idea #42. First check all related tasks are closed.
Mark idea as done
Mark idea #15 as completed. Verify all tasks from it are closed.
Finish idea manually
Idea #7 wasn't closed by feed-backlog. Please complete it after checking its tasks.

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:accepted label
  • 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.

Related skills