tasks-documentation

[IMPORTANT] Use TaskCreate to break ALL work into small tasks BEFORE starting — including tasks for each file read. This prevents context loss from long files. For simple tasks, AI MUST ask user whether to skip.

Prerequisites: MUST READ .claude/skills/shared/evidence-based-reasoning-protocol.md before executing.

Quick Summary

Goal: Autonomous documentation generation with structured templates for code comments, API docs, and architecture docs (subagent variant of documentation).

Workflow:

1. Identify Type — Code comments, API documentation, or architecture documentation
2. Apply Pattern — C# XML docs, TypeScript JSDoc, API endpoint docs, README structure, or inline comments
3. Follow Guidelines — Document "why" not "what", include examples, keep close to code, update with changes

Key Rules:

• Autonomous: Use for documentation tasks without user feedback loop
• DO: Document public APIs, explain "why", include usage examples, keep docs close to code
• DON'T: State obvious, leave TODOs indefinitely, duplicate code in docs, create separate stale docs