import

Validate external planning documents against project context and convert them to PLAN.md.

Updated Aug 27, 2026

Search Tags:#automation #planning #import #PLAN.md #conflict-detection #towline #planning-context

Ready to run

npx skills add https://github.com/SienkLogic/towline --skill import-sienklogic

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: import
Source: https://github.com/SienkLogic/towline/tree/main/plugins/dev/skills/import
Command: npx skills add https://github.com/SienkLogic/towline --skill import-sienklogic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Imports external plan documents (design docs, RFCs, or AI-generated plans) into Towline's planning format, validates them against project context, and generates PLAN.md files while keeping the main orchestration lean.

Core Features & Use Cases

Validate imported plans against ROADMAP.md phases, REQUIREMENTS.md, and existing CONTEXT.md to detect conflicts with locked decisions.
Detect deprecated or conflicting architecture or tech choices and propose resolution.
Generate properly formatted PLAN.md files and delegate plan checking to a dedicated subagent when enabled.

Quick Start

Paste or attach the external plan to import and let Towline validate and convert it into PLAN.md.

Frequently Asked Questions about import

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

FAQPage Schema

How do I validate an external planning document against existing project requirements?▼

To validate an external planning document, the import skill checks it against ROADMAP.md phases, REQUIREMENTS.md, and CONTEXT.md to detect conflicts with locked decisions before conversion. It identifies deprecated architecture or tech choices and proposes resolutions.

What is the best way to convert an external design doc or RFC into a PLAN.md file?▼

Converting an external design doc or RFC into a PLAN.md file requires validating the content against project context first. The import skill orchestrates this by running stepwise conflict checks and phase validation to generate a properly formatted PLAN.md.

Do I need ROADMAP.md and CONTEXT.md files to import an external plan?▼

Yes, you need ROADMAP.md, REQUIREMENTS.md, CONTEXT.md, and phase-specific CONTEXT files for accurate evaluation. These planning context files provide the baseline constraints required to detect conflicts during the plan import process.

Can I delegate plan checking to a subagent when importing planning documents?▼

Yes, you can delegate plan checking to a dedicated subagent when the feature is enabled. This keeps the main orchestration lean while ensuring the imported planning document undergoes thorough validation before PLAN.md generation.

How does conflict detection work when importing AI-generated plans?▼

Conflict detection works by comparing the imported AI-generated plan against locked decisions in project context files. It runs stepwise checks to identify deprecated architecture or tech choices and flags them for resolution before finalizing the import.

What are the limitations of importing plans without a complete planning context?▼

Importing plans without a complete planning context limits accurate evaluation. Missing ROADMAP.md, REQUIREMENTS.md, or phase-specific CONTEXT files reduce the ability to detect conflicts with locked decisions, potentially allowing deprecated architecture choices into PLAN.md.