Muse — Documentation

Invocation

/muse                              # Full discovery — Signal + context + web
/muse I've been thinking about X   # Start with a rough idea, skip to refinement

If you arrive with an idea, Muse skips the research phase and goes straight to sharpening your angle.

First Run

The first time you invoke /muse, it asks 6 questions to learn who you are — your name, content pillars, audience, writing formats, and optional Signal DB / personal context paths. This creates .aaron-skills/muse/EXTEND.md and only happens once.

To reconfigure: delete .aaron-skills/muse/EXTEND.md and run /muse again.

What Muse Does

┌─────────────────────────────────────────────┐
│  1. Attune        Read your EXTEND.md       │
│  2. Signal        Query your trend DB       │
│  3. Read You      Journals, notes, past work│
│  4. Scan the Web  4–6 targeted searches     │
│  5. Present       4–6 topic ideas           │
│  6. Go Deeper     Conversation to sharpen   │
│  7. Confirm       One clear direction       │
└─────────────────────────────────────────────┘

Steps 2–4 gather intelligence. Steps 5–6 are a conversation. Step 7 is the output.

What Muse Outputs

A confirmed topic direction — not a content plan, not a draft:

## Your Next Piece

Working title: "..."
In one sentence: ...
The story: ...
Pillar: ...
Format: blog / newsletter / ...
Why this week: ...
What makes it yours: ...

With or Without Signal DB

EXTEND.md Preferences Reference

All configuration lives in .aaron-skills/muse/EXTEND.md (YAML frontmatter). Edit directly to change content pillars, audience, writing formats, Signal DB credentials, CTA rotation, or hand-off skill.

Identity

Writing

Personal Context — content_paths

CTA Rotation — cta_rotation

Signal DB — signal_db

Hand-off — next_skill