harness/claude/skills/idea/SKILL.md
This skill should be used when the user says "idea", "I have an idea", "what if we", "we could", "it would be cool if", "feature idea", "improvement idea", or describes a potential feature, improvement, or exploration they want to capture for later.
npx skillsauth add popoffvg/dotfiles ideaInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Capture ideas with full context so they're actionable later.
/idea <description of the idea>
Gather context inline (fast, no subagent):
git rev-parse --show-toplevel | xargs basenamegit branch --show-currentgit diff --name-only HEAD~3..HEAD 2>/dev/nullSpawn context-keeper agent (haiku model) with this prompt:
Save an idea to memory. Use `memory_save` with type=`task` and the following content:
## <Idea title, 5-10 words> — <date>
**Context:** <repo> / <branch>
**Related files:** <recently changed files, if relevant>
<1-2 paragraphs expanding the idea: what it solves, rough approach, constraints>
### Open questions
- <Things to figure out before implementing>
---
Idea text: <user's idea>
Repo: <repo>
Branch: <branch>
Recent files: <files>
The agent must:
memory_context to check for duplicate ideasmemory_save with the formatted contentAlso write the idea to ~/ctx/insights/_ideas/<slug>.md (slug: lowercase, hyphens, max 60 chars) as a file backup.
Report the saved path and a one-line summary to the user.
testing
Use when the user asks to create test sets, enumerate scenarios, generate edge cases, or draft a coverage matrix before implementation.
testing
Use when the user asks to review, audit, score, or validate test sets for missed cases before execution or merge.
tools
Test harness plugins in isolation using tmux panes. Runs MCP servers, unit tests, typecheck, and Claude plugin loading. Use when user says "test plugin", "check plugin", "run plugin tests", "validate plugin", or names a specific plugin to test.
development
Guide for designing integration and e2e tests using BDD (Behavior-Driven Development) methodology with Cucumber-style Given/When/Then scenarios. Use when writing or reviewing tests for any service, API, or component. Language-agnostic — covers scenario structure, step notation, assertion principles, async patterns, and common anti-patterns.