platonic-workflow

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Platonic Coding Workflow

Platonic Coding工作流

Orchestrate the complete five-phase Platonic Coding workflow from conceptual design through specification, implementation guide, code, and review.

编排完整的五阶段Platonic Coding工作流，覆盖从概念设计到规范制定、实现指南、代码开发及审查的全流程。

When to Use This Skill

何时使用该Skill

Use this skill when you need to:

Run the full workflow from design idea to reviewed implementation
Progress through phases with clear phase visibility and handoffs
Ensure traceability from design draft → RFC → impl guide → code → review
Coordinate other skills (platonic-specs, platonic-impl-guide, platonic-code-review) in the correct order

Keywords: workflow, platonic coding, design draft, RFC, implementation guide, code review, phase

当你需要以下功能时，可使用本Skill：

运行完整工作流：从设计想法到经过审查的实现
分阶段推进：清晰展示阶段进度与工作交接
确保可追溯性：从设计草案→RFC→实现指南→代码→审查的全链路可追溯
协调其他Skill：按正确顺序调用platonic-specs、platonic-impl-guide、platonic-code-review

关键词：工作流、Platonic Coding、设计草案、RFC、实现指南、代码审查、阶段

Phase Visibility

阶段可见性

Always show the current Phase of the workflow at the start of each step and in summaries:

Phase 0: Conceptual Design & Design Draft
Phase 1: RFC Specification (Draft)
Phase 2: Implementation Guide
Phase 3: Code Implementation
Phase 4: Spec Compliance Review
FINISHED: Workflow complete

在每一步开始和总结中，始终展示工作流的当前阶段：

Phase 0：概念设计与设计草案
Phase 1：RFC规范（草案）
Phase 2：实现指南
Phase 3：代码实现
Phase 4：规范合规审查
FINISHED：工作流完成

Workflow Summary

工作流概述

Phase	Focus	Output Location	Skills / Actions
0	Conceptual design, requirements	`docs/drafts/`	Interactive chat, optional items
1	Formal RFC from design draft	`specs/`	Generate RFC, then platonic-specs (refine)
2	Concrete impl guide from RFC	`docs/impl/`	platonic-impl-guide (create guide)
3	Write code from guide	Codebase	Coding agents
4	Review code vs specs & impl RFCs	Report	platonic-code-review
FINISHED	—	—	—

阶段	核心内容	输出位置	技能/操作
0	概念设计、需求	`docs/drafts/`	交互式聊天、可选项
1	基于设计草案生成正式RFC	`specs/`	生成RFC，随后调用platonic-specs（优化）
2	基于RFC生成具体实现指南	`docs/impl/`	调用platonic-impl-guide（创建指南）
3	基于指南编写代码	代码库	编码Agent
4	对照规范与实现指南审查代码	报告	调用platonic-code-review
FINISHED	—	—	—

Phase Details

阶段详情

Phase 0: Conceptual Design & Design Draft

Phase 0：概念设计与设计草案

Goal: Obtain a shared conceptual design (principles, constraints, conceptual interfaces, design art, etc.).
Method: Interactive chat; use optional items to communicate with the user.
Output: A design draft.
Location: Default
```
docs/drafts/
```
. The user may provide a draft from elsewhere.
Reference: See
```
references/phase-0-design-draft.md
```
.

目标：达成共识的概念设计（原则、约束、概念接口、设计示意图等）。
方法：交互式聊天；使用可选项与用户沟通。
输出：一份设计草案。
存储位置：默认
```
docs/drafts/
```
，用户也可从其他位置提供草案。
参考文档：参见
```
references/phase-0-design-draft.md
```
。

Phase 1: RFC Specification (Draft)

Phase 1：RFC规范（草案）

Goal: Turn the design draft into a formal RFC spec (Status: Draft).
Optional: Ask the user for RFC number/index if not specified.
Actions:
1. Generate RFC from the Phase 0 design draft.
2. Call platonic-specs to refine the generated RFC (and related specs).
Output: RFC(s) in the specs directory.
Location: Default
```
specs/
```
.
Reference: See
```
references/phase-1-rfc-spec.md
```
.

目标：将设计草案转化为正式的RFC规范（状态：草案）。
可选操作：若未指定RFC编号/索引，可向用户询问。
操作步骤：
1. 基于Phase 0的设计草案生成RFC。
2. 调用platonic-specs优化生成的RFC（及相关规范）。
输出：RFC文档存储在specs目录中。
存储位置：默认
```
specs/
```
。
参考文档：参见
```
references/phase-1-rfc-spec.md
```
。

Phase 2: Implementation Guide

Phase 2：实现指南

Goal: Produce a concrete implementation guide from the RFC spec.
Optional: Ask the user for RFC number/index for which to create the impl guide.
Actions: Use platonic-impl-guide to create the implementation guide (per README and skill docs).
Output: Implementation guide integrated into the project.
Location: Default
```
docs/impl/
```
.
Reference: See
```
references/phase-2-impl-guide.md
```
.

