Taskmark
Product memory for agent work
Local markdown boards that keep epics, stories, and tasks in sync with Cursor — so planning survives the chat.
Example session: plan an epic or task, implement a leaf without committing, then commit linked projects explicitly.
Why Taskmark
Agents forget. Boards remember.
Chat threads are a terrible backlog. Taskmark keeps product work as hierarchical markdown the agent already knows how to open, update, and complete — with sizes, points, and billable work logs that stay honest.
You get a durable trail of decisions and delivery without bolting on another SaaS board that drifts from what actually shipped.
Epic · E-MM-4b9b509e
Website landing
Story · S-MM-60c97eed
Hero + Start now
Task · T-MM-f84c1351
Console typing demo
Built with Taskmark
We ship Taskmark on a Taskmark board
Every epic, story, and task behind this product lives on the same kind of markdown board you would keep in your own workspace. The hosted board is the real backlog we use to plan, implement, and commit — not a mock screenshot.
Open it to see a working example of the UI, the hierarchy, and how work looks after months of agent sessions.
Features
Work that agents can remember — and teams can see
A markdown board humans and agents share: context, delivery, and release notes without a second tracker.
Product memory for agents
Chat is not a backlog. The board is the product context agents read and update — so planning survives the session.
Agents report their own work
You cannot pre-write every task in an agentic project. As features land, the agent records what it actually did, so the board stays true without a human tax.
Everyone on one board
People and agents write the same leaves. Status, contributors, and activity roll up so you can see who shipped what.
Changelogs users can read
Done work becomes Keep a Changelog notes for each version — user-facing outcomes, not ticket IDs.
Priorities and points that steer delivery
Priority plus a fixed story-point scale sequences work and shows how fast the team is moving — without inventing estimates from the past.
Hierarchical boards
Epics, stories, tasks, and bugs as markdown — nested product memory the agent can read and update, without a generated dashboard.
MIT-licensed. Cursor-first. Local by default.
Taskmark ships as a Cursor plugin marketplace package — skills, rules, and scripts that live next to your repos. Boards stay on disk in git; there is no hosted backlog to sync against. IDE support beyond Cursor is intentionally out of scope for now.
Read the docs
Install the plugin, initialize a board, and learn the slash commands that keep work sessions billable and honest.
Become a contributor
Ideas, fixes, and new skills are welcome. Open an issue or pull request on GitHub — the plugin package and board conventions live in the public repos.
Prefer to talk first? Send a message.
Contact
Questions about Taskmark, partnerships, or the board workflow — send a note and we will get back to you.