Project docs with approvals
Ask the COO to create or update durable project documentation while every write action stays explicit and reviewable.
Example request
Draft a launch checklist from the current project brief and recent missions, then propose it as a project doc for review.
- Memory
- Docs
- Control
- Approval
- Scope
- Project
Product, engineering, research, and internal teams
Project memory improves over time without silent changes to important docs.
Knowledge work
How it works
From request to result
- 1
Point at the source
Ask the COO to use a project brief, existing docs, mission comments, uploaded files, or repository context.
- 2
Generate the draft
Kibo prepares a new doc or edit proposal with clear structure and the relevant project details.
- 3
Approve the write
The doc is only created or updated after a human confirms the proposed change.
- 4
Keep it findable
The resulting reference material lives in the project docs area and can guide future missions and routines.
Kibo capabilities
- Project doc proposals
- Markdown editing
- AI-assisted doc updates
- Project context search
Typical outputs
- Project brief updates
- Launch checklists
- Research summaries
- Reusable internal docs
What stays visible
- Proposed changes before write
- Source context
- Doc hierarchy
- Exportable document output
Related workflows