---
description: "Strict documentation policy - summaries in chat only"
globs:
alwaysApply: true
---

# Documentation Policy

## CRITICAL: Never Auto-Generate Documentation Files

❌ **FORBIDDEN - Never create these files unless explicitly asked:**
- README files
- CHANGELOG files  
- Summary documents (.md files)
- Architecture diagrams (unless spec requires it)
- Documentation artifacts of any kind

✅ **ALLOWED - Create files only when user says:**
- "Create a README for..."
- "Document this in..."
- "Write a summary document for..."
- "Generate docs for..."

## Required: Succinct Summaries in Chat

✅ **DO provide summaries directly in chat:**
- **Length:** 100-500 words
- **Format:** Bullets + next steps + recommended actions
- **No files created** - everything stays in conversation

### Summary Template

When completing work, provide:
```
## Summary
[2-3 sentence overview of what was done]

## Key Changes
- Bullet 1: What changed and why
- Bullet 2: What changed and why
- Bullet 3: What changed and why

## Recommended Action
- Suggestion 1: What do you recommend and why
- Suggestion 2: What do you recommend and why
- Suggestion 3: What do you recommend and why

## Suggested TODOs
[Propose items for the TODO list - user will approve/reject]

1. Task description (AI can handle)
2. 🧑 Task description (requires human decision/action)
3. Task description (AI can handle)
4. 🧑 Task description (requires human decision/action)
```

## Summary

**Default behavior:** CODE + TESTS + CHAT SUMMARY + TODO SUGGESTIONS

**Documentation files:** ONLY when explicitly requested

**Summaries:** Always in chat (100-500 words, bullets, TODO suggestions, recommendations)

**TODOs:** Suggest items for approval - use 🧑 for human tasks

---

## Related Policy

- **Documentation Standards:** `05-documentation.mdc` — When to document
- **Chat-Based Summaries:** Default format for all completions (100-500 words)