task-management

You can manage software epics and stories using Markdown files by storing them in a local .dots/ repository. Markdown bodies hold context and acceptance criteria, while YAML frontmatter tracks status, priority, and hierarchical relationships.

Tracking blocking dependencies for local development tasks is done by linking blockers within the Markdown task files. You can query ready-to-work items and visualize blocked progress across your project using the dot CLI.

Priority-driven work is structured by assigning priority values in YAML frontmatter. You can create epics, break them into stories, and use CLI commands like dot ready to query available tasks based on their priority.

Yes, the dot CLI must be installed locally to organize project work in Markdown. It orchestrates the local .dots/ repository, handling task creation, hierarchical linking, and status updates for your development workflow.

Markdown task management supports both personal productivity and team SDLC workflows. It models tasks hierarchically from epics to stories, allowing developers to track blockers and update task status locally.

Initialize a workspace with dot init, then add an epic using dot add with a priority flag. Capture the returned epic ID and pass it to subsequent dot add commands with the parent flag to generate linked stories.