Spec-Driven DevelopmentCollaborative authoring
Agent document edits
Review AI-assisted document suggestions before they change canonical content.
Beta
Agents can help draft or rewrite lifecycle document text, but they do not silently mutate canonical content. A person with edit access must review and apply a suggestion before the document changes.
Suggestion flow
- Ask for a document suggestion from a supported lifecycle document surface.
- Review the preview before anything is inserted or replaced.
- Dismiss the suggestion to leave the document unchanged.
- Apply the suggestion to write through the same editor and save path as a human edit.
- Integrity records provenance for the approved agent apply event.
What agents can change
Agent suggestions can insert or replace document content. They cannot directly change structured planning fields such as status, priority, Team, lead, dates, Version, Initiative membership, Issue links, Health, or permissions.
Use fields and selectors for structured state. Use agent document edits for reviewed narrative text only.
Safety boundaries
- Suggestions require edit permission on the underlying lifecycle object.
- Applying a suggestion records an
agent_applyevent with display-safe metadata. - Search, export, and agent context use plain-text and Markdown projections, not raw Yjs state.
- Restricted Source Library or workspace-object references are redacted, replaced with generic labels, or omitted when the viewer should not see them.
- Hidden or unavailable references are not serialized into exported Markdown or agent-ready payloads.