Outline Wiki Content

Task Modes

Create or Rewrite Page

• Draft a compact outline before writing full prose.
• Start with context and outcome; then provide actionable details.
• Add examples, commands, and decision criteria where ambiguity is likely.
• Keep section titles task-oriented (for example: "Restore Access" not "Access").

Update Existing Page

• Preserve stable concepts and links unless a change is requested.
• Show changes as: keep, update, remove, add.
• Highlight breaking changes, renamed terms, and follow-up edits needed in related docs.

Reorganize Collection

• Propose a target tree grouped by user intent, not by internal team structure.
• Keep depth shallow where possible (typically 2-3 levels).
• Define document ownership per top-level area.
• Include a migration sequence: move, merge, redirect, archive.

Audit Documentation Quality

• Score pages on clarity, correctness, freshness, and findability.
• Mark stale pages with an explicit review or archive recommendation.
• Recommend a small number of high-impact fixes first.

Output Templates

New Page Draft

Use this structure:

# <Title>

<1-2 sentence purpose and scope>

## When to Use This
## Prerequisites
## Steps
## Validation
## Troubleshooting
## Ownership and Review

Update Proposal

Use this structure:

Document: <collection/path/title>

## Keep
- ...

## Update
- ...

## Remove
- ...

## Add
- ...

Reference Material

• Read references/api_reference.md when interacting with Outline APIs, IDs, or automation.
• Stay in this file for purely editorial writing and information architecture tasks.