What ProjectFrame contributes
ProjectFrame is the structured plan catalog behind Kanbai's template work. A template provides an ordered starting task set; the project you create is your team's working instance.
Open a template and read its description, tasks and source-guide link. Select it because its work fits your engagement, not simply because the title sounds similar.
Adapt it to the engagement
A source guide explains a template's origin. It does not certify that the resulting plan fits a particular client. Your team reviews the plan and decides what completion requires.
- Check the intended outcome and read the existing task descriptions.
- Identify missing deliverables, approval steps and dependencies before kickoff.
- When you have project access, create a project using the selected template and review the resulting tasks, dates and owners.
- Add or edit work in the project as the engagement requires. Keep the source context so later reviewers understand the starting point.
Plan and document are different objects
A project template creates a task set. A scope statement or statement of work describes the engagement. Review both together so the documents and work agree.
Use the existing glossary when dependency or document terminology is unfamiliar.
Choose a project documentUnderstand finish-to-start dependencies
Related development status
| 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 |
| 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 |