grow-note

name	grow-note
description	Promote daily thoughts into real assets. Transform scattered daily notes, fleeting thoughts, and rough ideas into structured, actionable documents. Use when a thought has matured enough to become a proper article, plan, or reference document.
command	grow-note
metadata	{"author":"syner","version":"0.3.0"}
tools	["Glob","Read","Write"]

Grow Note

You detect growth opportunities and execute the right type of evolution.

Purpose

Growth isn't always "make it bigger." Sometimes it's:

• Graduate — Rough thought → Polished document
• Fragment — Dense file → Breathable structure
• Discover — Hidden potential → Visible opportunities

This skill orchestrates all three.

Ideas Scope Integration

Queries: Expected output from agent lead Purpose: Determine what document format to create when graduating Benefit: In notes creates personal plans/articles, in dev creates technical specs

Decision Flow

Input received
  ↓
Has --scan flag?
  ├─ Yes → Scout Evolution mode
  │         (Find opportunities across vaults)
  │
  └─ No → Analyze target
            ↓
          Is it a .md file path?
            ├─ Yes → Analyze density
            │         ├─ High → Document → Structure
            │         └─ Low → Thought → Document
            │
            └─ No (phrase/topic) → Thought → Document

Modes

Each mode has detailed reference documentation:

1. Scout Evolution (--scan)

Reference: references/scout-evolution.md

Proactively scan vaults for evolution opportunities.

Triggers:

• --scan flag present
• No specific file target

Output: Prioritized list of files ready to evolve

2. Document → Structure

Reference: references/document-to-structure.md

Fragment dense documents into folder structures.

Triggers:

• Input is .md file path
• Density analysis shows 3+ competing concepts
• File > 200 lines with clear boundaries

Output: Proposed folder structure + fragment plan

3. Thought → Document

Reference: references/thought-to-document.md

Graduate raw thoughts into polished documents.

Triggers:

• Input is phrase/topic
• Input is daily note or rough draft
• Density analysis shows single cohesive idea

Output: Drafted document with suggested placement

Usage

# Scout for opportunities
/grow-note --scan
/grow-note --scan .syner/vaults/design

# Transform dense document
/grow-note .syner/vaults/design/syner/components.md

# Graduate a thought
/grow-note "my thoughts on async communication"
/grow-note daily/2024-03-09.md

# Force specific format
/grow-note "async notes" --format article

For detailed help: Read help.md in this skill directory

Execution Steps

1. Parse Input

Extract:

• Target (file, topic, or none if scanning)
• Flags (--scan, --format, --path, --verbose, --stats)
• Scope (specific path or full vault)

2. Read References

Based on mode detected, read the appropriate reference:

Read references/scout-evolution.md        # If --scan
Read references/document-to-structure.md  # If high density file
Read references/thought-to-document.md    # If thought/topic

3. Execute Mode

Follow the process defined in the reference document.

4. Output Result

Use the output template from the reference, formatted consistently.

Context Loading

Load proportionally:

• Scout mode: Full vault scan (.syner/vaults/**/*.md)
• Transform mode: Single file + related notes
• Graduate mode: Topic search across vaults

Always read index.md files first for orientation.

Boundaries

This skill operates within /syner-boundaries:

Boundary	Application
Suggest, Don't Enforce	Propose structure/format, confirm before executing
Concrete Output	Deliver drafts and plans, not vague suggestions
Notes Are Context	Read for understanding, preserve user's voice
Proportional Loading	Load only what the mode requires

Self-check: Before outputting, verify:

• Mode detection was correct
• References were consulted
• Output is actionable and concrete
• User's voice is preserved (not templatized)

Meta-Note

This skill practices what it preaches:

grow-note/
  ├── SKILL.md                      ← You are here (orchestrator)
  ├── help.md                       ← User-facing documentation
  └── references/                   ← Detailed mode specifications
      ├── scout-evolution.md
      ├── document-to-structure.md
      └── thought-to-document.md

It evolved from a single file using its own methodology. This structure is the case study for document → structure transformation.

---

Related skills: /track-idea, /find-links, /find-ideas