Validate external planning documents against project context and convert them to PLAN.md.
npx skills add https://github.com/SienkLogic/towline --skill import-sienklogic
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
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.
Paste or attach the external plan to import and let Towline validate and convert it into PLAN.md.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
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.
MINT-IALoad project documents and repository patterns to produce a phase-numbered CONTEXT.md.
da-moonExecute roadmap phases by loading PLAN.md files and tracking progress.
kivo360Define the official schema and migration rules for .moai/config.json files.
coco-researchImport external plan files into GSD PLAN.md with conflict detection against PROJECT.md.
