Project context

Editorial feedback that understands the project behind the draft.

A draft rarely exists in isolation. A product announcement may depend on a current feature specification; a landing page may need to reflect approved positioning; a documentation change may need to keep terminology used elsewhere.

What this looks like in Studio

  • Group drafts into an optional named project with its own editorial settings. Each draft keeps its own writing type, so one project can hold documentation, release notes and a launch post.
  • Upload reference files — Markdown, plain text, PDF, Word or PowerPoint. Studio keeps the extracted text and quoted notes for later reviews and discards the original file.
  • When an uploaded source explicitly states a durable convention, such as a preferred term, it can become a source-quoted writing-guidance note for the project.
  • Project context informs the review but never overrides the editorial method or your draft, and you still decide on every suggestion.

If you use the open-source Second Read skill in your own agent environment, its knowledge-base reference describes consulting focused notes in Markdown repositories, Obsidian vaults or Notion where that environment already has authorised access. The skill does not create those connections.

How context should be used

Start with the draft and its immediate context

The review begins with the target draft, its brief and a narrow set of relevant sources. It does not ingest an entire workspace merely because material is available.

Prefer authoritative, current material

A signed-off product reference may support a claim. An old brainstorm is context, not an approved rule. When sources conflict, the review should expose the conflict rather than silently choose the convenient version.

Keep evidence types separate

A company website establishes its stated positioning. A repository file can corroborate source text or configuration. Observing runtime behaviour requires an authorised test. These are not interchangeable.

Respect access boundaries

Only material you have supplied or authorised is used. If a source is unavailable, the review should say so rather than guess.

Synthetic example · the draft

Worked example

A draft says a feature is generally available. A current release note says it is in beta, while an older marketing page uses the broader claim.

What a useful review does

It flags the conflict, names both sources and asks which one is authoritative if the current status cannot be established. Supplied context reveals mismatches with your own material; it does not make that material independently true.

Related reading

Try it on your own terms

See a second read before you apply.

The interactive demo uses a sample review and needs no account. The beta is free and applications are reviewed personally.