backend-document-workflow

Automate backend documentation workflows using command equivalents for design, planning, updating, and reverse-engineering. This process operates without subagent dependencies, guiding requirement clarification and enforcing strict review gates before proceeding.

Reverse-engineer existing backend architecture by using the reverse mode command equivalent. This mode discovers and documents existing codebase architecture and underlying requirements automatically, ensuring standardized output without manual extraction.

Generate test and work plans from approved design documents by triggering the plan mode command equivalent. It directly processes the approved design inputs to create structured work plans, ensuring alignment with the established backend design requirements.

Backend documentation generation strictly enforces review and approval gates before proceeding to the next phase. The workflow halts automated progression until the design, plan, or update outputs are explicitly reviewed and approved.

Update existing backend documentation consistently using the update mode command equivalent. This workflow facilitates targeted updates to existing documents, reducing manual effort and maintaining structural consistency across the codebase architecture.

Use a structured workflow for backend design documentation when creating new features, generating work plans, or reverse-engineering undocumented codebases. This standardizes the design, planning, and updating processes to reduce manual effort and ensure consistency.