readme-analyze-existing

Diagnose an existing README by validating its SKILL.md frontmatter against the source-analysis spine, reporting detected issues, and outputting a machine-readable payload of structured actions.

Generate a structured action list for documentation cleanup by comparing a README to the source spine, producing finite edits like CUT, RELOCATE, RESTRUCTURE, REWRITE-HEADING, REORDER, and ADD-CALLOUT.

Yes, you can separate documentation diagnosis from automated edits because this workflow produces a spine-consistent diagnosis payload consumed separately by the downstream readme-edit step for safe application.

Yes, the process validates SKILL.md frontmatter during README analysis, checking for structural alignment with the source spine and reporting detected issues before generating the action payload.

A machine-readable payload is needed for readme-edit tasks to ensure reproducible cleanup workflows, allowing AI agents and documentation teams to coordinate safe, auditable edits based on the diagnosis.

Avoid automated spine alignment for README cleanup when you require manual narrative control rather than finite structured actions, as this process strictly generates machine-readable payloads for automated application.