Platonic Coding
ReviewAudited by ClawScan on May 1, 2026.
Overview
This is a coherent workflow skill for generating specs, implementation guides, code, tests, and reviews within a project, with disclosed project read/write access and no evidence of hidden execution or data exfiltration.
This skill appears suitable for a project workflow assistant, but install it only if you want an agent to read and write project documentation and potentially implement code/tests. Keep confirmation gates enabled, review generated specs and plans, and check diffs before accepting changes.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
The agent may create or change project code and tests as part of the workflow.
The skill is explicitly allowed to move from specifications into code changes. This is purpose-aligned and includes confirmation gates, but users should notice that it can modify source code when used for implementation.
IMPL Mode... Translate RFCs to guides and code... Confirmation Gates: Pauses after impl guide and coding plan. Override with "no confirmations".
Use the confirmation gates, inspect generated implementation guides and coding plans, and review file diffs before accepting changes.
Generated project documents may influence future agent coding and review decisions.
The workflow creates persistent specifications that future implementation and review steps will treat as authoritative. This is central to the skill, but inaccurate or unreviewed specs could steer later work.
RFCs are the authoritative specifications for the {{PROJECT_NAME}} system.Review generated RFCs, implementation guides, terminology, and indexes before relying on them for future code generation.
Project requirements or design details may be used by the optional brainstorming integration.
The skill can optionally invoke another skill and share design context during brainstorming. The integration is disclosed and user-directed, but users should be aware project details may be passed into that workflow.
Use Skill tool with `skill: "platonic-brainstorming"` to check availability... Invoke: If available and user wants structured exploration
Only enable the optional brainstorming step when you are comfortable sharing the relevant project context with that skill.