Project Documents: Creation and Upkeep
Besides the documents you upload, the agent creates and maintains project working documents — the ones management stands on: charter, scope, requirements, specification, plans, and registers. This guide covers how they are created, how you review them, and how they live alongside the project.
Which documents the agent maintains
Each document has its own command — the agent creates a document only through that command, never "free-form":
| Document | Command | What it holds |
|---|---|---|
| Charter | /initiate | Purpose, objectives, success criteria, high-level In/Out |
| Scope | /scope | Boundaries of the approved scope: what is in, what is out, assumptions |
| BRD (business requirements) | /requirements | The living requirements document: functionality, acceptance criteria |
| Specification | /specify | Requirements detailed to implementation level |
| Contract / SOW | /contract-review | Delivery contract analysis: obligations, deadlines, risks |
| Risk register | /risks | Identified risks, assessment, response measures |
| Estimation method | /estimate | How the project estimates effort |
| Plans (sprint / release / Gantt) | /plan | Period commitments, baselines |
| Report format | /report-format | The status report template |
| Reports | /report | Completed status reports for periods |
The list is fixed: the agent does not invent new document types — it works with this set and with your uploaded files.
How a document is created
The typical cycle is the same for all documents:
- Request. You invoke a command (e.g.,
/scope) — or the agent offers it when the time comes. - Draft. The agent gathers material from the tracker, knowledge base, uploaded documents, and the conversation, and prepares the document in the working area.
- Review. Changes in the document are marked as blocks: additions are highlighted, deletions are struck through, with "Accept" / "Reject" buttons beside them. Any part can be edited by hand.
- Save. The document is saved in the format you need (Markdown or ADF) — into the session or straight into the project.
More on the editor mechanics — in the Collaborative editors section.
How documents live afterwards
Working documents are "living": the agent updates them as the project evolves, and always through review. Examples:
- BRD grows as requirements are refined: new requirements are added as blocks, outdated ones are marked.
- Risk register grows: new risks appear through
/risks, response measures through/risk-mitigate; you accept each change. - Scope does not change "silently": any scope growth goes through a check (see Scope control).
Registry and "not applicable"
The agent keeps a registry of working documents: what has been created, what is missing, and what does not apply. If the project is internal and there is no delivery contract, the "contract" document is marked "not applicable" — and the agent stops offering to create it.
A session draft and a project document are different levels. When a document is ready to be used across sessions, the agent proposes promoting it to the project — you confirm the promotion.
Where to continue
- Project initiation — how the first documents are created: charter, contract analysis, scope.
- Gathering and elaborating requirements — how the BRD lives.
- Working with the document base — the documents you upload.