Skip to main content
ProductsPricingDocsBlogSign in한국어Get started

Markdown Documents

Markdown is the default document for a project's current standard. An Agent reads it before starting work, and reviewed results return to it as durable project memory.

Good uses​

  • Project goals and scope
  • Requirements and policies
  • Confirmed decisions and evidence
  • Open questions
  • Meeting and review results
  • Operating procedures
  • Current results and next actions
  • Locations of related deliverables

Create a Markdown document​

Use the web app or ask an Agent.

Create a Markdown document named Project Context in [project name].

Include the workspace and project when the destination is ambiguous. If a document already serves the same purpose, inspect and update it instead of creating a duplicate.

Read the Project Context document and separate its goals, decisions, open questions, and next actions.

Search covers titles and bodies. If several candidates appear, compare their project, folder, and last change.

Update versus append​

Update the relevant sections when the current standard changes.

Keep everything that is still valid and update the confirmed decisions, open questions, and next actions.

Append when you are adding a dated record that should not replace existing content.

Do not change the existing body. Append today's review result at the end.

Do not keep appending to a current-state document until old decisions look current.

Generation assistance​

An Agent can generate a Markdown draft from existing documents and supplied context. Identify the target document clearly and review the result before treating it as the current standard.

Versions and restore​

Saved changes appear as versions that can be read and restored. Compare the current and target versions before restoration so later valid decisions are not lost.

Comments and review​

Use a comment for feedback and a question when an answer is required. Apply agreed outcomes to the body instead of leaving them only in the discussion.

A good Markdown source of truth​

  • Shows the current standard near the beginning
  • Separates facts, decisions, questions, and actions
  • Points to evidence and related deliverables
  • Does not present obsolete guidance as current
  • Can be understood by the next person or Agent without the previous conversation

If the work needs to be reviewed visually in a browser, continue to HTML Documents.