feat: add Ideas workflow for capturing and developing ideas (#7)

- Add ideas/ folder to vault structure
- Add idea type with status lifecycle (new → developing → decided)
- Add Idea.md template with sections for idea development
- Add /synapse-review-ideas command for weekly idea review
- Add idea-specific frontmatter fields (status, category, outcome)
- Update CLAUDE.md and README.md with Ideas Workflow documentation

Author: julien731

.claude/commands/synapse-review-ideas.md

@@ -0,0 +1,103 @@
+# Synapse Review Ideas Command
+
+Weekly review of ideas to develop them further, promote them to projects, or discard them.
+
+## Purpose
+
+Ideas need regular attention to progress. This command surfaces ideas that need decisions and helps move them through the lifecycle:
+
+```
+new → developing → decided (project or discarded)
+```
+
+## Scope
+
+By default, review all ideas with `status: new` or `status: developing`.
+
+If the user specifies a category filter, only review ideas matching that category.
+
+## Process
+
+### 1. Gather Ideas for Review
+
+Find all notes in `ideas/` where:
+- `status: new` (never reviewed), OR
+- `status: developing` (in progress)
+
+Sort by:
+1. `status: new` first (need initial review)
+2. Then by `created` date (oldest first)
+
+### 2. Present Ideas
+
+For each idea, show:
+- **Title** (filename)
+- **Category** (`product`, `workflow`, `content`, `personal`)
+- **Age** (days since created)
+- **Summary** (from frontmatter)
+- **Content preview** (first section if helpful)
+
+### 3. For Each Idea, Ask
+
+Present options using AskUserQuestion:
+
+**"What should we do with this idea?"**
+
+Options:
+- **Keep developing** - Add thoughts, connections, or notes; stays at `status: developing`
+- **Promote to project** - Ready to act on; will create a project and link it
+- **Discard** - Not worth pursuing; mark `status: decided`, `outcome: discarded`
+- **Skip for now** - Leave unchanged, review next time
+
+### 4. Handle Each Decision
+
+**Keep developing:**
+1. Set `status: developing` (if was `new`)
+2. Ask: "Any thoughts to add?" (optional)
+3. If yes, append to the Notes section
+4. Update `related` if user mentions connections
+
+**Promote to project:**
+1. Ask: "What should the project be called?"
+2. Create new project in `projects/` using Project Brief template
+3. Copy relevant content from idea to project
+4. Update idea: `status: decided`, `outcome: "[[projects/Project Name]]"`
+5. Add `related: [[ideas/Idea Name]]` to the new project
+
+**Discard:**
+1. Optionally ask: "Any reason to note?" (helps future reference)
+2. Update idea: `status: decided`, `outcome: discarded`
+3. If reason given, append to Notes section
+
+**Skip:**
+- No changes, move to next idea
+
+### 5. Summary Report
+
+After reviewing all ideas, provide:
+- Total ideas reviewed
+- Decisions made:
+  - X kept developing
+  - X promoted to projects (with links)
+  - X discarded
+  - X skipped
+- Ideas remaining for next review
+
+## Example Usage
+
+User: `/synapse-review-ideas`
+→ Review all new and developing ideas
+
+User: `/synapse-review-ideas product`
+→ Review only product ideas
+
+User: `/synapse-review-ideas --new`
+→ Review only new ideas (skip developing)
+
+## Notes
+
+- Keep the review lightweight; don't force decisions on every idea
+- Some ideas need time to incubate; "skip" is a valid choice
+- When promoting to project, carry over the "Why It Matters" and "Open Questions" sections
+- Discarded ideas stay in the vault; they may become relevant later
+- If there are many ideas, consider batching by category

CHANGELOG.md

@@ -5,6 +5,21 @@ All notable changes to Synapse will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [0.2.0] - 2026-01-26
+
+### Added
+
+- Ideas workflow for capturing and developing ideas before they become projects
+  - New `ideas/` folder in vault structure
+  - New `idea` type with status lifecycle: `new` → `developing` → `decided`
+  - New `Idea.md` template with sections for The Idea, Why It Matters, Open Questions, Next Steps
+  - New `/synapse-review-ideas` command for weekly idea review
+- Idea-specific frontmatter fields:
+  - `status`: `new`, `developing`, `decided`
+  - `category`: `product`, `workflow`, `content`, `personal`
+  - `outcome`: links to resulting project or `discarded`
+- Ideas Workflow documentation in README.md explaining lifecycle, categories, and weekly review process
+
 ## [0.1.0] - 2026-01-10
 
 ### Added

CLAUDE.md

@@ -28,6 +28,7 @@ vault/
 ├── .claude/        # Claude commands and configuration
 ├── inbox/          # Unprocessed items (captures, imports, quick notes)
 ├── projects/       # Active project briefs and planning
+├── ideas/          # Ideas at various stages of development
 ├── areas/          # Ongoing areas of responsibility
 ├── resources/      # Reference material, research, learning notes
 ├── people/         # Contact notes (clients, candidates, partners, colleagues)
@@ -42,7 +43,7 @@ All notes use YAML frontmatter. Key fields:
 
 | Field | Purpose |
 |-------|---------|
-| `type` | Note classification: `daily`, `meeting`, `project`, `resource`, `area`, `person`, `reflection` |
+| `type` | Note classification: `daily`, `meeting`, `project`, `idea`, `resource`, `area`, `person`, `reflection` |
 | `status` | Current state: `active`, `completed`, `archived`, `on-hold` |
 | `summary` | One-sentence description for AI retrieval (read this first) |
 | `tags` | Topics and themes as array |
@@ -97,6 +98,7 @@ When reviewing manually-created notes (via `/synapse-review` command), check and
 | `meeting` | `date`, `meeting_type`, `attendees` |
 | `person` | `company`, `role`, `context` |
 | `project` | `client` (if applicable), `phase` |
+| `idea` | `category`, `outcome` (when decided) |
 
 ### Content Standards
 

README.md

@@ -34,6 +34,7 @@ vault/
 ├── .claude/        # Claude commands and configuration
 ├── inbox/          # Unprocessed items (captures, imports, quick notes)
 ├── projects/       # Active project briefs and planning
+├── ideas/          # Ideas at various stages of development
 ├── areas/          # Ongoing areas of responsibility
 ├── resources/      # Reference material, research, learning notes
 ├── people/         # Contact notes
@@ -48,7 +49,7 @@ All notes use YAML frontmatter with these fields:
 
 | Field | Required | Values | Purpose |
 |-------|----------|--------|---------|
-| `type` | Yes | `daily`, `meeting`, `project`, `resource`, `area`, `person`, `reflection` | Note classification |
+| `type` | Yes | `daily`, `meeting`, `project`, `idea`, `resource`, `area`, `person`, `reflection` | Note classification |
 | `status` | For actionable | `active`, `completed`, `archived`, `on-hold` | Current state |
 | `summary` | Yes | One sentence | AI retrieval optimization |
 | `tags` | Recommended | Array of strings | Topics and themes |
@@ -113,6 +114,34 @@ One concept per file. Smaller, focused notes (300-500 words) retrieve more preci
 | Ambiguous pronouns | Referent unclear in isolation |
 | Links without context | AI may not follow links |
 
+## Ideas Workflow
+
+Ideas are generative notes that need space to incubate before becoming projects or being discarded. Unlike resources (reference material you consume), ideas are things you develop over time.
+
+**Lifecycle:**
+
+```
+new → developing → decided
+```
+
+| Status | Meaning |
+|--------|---------|
+| `new` | Just captured, hasn't been reviewed yet |
+| `developing` | Actively thinking about it, adding connections |
+| `decided` | Fate determined (became a project or discarded) |
+
+**Categories:** `product`, `workflow`, `content`, `personal`
+
+**Idea-specific fields:**
+
+| Field | Values |
+|-------|--------|
+| `status` | `new`, `developing`, `decided` |
+| `category` | `product`, `workflow`, `content`, `personal` |
+| `outcome` | `null` (undecided), `[[projects/...]]` (became project), `discarded` |
+
+**Weekly Review:** Use `/synapse-review-ideas` to review active ideas and decide their fate.
+
 ## Synapse Commands
 
 Commands are Claude Code slash commands in `.claude/commands/`.
@@ -137,6 +166,18 @@ Cleans up manually-created notes to comply with AI-first standards:
 /synapse-review --all            # Review entire vault
 ```
 
+### `/synapse-review-ideas` - Weekly Idea Review
+
+Review ideas to develop them, promote them to projects, or discard them:
+- Surfaces all ideas with `status: new` or `status: developing`
+- For each idea, asks what to do: keep developing, promote to project, discard, or skip
+- When promoting, creates a new project and links it to the original idea
+
+```
+/synapse-review-ideas            # Review all active ideas
+/synapse-review-ideas product    # Review only product ideas
+```
+
 ### `/synapse-update` - Update Framework
 
 Pull the latest Synapse framework updates:
@@ -157,13 +198,28 @@ Import content from a Notion export:
 /synapse-migrate-notion ~/path/export   # Specify export path
 ```
 
+### `/synapse-publish` - Publish Framework Changes (Maintainers)
+
+Push framework improvements to the public Synapse repository:
+- Identifies changed framework files
+- Strips user-specific content
+- Creates a pull request for review
+
+### `/synapse-changelog` - Generate Changelog (Maintainers)
+
+Document framework updates with migration instructions:
+- Generates structured changelog entries
+- Prompts for migration instructions on breaking changes
+- Updates CHANGELOG.md
+
 ## Templates
 
 | Template | Use case |
 |----------|----------|
 | Daily Note | Daily planning and reflection |
 | Meeting Note | Client, sales, internal meetings |
 | Project Brief | Project planning and scope |
+| Idea | Ideas to develop and evaluate |
 | Person | Contact reference notes |
 
 ## Updating Synapse

ideas/.gitkeep

@@ -139,7 +139,9 @@ test_structural() {
     log_info "Checking command references..."
 
     # Extract all /synapse-* references from docs and check they exist
-    refs=$(grep -oh '/synapse-[a-z-]*' "${VAULT_DIR}/README.md" "${VAULT_DIR}/CLAUDE.md" 2>/dev/null | sort -u)
+    # Exclude URLs (github.com, http) to avoid false positives
+    # Use -h to suppress filename prefix (which contains /synapse-pkm path)
+    refs=$(grep -h -v 'github.com\|http' "${VAULT_DIR}/README.md" "${VAULT_DIR}/CLAUDE.md" 2>/dev/null | grep -oh '/synapse-[a-z-]*' | sort -u)
     for ref in $refs; do
         cmd_name="${ref#/}"
         if [[ -f "${VAULT_DIR}/.claude/commands/${cmd_name}.md" ]]; then

scripts/test-synapse.sh

@@ -0,0 +1,25 @@
+---
+type: idea
+status: new
+category:
+created: {{date:YYYY-MM-DD}}
+summary:
+outcome:
+tags: []
+related: []
+---
+
+## The Idea
+
+## Why It Matters
+
+## Open Questions
+
+-
+
+## Next Steps
+
+-
+
+## Notes
+