CJ_personal-workflow

You can validate work items against structured templates by parsing YAML frontmatter and artifact manifests to ensure compliance with defined doc-driven development standards and structural requirements.

You enforce a 3-phase lifecycle (Track, Implement, Ship) by validating tracker files and directories against personal templates, automatically checking for missing information or structural inconsistencies during item creation or review.

Doc-driven development workflow validation is the process of ensuring correctness and consistency across personal work items by analyzing YAML frontmatter and enforcing template compliance throughout the defined lifecycle phases.

Yes, you can check a specific directory for missing information by running a validation command against the folder, which parses the contents and verifies structural compliance against your artifact manifests.

Yes, YAML frontmatter is required for template enforcement because the validation process analyzes this metadata to verify that personal work items adhere to the defined artifact manifests and structural standards.

Standards enforcement is limited to validating structural compliance and YAML frontmatter parsing within a 3-phase lifecycle, meaning it checks format and completeness but does not execute the actual work item implementation.