Complete Idea

VerifiedSafe

Mark an accepted idea as completed after all its derived tasks are done. Use only for edge cases as ideas are automatically closed when converted to tasks.

Sby Skills Guide Bot
DevelopmentIntermediate
306/2/2026
Claude Code
#idea-management#github-issues#task-completion#edge-case

Recommended for

Our review

Marks an accepted idea as completed after verifying all derived tasks are closed, for cases where automatic closure didn't occur.

Strengths

  • Ensures traceability of ideas in the workflow
  • Automates verification of associated tasks
  • Uses GitHub CLI for precise actions

Limitations

  • Requires tasks to be explicitly referenced in the idea body
  • Only handles ideas with the 'idea:accepted' label
  • Does not cover ideas without derived tasks
When to use it

When you have an accepted idea that wasn't automatically closed after task conversion, e.g., manually created or legacy ideas.

When not to use it

For ideas recently converted via /feed-backlog, as they are automatically closed.

Security analysis

Safe
Quality score85/100

The skill only uses gh CLI commands to view, list, and edit issues within the user's own repository. There are no destructive operations, external data exfiltration, or unsafe script executions. All commands are standard and non‑harmful.

No concerns found

Examples

Complete a manually created idea
Idea #15 was manually converted to tasks and all tasks are done. Mark it as completed.
Handle a legacy idea
Complete idea #42 about refactoring – all its tasks are closed but it's still open.

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