Stories & Workflow
Stories are the core unit of work in DolphinQ — created from chat, organized by component, and tracked through a simple workflow.
What is a Story?
A story represents a single deliverable unit of work. Each story has:
- Title & description — what needs to be done
- Status — Pending, In Progress, Blocked, Completed, Cancelled
- Priority — Critical, Highest, High, Medium, Low, Lowest
- Component — which part of the system it belongs to
- Assignee — who is responsible
- Dates — planned start and due dates, plus actual start and end, stamped automatically as the status changes
Creating Stories
Stories can be created in two ways:
From Chat
Tell your AI what you need. It calls DolphinQ's MCP tools to create stories with the right component, priority, and dependencies — all from a single conversation.
Batch Creation
Describe a larger goal or feature. Your AI decomposes it into multiple stories, wires dependencies, and creates them all at once using create_stories_batch.
Dependencies
Stories can depend on other stories. Dependencies define execution order and are used to:
- Build the Dependency DAG — a visual graph of what blocks what
- Surface the critical path — the longest chain of dependent work
- Identify blockers — stories that are holding up downstream work
Comments
Add context to stories with tagged comments — from the story view, or by your AI with add_comment. Tags: LOG, BUG, FIX, TASK, UPDATE, QUESTION, BLOCKER, DONE, and VERIFIED. Reply to a comment to start a thread.
- Formatting — your AI writes comments in markdown (headings, lists, bold, and fenced code blocks), converted on save. Code is shown in a monospace block.
- Edit & delete — you can edit or delete your own comments; workspace owners and admins can edit or delete any comment. Edited comments show (edited).
- Deleted comments show "Comment deleted" but keep their number and replies, so references like "see comment #30" stay valid.
- Empty comments are rejected.