Complete Idea

VerifiedSafe

Manually closes an accepted idea after verifying that all its derived tasks are completed. This is useful for edge cases where the idea wasn't automatically closed, such as manually converted tasks or legacy ideas predating the auto-close feature.

Sby Skills Guide Bot
ProductivityIntermediate
606/2/2026
Claude Code
#github-issues#idea-management#project-workflow#task-completion

Recommended for

Our review

Marks an idea as completed once all its derived tasks are done, handling cases where automatic closure did not occur.

Strengths

  • Automates manual closure of ideas for edge cases
  • Verifies automatically that all related tasks are closed
  • Updates labels and adds a completion comment

Limitations

  • Only needed for edge cases (manually created tasks, legacy ideas)
  • Relies on GitHub CLI tool (gh)
  • Does not replace human review of task completeness
When to use it

Use this skill when an accepted idea was not automatically closed after being converted to tasks and all tasks are now completed.

When not to use it

Do not use it if the derived tasks are not all closed or if the idea was already automatically closed.

Security analysis

Safe
Quality score90/100

The skill uses gh CLI commands to manipulate issues in a specific repository, with no external data exfiltration, no destructive system commands, and no obfuscated payloads. All actions are constrained to GitHub issue management.

No concerns found

Examples

Complete idea after manual task creation
Mark idea #15 as completed now that all its manually created tasks are done.
Close legacy idea with finished tasks
Complete the legacy idea about refactoring authentication, all related issues are closed.

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