Use Cases

Last updated February 24, 2026

AutoMD is a blank canvas — a markdown file can be anything. Here are real use cases that go beyond the obvious kanban board.

Solo developer: personal task system

Keep a single todo.md as your daily driver:

# Today

- [ ] Fix pagination bug in /api/users #bug priority:high
- [ ] Review PR #142 from @bob est:30m

# This Week

- [ ] Write tests for search module #testing est:4h
- [ ] Update deployment docs #docs priority:low

# Backlog

- [ ] Investigate Redis caching for sessions #performance
- [ ] Refactor error handling middleware #tech-debt

Ask your agent each morning:

Look at my todo.md. What's overdue? Move anything from "This Week"
to "Today" if it's due today. Suggest a priority order for my day.

Startup: sprint planning with AI

Use the agent as your sprint planning copilot:

Here's what the team accomplished last sprint (see sprint-11.md).
Create sprint-12.md and:
1. Carry over anything that wasn't completed
2. Pull the top 5 items from product-roadmap.md Backlog
3. Balance the load — no one should have more than 20 story points
4. Flag any tasks that depend on each other

Engineering team: incident tracking

When things break, create an incident board fast:

Create incident-2026-02-24.md with columns:
Timeline, Root Cause, Mitigation, Follow-up.

Add to Timeline:
- "14:32 — Alerts fired for API latency >2s" @on-call #incident priority:high
- "14:35 — Identified: database connection pool exhausted" @alice #incident
- "14:41 — Mitigation: increased pool size, restarted service" @alice #incident

Add to Follow-up:
- "Add connection pool monitoring" @bob #monitoring priority:high due:friday
- "Implement circuit breaker for DB connections" @charlie #backend est:4h
- "Write postmortem" @alice #docs due:next-monday

Product manager: roadmap tracking

A roadmap board gives you high-level visibility:

# Now (Q1 2026)

- [ ] User search with filters @team #feature priority:high
- [ ] MCP v2 protocol @team #feature priority:high
- [ ] Self-hosted cloud setup wizard @team #feature priority:medium

# Next (Q2 2026)

- [ ] Real-time collaboration @team #feature
- [ ] Custom fields for task metadata @team #feature
- [ ] Webhook integrations @team #feature

# Later

- [ ] Mobile app @team #feature
- [ ] Marketplace for board templates @team #feature
- [ ] Enterprise SSO @team #feature

Weekly check-in prompt:

Compare product-roadmap.md with our sprint boards. Are we on track
for Q1 goals? Which features are at risk? Summarize in a format I
can share with stakeholders.

Content team: editorial calendar

Track blog posts, docs, and content production:

# Drafting

- [ ] "Getting Started with AutoMD" blog post @alice #blog priority:high due:march-1 est:4h
- [ ] Update quickstart guide for v2 @bob #docs est:2h

# Review

- [ ] "Why Markdown for Project Management" @alice #blog
  > Draft in Google Docs. Needs technical review from @charlie.

# Published

- [x] "Announcing AutoMD Cloud" @alice #blog
  > Published 2026-02-20. 2.4k views first week.

Open source maintainer: issue triage

Mirror your GitHub issues into a triage board:

Scan the last 10 open issues on our GitHub repo. Create a board
called triage-feb.md with columns: New, Needs Info, Accepted, Won't Fix.
Add each issue as a task with the reporter's name, labels, and
a one-line summary. Prioritize anything with more than 5 thumbs-up.

Freelancer: client project tracking

One board per client, all in one place:

# Active

- [ ] Homepage redesign @me #design priority:high due:march-5 est:12h
- [ ] Logo variations (3 options) @me #design est:4h

# Waiting on Client

- [ ] Approve color palette @client #design
  > Sent Feb 20. Follow up if no response by Feb 27.

# Invoiced

- [x] Brand guidelines PDF @me #design est:8h
  > Invoiced $1,200 on Feb 18. Payment pending.

One pattern, infinite uses

The power of AutoMD is that every use case above is the same thing: a markdown file with headings and checkboxes. You don’t need different tools for roadmaps, incidents, and meeting notes — just different column names.

What should you build first?

If you’re just getting started, pick one use case and commit to it for a week:

  1. Solo devs — start with todo.md as your daily driver
  2. Teams — start with a single sprint board
  3. Managers — start with a decision log

Once it clicks, you’ll naturally expand to more boards. The key is starting simple.