Workflow Commands
Full reference for /cm:daily, /cm:standup, /cm:weekly, and /cm:eod
Workflow Commands
Workflow commands automate your daily, weekly, and launch routines. Run one command, get a full pipeline of outputs.
/cm:daily — Daily Content Creation
What it does: Research trending topics → create content brief → draft content → review.
When to use it: Every morning if you're publishing daily content (LinkedIn posts, newsletters, blogs).
Workflow
-
Research (
/cm:research)- Finds trending topics in your niche
- Pulls from Google Trends, social signals, competitor content
- Output:
deliverables/daily/YYYY-MM-DD-research.md
-
Content Brief (
/cm:content-brief)- Picks the most relevant topic for your ICP
- Creates SEO-optimized outline
- Defines target keywords and search intent
- Output:
deliverables/daily/YYYY-MM-DD-content-brief.md
-
Draft (
/cm:write)- Writes full draft based on brief
- Uses your brand voice (from
.cm-context) - Includes examples, data, CTAs
- Output:
deliverables/daily/YYYY-MM-DD-draft.md
-
Review (
/cm:review)- Suggests edits for clarity, flow, SEO
- Flags weak arguments or missing proof
- Output:
deliverables/daily/YYYY-MM-DD-review.md
Example Output
After running /cm:daily:
deliverables/daily/
2024-03-14-research.md → 5 trending topics
2024-03-14-content-brief.md → Outline for "Why CTOs need personal brand"
2024-03-14-draft.md → Full 1200-word post
2024-03-14-review.md → Suggested edits
You get a publish-ready draft in one command.
How to Customize
Edit .cm-context to control topics:
# Content Strategy
Content Focus: Personal branding for CTOs, AI-native product development, remote team leadership
Avoid Topics: Politics, non-technical content, overly sales-y posts
Tone: Technical but accessible, founder-led, honest about challenges
The command will prioritize topics matching your focus.
/cm:standup — Morning Standup
What it does: Check metrics → review calendar → plan day's priorities.
When to use it: Start of every workday.
Workflow
-
Metrics Check (
/cm:metrics-check)- Pulls yesterday's key metrics (signups, MRR, traffic)
- Flags anomalies (spikes or drops)
- Output:
deliverables/standup/YYYY-MM-DD-metrics.md
-
Calendar Review (
/cm:calendar-review)- Lists today's meetings and commitments
- Flags conflicts or prep needed
- Output:
deliverables/standup/YYYY-MM-DD-calendar.md
-
Priority Planning (
/cm:plan-day)- Suggests top 3 priorities for the day
- Based on: metrics, calendar, ongoing projects
- Output:
deliverables/standup/YYYY-MM-DD-priorities.md
Example Output
deliverables/standup/
2024-03-14-metrics.md
- Signups: 12 (up 20% from yesterday)
- MRR: $3,400 (no change)
- Top traffic source: LinkedIn (45% of visits)
2024-03-14-calendar.md
- 10 AM: Investor call (prep deck)
- 2 PM: Customer interview (CTO at Acme Corp)
2024-03-14-priorities.md
1. Prep investor deck (meeting at 10 AM)
2. Follow up with 3 warm leads from yesterday
3. Publish LinkedIn post (draft ready from /cm:daily)
You get a focused day plan in 30 seconds.
How to Customize
Connect data sources in .cm-context:
# Data Sources
Analytics: Google Analytics (GA4)
CRM: HubSpot
Calendar: Google Calendar
The command will pull real metrics instead of placeholders.
/cm:eod — End-of-Day Review
What it does: Review what got done → capture learnings → set tomorrow's priorities.
When to use it: End of every workday.
Workflow
-
Done Today (
/cm:review-day)- Lists completed tasks
- Flags what didn't get done (and why)
- Output:
deliverables/eod/YYYY-MM-DD-done.md
-
Learnings (
/cm:capture-learnings)- What went well, what didn't
- Customer feedback, experiment results
- Output:
deliverables/eod/YYYY-MM-DD-learnings.md
-
Tomorrow's Plan (
/cm:plan-tomorrow)- Top 3 priorities for tomorrow
- Carry-over tasks from today
- Output:
deliverables/eod/YYYY-MM-DD-tomorrow.md
Example Output
deliverables/eod/
2024-03-14-done.md
✅ Published LinkedIn post (150 likes, 12 comments)
✅ Investor call (interest in seed round)
❌ Follow-up emails (pushed to tomorrow)
2024-03-14-learnings.md
- LinkedIn post on "personal brand for CTOs" performed 3x better than average
- Customer interview revealed new pain point: "We need team collaboration, not solo mode"
- Investor feedback: Wants to see more traction before committing
2024-03-14-tomorrow.md
1. Send follow-up emails to 3 warm leads
2. Update positioning to emphasize team collaboration
3. Run /cm:position to refine messaging
You get a learning loop that compounds over time.
/cm:weekly — Weekly Review
What it does: Review the week → analyze wins/losses → plan next week.
When to use it: Monday mornings (review last week, plan this week).
Workflow
-
Weekly Metrics (
/cm:metrics-weekly)- Last 7 days vs previous 7 days
- Trends: up, down, flat
- Output:
deliverables/weekly/YYYY-MM-DD-metrics.md
-
Wins & Losses (
/cm:review-week)- What worked (double down)
- What didn't (fix or drop)
- Output:
deliverables/weekly/YYYY-MM-DD-review.md
-
Next Week's Plan (
/cm:plan-week)- Top 3 goals for next week
- Key tasks to hit those goals
- Output:
deliverables/weekly/YYYY-MM-DD-plan.md
Example Output
deliverables/weekly/
2024-03-14-metrics.md
- Signups: 47 (up 12% from last week)
- MRR: $3,400 (no change)
- Top content: "Personal brand for CTOs" post (500 likes, 50 shares)
2024-03-14-review.md
Wins:
- LinkedIn content is working (3x engagement)
- 2 warm investor intros from network
Losses:
- Cold email conversion: 2% (below target of 5%)
- No new paid customers this week
2024-03-14-plan.md
Goals:
1. Close 2 paid customers
2. Refine cold email copy (current version isn't working)
3. Publish 5 LinkedIn posts
Key Tasks:
- Re-run /cm:cold-email with updated ICP insights
- Follow up with 10 warm leads
- Write LinkedIn content on "team collaboration" (new pain point)
You get a strategic review that keeps you focused on what matters.
How to Adapt Workflow Commands
All workflow commands use .cm-context + deliverables/.
To adapt /cm:daily for your workflow:
- Update
.cm-contextwith your content focus - Run
/cm:daily - If one piece is off (e.g., draft tone), edit
.cm-contextand re-run just/cm:write
To adapt /cm:standup for your data:
- Connect your analytics, CRM, calendar in
.cm-context - Run
/cm:standup - Review priorities, adjust as needed
To adapt /cm:weekly for your metrics:
- Define your key metrics in
.cm-context:# Key Metrics North Star: Weekly signups Supporting Metrics: MRR, CAC, content engagement - Run
/cm:weekly - The report will focus on those metrics
Next Steps
- Commands Overview — when to use commands vs skills
- Skills Overview — see individual skills these commands use
- Configuration Guide — connect your data sources