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
6/2/2026
Claude Code
#github-issues#idea-management#project-workflow#task-completion

Recommended for

Automated summary

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

How this analysis is made

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.

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/complete-idea-mmk3ni8w/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/complete-idea-mmk3ni8w' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/complete-idea-mmk3ni8w/download' --output '.skill-downloads/complete-idea-mmk3ni8w/SKILL.md.part' && mv '.skill-downloads/complete-idea-mmk3ni8w/SKILL.md.part' '.skill-downloads/complete-idea-mmk3ni8w/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

This file does not provide a usable name/description header for this native procedure. It remains available to download and inspect; use the manual method below.

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/complete-idea-mmk3ni8w/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills