hiddink-harness-takeover

To reverse-engineer specifications from existing markdown agent files, this skill parses YAML frontmatter and markdown body content to automatically generate a structured .spec.md file capturing intent, invariants, and I/O contracts.

Documenting undocumented agent configurations is best handled by deriving a canonical specification from the organic implementation files, creating a structured source of truth that captures the agent's intent and I/O contracts.

Generating I/O contracts for an undocumented agent involves analyzing the existing markdown files to extract behavioral invariants and intent, then outputting a standardized specification file to enforce those contracts during maintenance.

Yes, you can use the generated .spec.md file for invariant-preserving refactoring, as it serves as a structured source of truth that can be consumed by refactoring tools to ensure changes do not violate the original agent's intent.

Yes, this specification generation tool requires YAML frontmatter within the agent or skill markdown files, as parsing both the frontmatter and the markdown body content is necessary to accurately derive the standardized specifications.

Reverse-engineering agent behavior into a formal specification solves the issue of undocumented configurations by creating a clear contract, ensuring that future maintenance and refactoring preserve the original operational invariants.