Create and edit a project doc

Write project requirements, plans, and decisions in documents that stay close to the work.

Before you start

Select a project and open Docs. Use a document for information that benefits from more structure than a short task description.

A project document keeps structured requirements alongside status, labels, design, and implementation actions.

Step by step

1. Choose New in the Docs panel. Start with Blank Doc or a suitable template, such as Feature / PRD, Technical Design, Research Spike, or Decision Record.

2. Give the document a recognizable title. Use the template’s sections as prompts, then replace example or placeholder text with the actual project information.

3. Write the outcome, scope, and important constraints. For a feature document, include how a reader can tell whether the result is correct.

4. Use headings and short sections to make the document easy to scan. Keep unresolved questions explicit instead of leaving contradictory instructions in the main requirement.

5. Return to the document from the Docs list to review it. Use its status and labels to organize it where those controls are available.

6. For a structure you expect to reuse, open the document’s menu and choose Save as template. Give the template a clear name so it can be selected for a future document.

What to expect

The project has a readable source of requirements or decisions that you can revisit and use when preparing agent work.

Troubleshooting and useful details

A template provides structure; it does not know your project’s requirements. Check that copied text is relevant before handing it to an agent. If Choro reports a saving error, resolve that error before using the document as an implementation source. A saved template is a reusable snapshot, so later edits to the original document are not a reason to assume the template has changed.