platonic-init

To scaffold a project setup with RFC workflows, this tool initializes Platonic Coding infrastructure by generating a .platonic.yml configuration file alongside structured docs/specs, docs/impl, and drafts directories to accelerate project onboarding and governance.

Yes, you can recover design specs from an existing codebase using a guided five-phase workflow that analyzes your current project structure and extracts the architectural metadata into standardized docs/specs and docs/impl formats.

The best way to bootstrap infrastructure for a new project is to run the initialization process at the project root, which prompts for custom metadata and instantly scaffolds ready-made templates and structured directories for consistent development.

Yes, you need file I/O access to the project root directory because the initialization process must write the .platonic.yml configuration and process template placeholders to generate the required structured directories.

Yes, the scaffolding workflow supports customizing project metadata by requiring user input during initialization to process placeholders within the generated templates and configuration files accurately.

A key limitation when recovering specs from existing code is that the guided five-phase workflow depends on user input and accurate file I/O access to correctly parse and map the current codebase structure into the standardized docs/impl and docs/specs formats.