How to read this page
Kanbai is being developed as a connected place for project plans, documents, people and AI agents. This table separates that direction from the current experience.
Dates appear only when development timing has been committed. “Not yet scheduled” means a delivery date has not been set.
Features and development
Scroll across the table to read all five columns. Keyboard users can focus the table and use the arrow keys.
| Feature | Vision | Current state | Gap | Planned timing |
|---|---|---|---|---|
| Templates and ProjectFrame | A fitting starting plan with useful tasks and clear completion requirements. | Public templates show an ordered task set and source context; permitted users can start project work from a template. | Broader reviewed plan coverage and deeper task-by-task adaptation. | Not yet scheduled |
| Project workspaces | Connected planning and delivery for the intended team. | Authorized project users can work with tasks, dependencies, views and saved project documents. | Self-service project access and project-scoped invitations are not part of the current entry path. | Not yet scheduled |
| Planning documents | Project plans and client paperwork that agree. | Standalone document generators create Markdown from your fields; authorized project instruments have a separate save/export path. | More connected review across the plan and its documents. | Not yet scheduled |
| Drafts and return | Return to the exact work you reviewed, across supported contexts. | Standalone text drafts use this browser's local storage. Markdown downloads are portable copies; project records require an authorized project save. | Account-based cross-device draft saving and browser restore of risk-table rows are not connected. | Not yet scheduled |
| Planning tools | Useful analytical support beside the project work. | Definition, estimate, RACI and risk tools use the inputs you supply and explain their approach. | The tools are used separately; automatic assembly into one project workflow is not connected. | Not yet scheduled |
| Completion and review | Work is complete only after its requirements have been checked. | Task statuses and completion reports record what a person or agent says is done. | An independent task-verification event and complete review history. | Not yet scheduled |
| Sharing | Clients see the intended work with appropriate access. | Markdown exports and available item-specific share links support deliberate sharing. | Broader project-level client sharing and collaboration. | Not yet scheduled |
| Application and agent interfaces | People and authorized agents work from consistent project information. | Public catalog discovery and read-only data are distinct from authorized private operations. | Public catalog reads and authorized project operations are separate; automatic cross-application workflows are not provided here. | Not yet scheduled |
| Shared membership | One Bicycle membership includes Kanbai while private project access stays scoped. | The current beta uses the application's account and project-permission rules. | A Bicycle membership is not yet recognized when signing into Kanbai. | Not yet scheduled |
| Documentation and support | Readers can understand the product, complete a task and recover from a problem. | Documentation, questions, universal support articles and an existing contact form are connected. | Deeper task coverage and continuing review as the application changes. | Ongoing; no fixed completion date |