Skip to content
complete-idea logo

Complete Idea

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

SKILL.md

Full skill instructions

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.

More Other skills

Delegate independent tasks to specialized agents working concurrently with isolated context.

295.4K 206.3K
View

Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.

179.7K 100.1K
View

Toolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors/fonts that you can apply to any artifact that has been creating, or can generate a new theme on-the-fly.

179.7K 89.5K
View

A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).

179.7K 76.1K
View

Fundamental design principles for writing maintainable, testable Python code.

40.2K 21.9K
View

Modern responsive layouts using container queries, fluid typography, CSS Grid, and mobile-first strategies.

40.2K 20K
View

Generate Playwright tests from scenarios using interactive browser exploration and validation.

39.7K 18.2K
View

Modern React state management with Redux Toolkit, Zustand, Jotai, and React Query for every state category.

40.2K 14.7K
View

GDPR-compliant data handling with consent management, data subject rights, and privacy controls.

40.2K 14.3K
View

Python error handling patterns including input validation, exception hierarchies, and partial failure handling. Use when implementing validation logic, designing exception strategies, handling batch processing failures, or building robust APIs.

40.2K 13.5K
View

Detailed multi-file refactor planning with safety checks and rollback guidance.

39.7K 13K
View