platonic-specs_skill

Overview

This skill manages RFC-style specifications with AI-assisted validation and generation tools. It helps keep spec collections consistent by updating history, index, and terminology files while checking taxonomy and cross-reference integrity. Use it to automate routine spec maintenance and enforce RFC conventions across a project.

How this skill works

The skill inspects a specifications directory of Markdown RFC files, parsing metadata, links, and defined terms. It runs validation passes to detect broken cross-references, taxonomy mismatches, and compliance deviations, then generates or updates history, index, and namings files based on current content. Operations are defined as small, focused tasks so you can run a comprehensive refine or a single generator like history or index. Outputs include reports of errors and warnings plus updated Markdown artifacts ready for commit.

When to use it

• Validating RFC documents for cross-reference and metadata consistency
• Generating or updating RFC change history, index, or terminology references
• Checking taxonomy and terminology compliance across specs
• Refining specifications before a release or public publication
• Running routine maintenance to prevent drift in naming and links

Best practices

• Read the operation reference before running an operation to understand scope and side effects
• Keep a canonical rfc-standard.md in the specs directory to codify conventions
• Run validation and taxonomy checks regularly, not only after large changes
• Update the history file whenever you change RFC content or deprecate terms
• Use the generate-namings operation to keep terminology current and collect deprecated terms into history

Example use cases

• Run a full Refine operation to validate all RFCs and update index, history, and namings before a release
• Use Generate History to produce an RFC change log from commit notes or metadata for a release announcement
• Run Validate Consistency to find and fix broken cross-references before publishing a specification
• Use Check Taxonomy to ensure a new RFC uses established terminology and avoid introducing conflicting names
• Generate Index to build a quick-links index for consumption in a docs site or developer portal