platonic-code-review
Platonic Code Review
Validate that code implementation is consistent with project specifications and requirements.
When to Use This Skill
Use this skill when you need to:
- Verify code implementation matches RFC specifications
- Validate feature completeness against requirements
- Check consistency between specs and actual code
- Identify gaps where specs exist but implementation is missing
- Find discrepancies where code behavior differs from specs
- Audit compliance with documented design decisions
Keywords: spec compliance, implementation validation, requirement verification, consistency check, gap analysis
What This Skill Does
More from caesar0301/platonic-coding-skills
platonic-specs
Manage RFC-style specifications with validation, and dynamic generation of history, index, and namings files. Use when validating RFC documents, checking taxonomy compliance, or generating specification indices and terminology references.
11platonic-workflow
Orchestrate the full Platonic Coding workflow from conceptual design to RFC specs, implementation (guide + code with tests), and spec-compliance review. Always shows current phase; uses interactive chat in Phase 0, invokes platonic-specs in Phase 1, platonic-impl in Phase 2 (impl guide + coding), and platonic-code-review in Phase 3.
11platonic-impl-guide
Create and manage implementation guides that translate RFC specifications into concrete, project-specific implementation designs. Implementation guides are language-aware, framework-aware, and MUST NOT contradict RFC specs. Use when planning implementation of RFC specifications, creating detailed technical designs, or documenting implementation architecture.
10platonic-init
Initialize the Platonic Coding system for any project. Scaffolds specs infrastructure (.platonic.yml, RFC templates, impl guide directory) and scans existing codebases to recover missing conceptual and architecture design specs as Draft RFCs. Use when adopting platonic coding for a new or existing project.
9platonic-code-specs
Manage RFC-style specifications with templates, validation, and dynamic generation of history, index, and namings files. Use when initializing specification systems, validating RFC documents, checking taxonomy compliance, or generating specification indices and terminology references.
6platonic-impl
Translate RFC specifications into concrete implementation guides and then implement them as code. Manages the full implementation lifecycle from spec analysis through architecture design, coding plan, and code with tests. Use when creating implementation guides, implementing features from specs, or running the full spec-to-code pipeline.
3