Get the FREE Ultimate OpenClaw Setup Guide →

review-ideas

npx machina-cli add skill rjroy/vibe-garden/review-ideas --openclaw
Files (1)
SKILL.md
2.4 KB

Review Ideas

Refine raw ideas captured by idea: into structured issues or discard them.

When to Use

  • After accumulating ideas via idea: during sessions
  • When ready to process the idea backlog
  • Periodically, to keep .lore/ideas/ from growing stale

Process

  1. Read all files in .lore/ideas/*.md, collecting bullets across all daily files
  2. If no ideas exist, report "No ideas to review" and stop
  3. Present ideas one at a time, oldest first (earliest date file, top bullet first)
  4. For each idea, ask clarifying questions to understand:
    • What was observed or noticed
    • Why it matters
    • What direction a fix or improvement might take
  5. After the conversation clarifies the idea, offer three outcomes:
    • Save as issue: Write to .lore/issues/ with standard frontmatter
    • Discard: Remove without creating an issue
    • Stop: End the review session, leaving remaining ideas for later
  6. After saving or discarding, remove that bullet from the source ideas file
  7. If removing the last bullet leaves only a date header, delete the ideas file
  8. Present the next idea and ask if the user wants to continue

Issue Output

Save to .lore/issues/[kebab-case-title].md

Before writing: Load ${CLAUDE_PLUGIN_ROOT}/shared/frontmatter-schema.md to get frontmatter field definitions and status values for issues.

Document Structure

---
[frontmatter per schema, status: open]
---

# [Issue Title]

## What Happened

[Description of the observation]

## Why It Matters

[Impact or consequence]

## Fix Direction

[Suggested approach, if known]

Removing Processed Bullets

After saving or discarding an idea:

  1. Read the source ideas file
  2. Remove the specific bullet line (- idea text)
  3. If only the date header remains (with optional blank lines), delete the file
  4. Write the updated file back otherwise

Constraints

  • Process one idea at a time. Don't batch.
  • The user controls pace. They can stop at any time.
  • Don't work the issue. Refine understanding and save. Acting on issues is separate.
  • Ideas files are not lore documents. Issues are.

Source

git clone https://github.com/rjroy/vibe-garden/blob/main/lore-development/skills/review-ideas/SKILL.mdView on GitHub

Overview

Review Ideas refines raw ideas captured with idea: prompts into structured issues or discards them. It helps you manage an idea backlog by processing items one at a time, oldest first, with clarified outcomes for each idea.

How This Skill Works

The tool reads all bullets from .lore/ideas/*.md, processes ideas oldest first, and asks clarifying questions about what was observed, why it matters, and potential directions. After the discussion, you choose Save as issue, Discard, or Stop; then the bullet is removed and the source file is cleaned up if needed, before presenting the next idea.

When to Use It

  • After accumulating ideas via idea: prompts during sessions
  • When you're ready to process the idea backlog
  • Periodically to keep .lore/ideas/ from growing stale
  • When you want to decide whether an idea should become an issue
  • When you want to prune the ideas file and align backlog with priorities

Quick Start

  1. Step 1: Read all bullets from .lore/ideas/*.md, collecting them oldest first
  2. Step 2: For each idea, ask clarifying questions (what happened, why it matters, possible fixes)
  3. Step 3: Decide: Save as issue to .lore/issues/[title].md, Discard, or Stop; then remove the bullet

Best Practices

  • Process one idea at a time to avoid batching
  • Ask clarifying questions for each idea: what was observed, why it matters, and potential fixes
  • Tackle ideas oldest first (earliest date file, top bullet first)
  • Choose between Save as issue, Discard, or Stop to pause
  • After action, remove the bullet and delete the source file if it becomes empty

Example Use Cases

  • You have several 'idea:' bullets in .lore/ideas/2026-03-01.md; you start review-ideas to process them one by one and save two as issues
  • A duplicate idea is discarded during a review session to keep the backlog clean
  • An idea is saved as an issue in .lore/issues/my-feature.md with a clear description and fix direction
  • You select Stop to pause the review and resume later, leaving remaining ideas intact
  • After finishing, the processed bullets are removed and the ideas file is deleted if empty

Frequently Asked Questions

Add this skill to your agents
Sponsor this space

Reach thousands of developers