目标：基于RFC规范生成具体的实现指南。
可选操作：若未指定，可向用户询问要为哪个RFC创建实现指南。
操作步骤：使用platonic-impl-guide创建实现指南（遵循README及Skill文档）。
输出：集成到项目中的实现指南。
存储位置：默认
```
docs/impl/
```
。
参考文档：参见
```
references/phase-2-impl-guide.md
```
。

Phase 3: Code Implementation

Phase 3：代码实现

Goal: Implement the feature in code following the guide and RFCs.
Actions: Run coding agents to write code according to the implementation guide and specs.
Output: Source code in the existing codebase.
Reference: See
```
references/phase-3-implementation.md
```
.

目标：遵循指南与RFC规范实现功能代码。
操作步骤：运行编码Agent，根据实现指南与规范编写代码。
输出：存入现有代码库的源代码。
参考文档：参见
```
references/phase-3-implementation.md
```
。

Phase 4: Spec Compliance Review

Phase 4：规范合规审查

Goal: Review implementation against both RFC specs and implementation guides.
Actions: Call platonic-code-review to review the code implementation and the targeted RFC (specs and impl RFCs).
Output: Review and compliance report.
Reference: See
```
references/phase-4-review.md
```
.

目标：对照RFC规范与实现指南审查代码实现。
操作步骤：调用platonic-code-review审查代码实现及目标RFC（规范与实现相关RFC）。
输出：审查与合规报告。
参考文档：参见
```
references/phase-4-review.md
```
。

FINISHED

Workflow complete. Summarize outcomes and any follow-up recommendations.

工作流完成。总结成果及后续建议。

Default Paths

默认路径

Artifact	Default Path
Design drafts	`docs/drafts/`
RFC specs	`specs/`
Implementation guides	`docs/impl/`

Paths may be overridden by the user.

产物	默认路径
设计草案	`docs/drafts/`
RFC规范	`specs/`
实现指南	`docs/impl/`

用户可自定义路径。

Available References

可用参考文档

Phase	Reference File	Purpose
Overview	`workflow-overview.md`	End-to-end workflow and phase transitions
Phase 0	`phase-0-design-draft.md`	Conceptual design and design draft
Phase 1	`phase-1-rfc-spec.md`	RFC generation and platonic-specs refine
Phase 2	`phase-2-impl-guide.md`	platonic-impl-guide usage
Phase 3	`phase-3-implementation.md`	Coding agents and implementation
Phase 4	`phase-4-review.md`	platonic-code-review usage

See references/REFERENCE.md for detailed phase procedures.

阶段	参考文件	用途
概述	`workflow-overview.md`	端到端工作流与阶段过渡说明
Phase 0	`phase-0-design-draft.md`	概念设计与设计草案说明
Phase 1	`phase-1-rfc-spec.md`	RFC生成与platonic-specs优化说明
Phase 2	`phase-2-impl-guide.md`	platonic-impl-guide使用说明
Phase 3	`phase-3-implementation.md`	编码Agent与代码实现说明
Phase 4	`phase-4-review.md`	platonic-code-review使用说明

详情参见references/REFERENCE.md中的阶段流程说明。

Best Practices

最佳实践

Always show current phase at the start of each step and in status summaries.
Confirm handoffs: Before leaving a phase, confirm outputs and paths with the user if ambiguous.
Ask for indices when useful: In Phase 1 (RFC number) and Phase 2 (RFC for impl guide), ask for index if not provided.
Call skills explicitly: Phase 1 → platonic-specs (refine); Phase 2 → platonic-impl-guide; Phase 4 → platonic-code-review.
Preserve traceability: Keep links between design draft → RFC → impl guide → code in summaries and docs.

始终展示当前阶段：在每一步开始和状态总结中明确当前阶段。
确认工作交接：若输出内容或路径不明确，在离开当前阶段前与用户确认。
必要时询问索引：在Phase 1（RFC编号）和Phase 2（实现指南对应的RFC）中，若未提供索引则向用户询问。
显式调用Skill：Phase 1→platonic-specs（优化）；Phase 2→platonic-impl-guide；Phase 4→platonic-code-review。
保留可追溯性：在总结与文档中维护设计草案→RFC→实现指南→代码的关联链路。

Dependencies

依赖项

platonic-specs: Phase 1 (refine RFCs).
platonic-impl-guide: Phase 2 (create/update impl guides).
platonic-code-review: Phase 4 (review code vs specs and impl guides).
Read/write access to
```
docs/drafts/
```
,
```
specs/
```
,
```
docs/impl/
```
and codebase as needed.

platonic-specs：Phase 1（优化RFC）。
platonic-impl-guide：Phase 2（创建/更新实现指南）。
platonic-code-review：Phase 4（对照规范与指南审查代码）。
需具备
```
docs/drafts/
```
、
```
specs/
```
、
```
docs/impl/
```
及代码库的读写权限。