/code @devintern/pm DevIntern + Markdown
Skip the PM account entirely. DevIntern reads and writes local Markdown task files in your repo, ideal for solo operators, spikes, and teams that want specs versioned next to code.
How it works
What DevIntern does with Markdown
Each product path keeps Markdown as the handoff surface. No rip-and-replace, no new dashboard.
/pm Write Markdown task files
- 1 Set TASK_TRACKER=markdown and point MARKDOWN_TASKS_DIR at your tasks folder.
- 2 Draft a spec interactively or from a prompt.
- 3 Save the .md file into your repo for Code to pick up.
/code Implement Markdown tasks
- 1 Point devintern at a .md file path.
- 2 Agent reads the spec from disk and gathers repo context.
- 3 Implements, commits, and opens a PR against your branch.
Capabilities
Built for real Markdown workflows
No Jira, Linear, or SaaS PM account required
Task specs versioned alongside code in git
Works offline once configured
Fastest path for solo trials and internal spikes
Same agent harness options as tracker-backed runs
Get connected
Setup guides and configuration
Credentials stay in project-local .env files. DevIntern runs on your machine or server, not a shared implementation cloud.
FAQ
Common questions about Markdown
Where should Markdown tasks live?
Configure MARKDOWN_TASKS_DIR in .env relative to your project root. Many teams use a tasks/ or docs/tasks/ directory committed to the repo.
Can Markdown tasks sync to a tracker later?
Yes. Teams often start with Markdown for pilots, then move to Jira or Linear once the workflow is proven.
Try DevIntern with Markdown
Connect Markdown, run your first workflow, and keep the trackers, repos, and reviewers your team already trusts.
14-day trial · perpetual license · BYO model keys