Docs Workflow#

The docs workflow is supporting infrastructure, not the core execution loop.

Core loop:

/hapo:specs -> /hapo:develop -> /hapo:test -> /hapo:code-review

Support docs flow:

/docs init
/docs update

What It Is For#

Use the docs workflow when you want project-level documentation such as:

• codebase summary
• architecture notes
• coding standards
• deployment guidance

What It Is Not For#

It is not a replacement for:

• task-level docs checkpoints
• spec artifacts
• verification evidence

CafeKit already expects lighter docs sync after verified task completion. /docs init and /docs update exist for broader project documentation work.