coworker-context

To keep YAML frontmatter consistent during external LLM edits, enforce byte-exact preservation rules for delimiters, key order, spacing, and quoting behavior to prevent metadata corruption in generated artifacts.

Standardizing LLM-generated artifacts requires enforcing a strict stage header contract for operator-facing outputs and restricting documentation types to Diátaxis taxonomy categories to maintain consistency across init, plan, and archive stages.

To ensure traceability between PRD success criteria and archive validation, require archive validation checklist items to mirror PRD success criteria on a 1:1 basis, maintaining strict consistency throughout the artifact lifecycle.

Yes, external coworker LLMs can generate Diátaxis taxonomy documentation without drift by applying output discipline constraints, structured Q&A sections, and history-agnostic naming gates to standardize the generation process.

YAML frontmatter breaks during external LLM delegation because models alter byte structure; enforcing strict preservation of delimiters, key order, and quoting behavior prevents this metadata corruption.

Structure init-task clarification rounds by standardizing structured Q&A and status expectation sections, ensuring reliable iteration and consistent logging when an external LLM generates the initial artifacts.