oat-project-import-plan

Import external markdown plans into OAT's canonical plan.md format.

1|Updated Jan 26, 2026

Search Tags:#task management #workflow automation #project scaffolding #oat #plan import #markdown normalization

Ready to run

npx skills add https://github.com/tkstang/open-agent-toolkit --skill oat-project-import-plan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: oat-project-import-plan
Source: https://github.com/tkstang/open-agent-toolkit/tree/main/.agents/skills/oat-project-import-plan
Command: npx skills add https://github.com/tkstang/open-agent-toolkit --skill oat-project-import-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the process of integrating existing markdown-based plans into the OAT project structure, ensuring consistency and enabling OAT's workflow capabilities.

Core Features & Use Cases

Plan Normalization: Converts external markdown plans into OAT's canonical plan.md format, including stable task IDs and structured phases.
Source Preservation: Safely stores the original imported plan for reference.
Use Case: You have a detailed project plan written in a markdown document by a colleague. Use this Skill to import it into your OAT project, making it executable within the OAT ecosystem.

Quick Start

Use the oat-project-import-plan skill to import the external plan located at './my-external-plan.md'.

Frequently Asked Questions about oat-project-import-plan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I import an external markdown plan into an OAT project?▼

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.

What happens to my original markdown file when normalizing it for OAT?▼

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.

Does OAT plan normalization generate stable task IDs for workflow automation?▼

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.

Can I use a markdown document created by a colleague for OAT project scaffolding?▼

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.

Does importing external plans into OAT require any specific dependencies?▼

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.