platonic-code-specs_skill

Overview

This skill manages RFC-style specification systems with templates, validation, and automated generation of history, index, and terminology files. It helps initialize specification folders, enforce consistency, and produce living documentation artifacts for project RFCs. Use it to keep RFC collections organized, discoverable, and standards-compliant.

How this skill works

The skill reads and writes Markdown files in a target specs directory and applies templates to create standard RFC artifacts. It validates cross-references, taxonomy, and metadata, and can generate or update rfc-history.md, rfc-index.md, and rfc-namings.md based on the current set of RFCs. Operations are driven by discrete commands (Initialize, Refine, Generate History/Index/Namings, Validate Consistency, Check Taxonomy, Check Compliance) guided by reference files.

When to use it

• Initializing a new project's RFC system and creating the core spec files from templates
• Running a full refinement to validate cross-references, metadata, and taxonomy consistency
• Generating or refreshing the RFC change history, index of RFCs, or terminology/namings reference
• Validating a set of RFC documents against the project's RFC standard
• Checking taxonomy and term usage across RFCs before a release or audit

Best practices

• Read the operation reference before running an action to understand inputs and side effects
• Keep rfc-standard.md authoritative for project conventions and update it when rules change
• Run validation and taxonomy checks regularly as part of documentation CI or pre-release checks
• Update rfc-history.md whenever you make breaking or notable changes to RFCs
• Treat deprecated terms as historical notes and keep rfc-namings.md current and concise

Example use cases

• Bootstrapping specs for a new project by generating rfc-standard.md, rfc-history.md, rfc-index.md, and rfc-namings.md from templates
• Performing a nightly refinement to catch broken links, missing metadata, or taxonomy drift across RFCs
• Creating an updated index with quick links before publishing a specification bundle
• Extracting and organizing terminology into rfc-namings.md to standardize naming across teams
• Validating a set of RFCs against the RFC standard to prepare for external review