Platonic Coding

Intelligent orchestrator for Platonic Coding workflow. Auto-detects project state and routes to the right next step—initialize a project, run the recovery fl...

Security Scan

The skill is an instruction-only orchestrator for spec-driven development that only requires reading/writing project files and .platonic.yml; its declared actions align with its description, but the source is unknown so exercise caution before giving it broad access to repositories.

Purpose & Capability

Name/description match the skill contents: templates, guides, and references all implement a Platonic Coding workflow. Declared dependencies (read/write project dirs, access to .platonic.yml) are proportionate to an orchestrator that scaffolds RFCs, guides, and code.

Instruction Scope

SKILL.md instructs the agent to auto-detect project state, scan code, generate scaffolding, create implementation guides, and implement code/tests. These operations legitimately require reading and writing arbitrary files in the repository. Confirmation gates are documented (e.g., before coding) but can be overridden with 'no confirmations' — this gives the skill broad discretion if the user chooses to bypass gates.

Install Mechanism

No install spec and no code files that execute on install — instruction-only skill has minimal disk/write footprint from the skill package itself. Low install risk.

Credentials

The skill requests no environment variables, binaries, or external credentials. However, because it reads/writes the project tree, it could access any secrets stored in the repo (config files, keys, tokens). That access is functionally necessary for code recovery/scanning but is a privacy/risk consideration for repositories containing secrets.

Persistence & Privilege

always:false and no special privileges are requested. The skill may modify project files as part of its normal operation; this is within its expected scope and not an elevated platform privilege.

Assessment

This skill appears coherent with its stated purpose: it reads your repo, generates RFCs/guides, and can produce or modify code and tests. Because it can modify files and can be run without confirmations if you opt to bypass gates, only run it on repositories where you are comfortable with automated edits (use a throwaway or preview branch). Back up your repo or run the skill in a sandboxed clone first. Review generated/modified files before committing. Avoid running the skill on repositories that contain secrets or private keys, and be cautious about enabling optional integrations (e.g., platonic-brainstorming) which allow cross-skill invocation. Finally, note the skill's source/homepage is unknown — if provenance matters, prefer a skill with an auditable source or request the author/source before granting access.

Intelligent orchestrator for the complete specification-driven development lifecycle. Auto-detects project state and executes the appropriate workflow phases—initialization, specification management, implementation, or review. Integrates with platonic-brainstorming as an optional accelerator in Phases 1 and 2 for structured design exploration and refinement.

When to Use This Skill

Use this skill when you need to:

• Bootstrap a new project with Platonic Coding infrastructure
• Adopt Platonic Coding for an existing codebase (recover specs from code)
• Manage RFC specifications (validate, refine, generate indices)
• Implement features from RFC specs with guides and tests
• Review code for spec compliance
• Run the full workflow from design → RFC → code → review

Keywords: platonic coding, specs, RFC, implementation, review, workflow, spec-driven, initialization

Intelligent Auto-Detection

Auto-detects project state when invoked without specific instructions. See references/REFERENCE.md for the full decision tree.

Quick Reference:

• No .platonic.yml → INIT mode (scaffold new or recover existing)
• RFCs but no guides → Phase 2 (implementation)
• Guides + code → Phase 3 (review) or resume Phase 2

Override with canonical operations: init-scaffold, init-scan, specs-refine, impl-full, review, workflow --phase <N>.

Core Workflow Phases

Phase	Focus	Output	Brainstorming
1	RFC Specification	Draft → RFC → specs-refine	✅ Optional
2	Implementation	Guide → Code + Tests	✅ Optional
3	Review	Compliance report	❌

Phases run sequentially (full workflow) or independently (explicit invocation). See references/WORKFLOW/workflow-overview.md for details.

Operation Modes

INIT Mode

Bootstrap Platonic Coding infrastructure. Operations: init-scaffold, init-scan, init-plan-modular-specs, init-recover-*.

Examples: init-scaffold for project "Acme", init-scan then recover specs.

SPECS Mode

Manage RFC specifications. Operations: specs-refine (comprehensive), specs-generate-*, specs-validate-*, specs-check-*.

Examples: specs-refine, specs-generate-index.

IMPL Mode

Translate RFCs to guides and code. Operations: impl-full (default), impl-create-guide, impl-code, impl-validate-guide, impl-update-guide.

Confirmation Gates: Pauses after impl guide and coding plan. Override with "no confirmations".

Examples: impl-full for RFC-042, impl-code from IG-001.

REVIEW Mode

Validate code against specs. Generates report-only by default (no code changes). 6-step process: understand specs → checklist → map → review → discrepancies → report.

Examples: review src/auth/ against RFC-001, review for gap analysis.

WORKFLOW Mode

Orchestrate full 3-phase flow. See references/WORKFLOW/workflow-overview.md.

Examples: workflow --phase 1, workflow with platonic-brainstorming.

---

For detailed guides, see references/REFERENCE.md.

Default Paths & Templates

Artifact	Path	Naming
Drafts	docs/drafts/	YYYY-MM-DD-<topic>-design.md
RFCs	docs/specs/	RFC-NNN-<name>.md
Guides	docs/impl/	IG-NNN-<name>.md

Templates in assets/ use {{PLACEHOLDER}} syntax.

Best Practices

1. Trust auto-detection; override with explicit operations when needed
2. Review generated artifacts (all Draft status)
3. Run specs-refine regularly
4. Use confirmation gates—don't skip unless confident
5. Review mode is report-only by default

Dependencies

• Read/write to project directories
• Access to .platonic.yml
• Understanding of target language/framework