Commands Overview
Workflow commands that chain multiple skills together
Commands Overview
Commands are multi-skill workflows that run several skills in sequence. Instead of running /cm:position, /cm:headlines, /cm:landing-page separately, you can run one command that does all three.
Commands vs Skills
Skills = Individual tasks
/cm:position→ writes positioning.md/cm:headlines→ writes headlines.md/cm:landing-page→ writes landing-page-copy.md
Commands = Multi-skill workflows
/cm:daily→ runs research + content creation + review/cm:standup→ morning routine (check metrics + plan day)/cm:weekly→ weekly review (wins, losses, next week's plan)
When to Use Commands vs Individual Skills
Use commands when:
- You're following a regular workflow (daily standup, weekly review)
- You want to run multiple related skills at once
- You're new and want a guided flow
Use individual skills when:
- You need one specific output (just headlines, not the full landing page)
- You're iterating on one piece (re-running
/cm:headlinesafter feedback) - You want more control over the sequence
Available Commands
Daily Workflows
| Command | What It Does | When to Use |
|---------|-------------|-------------|
| /cm:daily | Research + content creation + review | Every morning |
| /cm:standup | Check metrics + plan day | Start of workday |
| /cm:eod | End-of-day review + tomorrow's priorities | End of workday |
Weekly Workflows
| Command | What It Does | When to Use |
|---------|-------------|-------------|
| /cm:weekly | Weekly review + next week's plan | Monday mornings |
Launch Workflows
| Command | What It Does | When to Use |
|---------|-------------|-------------|
| /cm:launch-week | Full launch prep (positioning → copy → outreach → ads) | 1 week before launch |
How Commands Chain Skills Together
Commands run skills in dependency order. Each skill needs the outputs from previous skills.
Example: /cm:daily
/cm:research→ finds trending topics in your niche/cm:content-brief→ creates outline for today's content/cm:write→ drafts the content/cm:review→ suggests edits
Output:
deliverables/daily/2024-03-14-research.mddeliverables/daily/2024-03-14-content-brief.mddeliverables/daily/2024-03-14-draft.mddeliverables/daily/2024-03-14-review.md
You get a full content pipeline in one command.
Example: /cm:launch-week
/cm:position→ positioning.md/cm:icp-research→ icp-research.md/cm:headlines→ headlines.md/cm:landing-page→ landing-page-copy.md/cm:cold-email→ cold-email-sequence.md/cm:ads→ ad-copy.md/cm:launch-plan→ launch-plan.md
Output: Everything you need to launch, in dependency order.
Customizing Command Output
Commands use your .cm-context just like individual skills. To customize:
- Update
.cm-contextwith your specifics - Run the command
- If you don't like one piece, re-run that individual skill with refinements
Example:
You run /cm:launch-week but the headlines are off.
Instead of re-running the whole command:
- Edit
.cm-contextto add more customer pain language - Re-run just
/cm:headlines - The new headlines.md overwrites the old one
The rest of the deliverables stay the same.
How Commands Relate to Your .cm-context
Commands pull all context from .cm-context:
- Company info
- ICP details
- Positioning
- Traction (if any)
- GTM strategy
The more detail in .cm-context, the better the command output.
Minimal context = generic output:
Company: MyStartup
Product: A tool for teams
ICP: Busy professionals
Rich context = tailored output:
Company: AuthorityMax
Product: AI-native personal branding workspace for technical founders
ICP: CTOs at B2B SaaS (50-200 people) who need to build personal brand for hiring and fundraising
Pain: Writing LinkedIn posts feels like a chore. Generic AI sounds bland. Ghostwriters are slow and expensive.
Differentiator: Only tool that trains on YOUR past writing to match your voice at scale
The second one gives commands much more to work with.
Next Steps
- Workflow Commands Reference — full breakdown of each command
- Configuration Guide — write better
.cm-context - Skills Overview — see individual skills