Taskmark documentation

Taskmark is a Cursor plugin that keeps product work as hierarchical markdown the agent can read and update. The board is product memory — not a separate SaaS backlog that drifts from what shipped.

How docs are organized

• Setup — Install the Cursor plugin and create your first board.
• Commands — Slash commands: init, verify, plan, save, save-do, plan-do, do, shelf, changelog, version, reportme, and commit.
• Folder structure — Single-repo vs multi-repo boards and file conventions.
• File specification — Epic, story, task, and bug markdown shape for the UI and manual edits.
• Sizing & points — Static t-shirt sizes and points; parent rollups in the UI.
• Workflows — Overall tree, leaf-only writes, work logs, and when to plan, save, save-do, plan-do, report, or commit.

Suggested path

1. Setup — install the plugin and initialize a board
2. Commands — plan, implement, shelve, and commit work
3. Folder structure — know where files live
4. Workflows — Overall tree, leaf-only writes, actuals, and multi-repo

User-facing slash commands are /tkmd-init, /tkmd-verify, /tkmd-plan, /tkmd-save, /tkmd-save-do, /tkmd-plan-do, /tkmd-do, /tkmd-shelf, /tkmd-changelog, /tkmd-version, /tkmd-reportme, and /tkmd-commit. Use /tkmd-init for a first board and /tkmd-verify to migrate an older board to the current layout. Use /tkmd-save after Cursor Plan mode, /tkmd-save-do to save that plan and implement the new items immediately, /tkmd-plan for free-form prose, and /tkmd-plan-do when you want to plan from prose and implement the new items immediately. /tkmd-changelog and /tkmd-version write board CHANGELOG.md (and /tkmd-version the same SemVer on every linked product), not a README changelog. /tkmd-reportme writes a personal, gitignored report of your done work since the last report. /tkmd-commit is the only command that commits.