メニュー
Finds ideas that have been sitting untouched in your backlog and helps you decide what to do with each one — revive it, refine it, or abandon it. Use when your backlog has accumulated cruft over time.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
SOC 職業分類に基づく
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/wdm0006/idealog-skills --skill stale-ideas-auditコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SKILL.md を表示中
Generates a weekly summary of your idea.log activity — new ideas captured, progress made, ideas completed or abandoned — with suggestions for what to focus on next. Use at the start or end of each week.
Reviews all pending ideas in idea.log, cleans up stale or duplicate entries, improves descriptions, suggests tags, and helps prioritize what to work on next. Use when your idea backlog feels cluttered or you want to start a focused work session.
Picks an idea from your idea.log backlog and autonomously starts building it — scaffolding a project, writing initial code, setting up the repo. Use when you want to turn an idea into a real project without doing the setup yourself.
| name | stale-ideas-audit |
| description | Finds ideas that have been sitting untouched in your backlog and helps you decide what to do with each one — revive it, refine it, or abandon it. Use when your backlog has accumulated cruft over time. |
Works with idea.log. Get it on the App Store.
search_ideas to get the full listget_idea for each pending idea to check creation dates and commentsAbandoned with a reason.update_idea and add_comment (use idea.log's canonical status values — see the shared reference)| Signal | Staleness Level |
|---|---|
| No first step, no comments, no tags | High — likely a drive-by capture that was never developed |
| Has first step but untouched for 30+ days | Medium — was once prioritized but lost momentum |
| Has comments but status is still Pending | Low — actively being thought about, just not started |
| Tagged "someday" or "low" priority | Expected — not stale, just deferred |
For each stale idea, present:
Idea: "[idea content]"
Created: [date]
Tags: [tags or "none"]
First step: [step or "none"]
Comments: [count]
Recommendation: [Revive / Refine / Abandon] — [reason]
What would you like to do? [revive / refine / abandon / skip]
Process ideas in batches of 3-5 to avoid overwhelming the user. After each batch, ask if they want to continue.
Input:
Audit my stale ideas
Actions:
Found 7 stale ideas out of 18 pending.
Batch 1:
1. "that API thing" — created 52 days ago, no tags, no first step, no comments
Recommendation: Abandon — too vague, hasn't been touched in nearly 2 months
→ User chose: Abandon ✓
2. "Learn Rust" — created 41 days ago, tagged "learning", no first step
Recommendation: Refine — still relevant but needs a specific goal
→ User chose: Refine → updated to "Learn Rust by building a small CLI tool"
Added first step: "Complete chapters 1-3 of The Rust Book"
3. "Redesign portfolio" — created 33 days ago, has first step, 1 comment
Recommendation: Revive — you commented on this recently, just needs momentum
→ User chose: Skip — will get to it next week
Summary: 1 abandoned, 1 refined, 1 skipped. 4 remaining stale ideas.
Continue? [yes/no]
Stale Ideas Audit:
- [ ] Identified all stale ideas using staleness criteria
- [ ] Presented each with a recommendation
- [ ] Applied user decisions (revive, refine, abandon, skip)
- [ ] Added comments documenting audit decisions
- [ ] Presented final summary of actions taken