Manage Work with Kanban
Kanban is a document inside a project that turns next actions into executable work. It records owners, priority, due dates, completion criteria, and review flow while linking requirements, results, and decisions from the same project.
Board scope
A Kanban board belongs to one project; it is not a workspace-wide task list.
Show me the Kanban boards in [project name] in [workspace name].
When names overlap, confirm the workspace, project, and board.
Columns and cards
A common flow is:
- To do
- In progress
- In review
- Done
Blocked work can be marked separately and resumed when the blocker is removed. Cards can be reordered within columns.
Card types include Task, Review, Bug, and Decision.
A card can contain a title, description, type, priority, assignee, requester, reviewer, watchers, blocker responders, due date, completion criteria, linked documents, external links, comments, questions, and activity.
Keep long requirements in a linked project document instead of copying everything into the card.
Create work from a document
Turn the next actions in Project Context into Kanban cards.
Add type, priority, due date, and completion criteria when needed.
Create this as a Review card and define three completion criteria.
Link requirements and results
A card can link an AiNecto document or external URL with a role:
- Requirement
- Reference
- Deliverable
- Review Result
- Decision
- Test Evidence
When linking another project's document, confirm its location and permissions.
Watchers and blocker responders
Watchers receive card activity that they need to follow. Blocker responders are people who can provide an answer or action when work is blocked. Add only people who have a real follow-up responsibility.
Assignment and acceptance
A person assigned work can accept or decline it. Assignment changes someone else's work and notifications, so confirm the person and result before an Agent performs it. Do not treat unaccepted work as actively in progress.
If declined, record the reason and reassign or adjust the scope. Work assigned to yourself may begin in an accepted state.
Progress and review
After accepting a card, start the work, check each completion criterion, and link results and evidence.
In [project name] in [workspace name], show my in-progress work and due dates.
Read this card's requirements and list the next actions needed to meet its completion criteria.
When results are ready, request review. The reviewer can approve and complete the work or request changes and return it to progress. Record review feedback in comments and update the result document when its body must change.
Block, resume, complete, and reopen
When work cannot proceed, record the blocker, required decision or dependency, and the person who can respond. Unblock the card after the issue is resolved.
Simple work that does not require review can be completed directly. If a problem appears later, reopen the card with the reason. Archive completed cards that no longer need to remain on the active board, and restore them when needed.
Comments, questions, mentions, activity, and notifications
Kanban cards support the same comments, questions, replies, and mentions as documents. Card creation, changes, assignment, acceptance, review, approval, blocking, and discussion appear in project activity and may create notifications or work items.
Separate this board's recent activity from the work I still need to handle.
Use an Agent to inspect a board
Show me the in-progress work in [project name] in [workspace name].
Separate work assigned to me from work I need to review.
Show the reason each blocked card is blocked and who needs to respond.
If several cards match, confirm the workspace, project, board, and state instead of guessing from the title.
Keep Kanban and documents aligned
Keep execution status in Kanban, confirmed decisions and the current standard in Markdown, deliverables in linked documents or URLs, and review or test evidence on the card and result document.
Changing a card state does not automatically update the project's source of truth.
Work is complete when the correct card was used, completion criteria are satisfied, results and evidence are linked, required review is finished, changed decisions are reflected in Markdown, and follow-up work remains visible.
Next, go to Document Types to choose the right deliverable.