Platonic Coding
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 → INLINECODE9 | ✅ 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 | INLINECODE36 | INLINECODE37 |
| 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
- Review generated artifacts (all Draft status)
- Run
specs-refine regularly - Use confirmation gates—don't skip unless confident
- Review mode is report-only by default
Dependencies
- - Read/write to project directories
- Access to INLINECODE45
- Understanding of target language/framework
Platonic编码
智能编排器，用于完整的规范驱动开发生命周期。自动检测项目状态并执行相应的工作流阶段——初始化、规范管理、实现或审查。与platonic-brainstorming集成，作为阶段1和阶段2的可选加速器，用于结构化设计探索和优化。
何时使用此技能
在以下情况下使用此技能：
- - 引导新项目，建立Platonic编码基础设施
- 采用Platonic编码到现有代码库（从代码中恢复规范）
- 管理RFC规范（验证、优化、生成索引）
- 实现RFC规范中的功能，附带指南和测试
- 审查代码是否符合规范
- 运行从设计→RFC→代码→审查的完整工作流
关键词：platonic编码、规范、RFC、实现、审查、工作流、规范驱动、初始化
智能自动检测
在未指定指令时自动检测项目状态。完整决策树请参见references/REFERENCE.md。
快速参考：
- - 无.platonic.yml → 初始化模式（搭建新项目或恢复现有项目）
- 有RFC但无指南 → 阶段2（实现）
- 有指南+代码 → 阶段3（审查）或恢复阶段2
覆盖使用规范操作：init-scaffold、init-scan、specs-refine、impl-full、review、workflow --phase 。
核心工作流阶段
| 阶段 | 重点 | 输出 | 头脑风暴 |
|---|
| 1 | RFC规范 | 草稿→RFC→specs-refine | ✅ 可选 |
| 2 |
实现 | 指南→代码+测试 | ✅ 可选 |
|
3 | 审查 | 合规报告 | ❌ |
阶段按顺序运行（完整工作流）或独立运行（显式调用）。详情请参见references/WORKFLOW/workflow-overview.md。
操作模式
初始化模式
引导Platonic编码基础设施。操作：init-scaffold、init-scan、init-plan-modular-specs、init-recover-*。
示例：init-scaffold for project Acme、init-scan then recover specs。
规范模式
管理RFC规范。操作：specs-refine（全面）、specs-generate-
、specs-validate-、specs-check-*。
示例：specs-refine、specs-generate-index。
实现模式
将RFC转换为指南和代码。操作：impl-full（默认）、impl-create-guide、impl-code、impl-validate-guide、impl-update-guide。
确认关卡：在实现指南和编码计划后暂停。使用no confirmations覆盖。
示例：impl-full for RFC-042、impl-code from IG-001。
审查模式
验证代码是否符合规范。默认仅生成报告（不修改代码）。6步流程：理解规范→检查清单→映射→审查→差异→报告。
示例：review src/auth/ against RFC-001、review for gap analysis。
工作流模式
编排完整的3阶段流程。请参见references/WORKFLOW/workflow-overview.md。
示例：workflow --phase 1、workflow with platonic-brainstorming。
详细指南请参见references/REFERENCE.md。
默认路径与模板
| 工件 | 路径 | 命名 |
|---|
| 草稿 | docs/drafts/ | YYYY-MM-DD-<topic>-design.md |
| RFC |
docs/specs/ | RFC-NNN-
.md |
| 指南 | docs/impl/ | IG-NNN-.md |
assets/中的模板使用{{PLACEHOLDER}}语法。
最佳实践
- 1. 信任自动检测；必要时使用显式操作覆盖
- 审查生成的工件（所有草稿状态）
- 定期运行specs-refine
- 使用确认关卡——除非确信，否则不要跳过
- 审查模式默认仅生成报告
依赖项
- - 对项目目录的读写权限
- 访问.platonic.yml
- 理解目标语言/框架
