document

Documentation generation for software features applies profile-driven rubrics to ensure content coverage. It loads profile definitions to enforce project conventions, producing standardized artifacts for feature work, bug fixes, and design changes.

A profile-rubric workflow detects active profiles, loads their document rubrics, and applies them to the feature under development. This enforces required topic coverage and project conventions in the final documentation artifacts.

ADR-friendly tracing surfaces decisions and rationale in generated documentation by applying rubric-driven workflows. This aligns architectural decisions with project conventions, ensuring required topics are covered in the final docs.

Yes, rubric-driven documentation generation applies to bug fixes, software feature work, and design changes. It loads profile definitions and enforces content coverage to generate consistent documentation across multiple profiles.

Standardize project conventions by applying a profile-rubric workflow that loads profile definitions and enforces content coverage. This holds documentation to project conventions, ensuring consistent, compliant artifacts across multiple profiles.

You begin by listing the feature directory to trigger profile detection. Once active profiles are detected, the workflow loads their document rubrics and generates rubric-driven documentation for the feature.