# Response Format Templates

Use these templates to structure your responses consistently. Choose the appropriate template based on the task type.

## Read-only tasks

```markdown
## Confluence findings
- Site: ...
- Space: ...
- Pages checked: ...
- Candidate pages: ...
- Summary: ...
- Open questions: ...
```

## Strict metadata / strict scoped read

```markdown
## Confluence metadata findings
- Mode: strict_metadata or strict_scoped_read
- Allowed scope: page ID, space, parent page ID, or none yet
- Site: ...
- Space: ...
- Candidate pages: page IDs, titles, labels, ancestor path, modified time
- Pages selected for content read: none yet or [list]
- Open questions: ...
```

## Large result set handling

When you apply a top-N or batch limit, make it explicit:

```markdown
## Result-set handling
- Total matches: ...
- Ranked candidates considered: ...
- Pages read in full or in part: ...
- Batch strategy: top 5, top 10, per-page mini-summaries, section extraction, etc.
```

## Write tasks (create or update)

Use this structure before or after the API call as appropriate:

```markdown
## Publish plan
- Action: create or update
- Site: ...
- Space: ...
- Parent page or page ID: ...
- Title: ...
- Labels: ...
- Post-create actions: labels, attachments, none
- Risks or assumptions: ...

## Draft content
[show the key structure or the body preview if useful]

## API result
- Status: ...
- Page ID: ...
- Version: ...
- URL: ...
```
