caesar0301/platonic-coding-skills

Overview

This skill orchestrates the five-phase Platonic Coding workflow from conceptual design to final spec-compliance review. It always shows the current Phase and coordinates the right sub-skills and agents for each step, ensuring traceability from draft to reviewed implementation. Use it to run, monitor, and complete a specs-driven implementation process end-to-end.

How this skill works

At each interaction the skill displays the current Phase (0–4 or FINISHED) and guides the next actions. Phase 0 uses interactive chat to produce a design draft; Phase 1 generates an RFC and invokes platonic-specs to refine it; Phase 2 creates an implementation guide via platonic-impl-guide; Phase 3 launches coding agents to write the code; Phase 4 calls platonic-code-review to produce a compliance report. The skill confirms handoffs, default artifact paths, and any user-specified indices before advancing phases.

When to use it

• You need an end-to-end, traceable workflow from idea to reviewed code
• You want clear phase visibility and controlled handoffs between specification and implementation
• You must enforce RFC-driven development and link artifacts across phases
• You need to coordinate sub-skills (platonic-specs, platonic-impl-guide, coding agents, platonic-code-review)
• You want automated phase summaries and a final compliance report

Best practices

• Always show the current Phase at the start of each step and in summaries
• Confirm outputs and storage paths with the user before advancing a phase
• Ask for RFC numbers or indices when generating or linking specs and guides
• Invoke the specific sub-skill for each Phase: platonic-specs (1), platonic-impl-guide (2), coding agents (3), platonic-code-review (4)
• Preserve traceability by linking design draft → RFC → impl guide → code in each summary

Example use cases

• Turn a product concept into a formal RFC and implementation with traceable artifacts
• Create an implementation guide from an existing RFC and then generate code from the guide
• Run a spec-compliance review for newly merged code against its RFC and implementation guide
• Coordinate multiple contributors by enforcing phase handoffs and artifact locations
• Automate end-to-end delivery so each phase produces stored outputs in the expected directories