easysdd-guidedoc

Generate developer and user guides by transforming internal specs and implementation details into publishable, version-controlled markdown files. The process drafts role-targeted documents with structured YAML frontmatter, enforcing required fields like doc_type, slug, component, status, and tags for clear repository integration.

Keep documentation synchronized with code changes by detecting existing guides, classifying updates versus new documents, and marking old content as outdated when code diverges. This ensures team members and downstream users always rely on current, stable guides located in docs/dev or docs/user directories.

Write a dev-guide by summarizing the spec and code, then outputting the file to docs/dev/{slug}.md. Enforce the YAML frontmatter schema including doc_type, slug, component, status, summary, tags, and last_reviewed, transitioning the document status to current once the draft is complete.

Spec-driven documentation works for feature acceptance handoff by converting specs and implementation details into actionable, role-targeted guides. It outputs structured files under docs/user or docs/dev, ensuring downstream users and contributors can quickly verify and integrate new features.

Mark existing guides as outdated during documentation updates when the code diverges from the previously documented spec. The system detects these mismatches, classifies the update requirement, and applies the outdated status transition to prevent users from relying on stale information.