docs

You can automate project documentation generation by running a prompt-driven workflow that produces staged doc fragments or regenerates the entire docs tree from spec and source data. Use /docs --quick for fragments or /docs --full for the complete tree.

A spec-driven documentation workflow generates and validates docs by applying structured prompts across planning stages. It creates lightweight, reviewable doc fragments during development cycles and ensures consistency with project changelogs before any guarded commits.

Documentation fragments are staged and validated through a reviewer-guarded merge process that requires explicit human approval before committing. This safe staging ensures frontmatter metadata and validation checks pass before any docs are merged into version control.

Canonical regeneration rebuilds the complete documentation tree from spec and source data using a human-in-the-loop validation process. This ensures that regenerated docs remain consistent with your project configuration while requiring explicit approval before overwriting existing files.

Prompt-driven documentation governance relies on structured constraints like frontmatter metadata and validation checks. It requires explicit approval for guarded commits, meaning it cannot automatically merge changes without human-in-the-loop validation, which may slow down fully automated pipelines.

You can configure the documentation mode with /setup if needed, then run /docs --quick to generate staged fragments. This lightweight process integrates with your existing development cycles and project changelogs without requiring external dependencies.