system-book-authoring

System book authoring maintains a human-readable system book for understanding architecture, workflows, and operations without requiring direct code analysis. It ensures documentation accurately reflects system decisions and architecture by facilitating co-authoring with agents.

Yes, agent co-authoring supports parallel subagent execution for substantial implementation work, prioritizing clarity for non-coding operators. It reduces manual effort while ensuring the technical documentation remains consistent and decision-driven.

The best way to update a system book chapter is to propose edits that clarify current and target behavior, including decision logs and relevant code snippets. This keeps the system book accurate and accessible for non-coding operators.

Maintaining a system book requires keeping a specific markdown file, `docs/SYSTEM_BOOK.md`, up-to-date and accessible. The process relies on standard markdown formatting to structure architecture, workflows, and operations documentation.

Agent collaboration for workflow documentation works by leveraging parallel subagent execution to handle substantial implementation work. Agents co-author the system book to ensure consistency, keeping documentation accurate without requiring direct code analysis.