oat-project-import-plan

Importing an external markdown plan into OAT normalizes the document into a canonical plan.md format. The process resolves the target project structure, preserves the original source file, and generates runnable OAT task structures with stable IDs.

When normalizing your markdown file for OAT, the original source plan is safely preserved and stored separately. The Skill generates a new canonical plan.md file with structured phases and stable task IDs without altering your initial document.

Yes, OAT plan normalization generates stable task IDs for workflow automation. It converts external markdown plans into structured phases within a canonical plan.md format, enabling OAT's workflow capabilities and execution tracking.

You can use a colleague's markdown document for OAT project scaffolding by importing it with this Skill. It handles project resolution and normalizes the external plan into runnable OAT task structures, making it executable within the OAT ecosystem.

Importing external plans into OAT requires no specific external dependencies. The Skill operates independently using its internal scripts to handle project resolution, source file preservation, and plan normalization for OAT execution.