external-plan-import

Import external plans into colony ROADMAP phases with conflict checks.

9|1|Updated Feb 1, 2026

Search Tags:#workflow #planning #roadmap #spec #prd #import #conflict-detection

Ready to run

npx skills add https://github.com/calcosmic/Aether --skill external-plan-import

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: external-plan-import
Source: https://github.com/calcosmic/Aether/tree/main/.aether/skills-codex/colony/external-plan-import
Command: npx skills add https://github.com/calcosmic/Aether --skill external-plan-import

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the safe integration of external plans (PRDs, roadmaps, specs) into the colony planning workflow, preventing contamination of internal decisions.

Core Features & Use Cases

Conflict-aware source detection and import of external plans
Plan parsing into goals, tasks, dependencies, constraints, and acceptance criteria
Conflict reporting with resolution options and safe-merge behavior

Quick Start

Provide the external plan document or link, and request an import; the system will validate conflicts and import non-conflicting items into the ROADMAP.

Frequently Asked Questions about external-plan-import

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

FAQPage Schema

How do I import a PRD or external roadmap into my planning workflow?▼

To import a PRD or external roadmap, provide the document or link to the system. It parses goals, tasks, and dependencies, then checks for conflicts with existing decisions before committing the validated items into the ROADMAP.

What happens when an imported plan conflicts with existing architecture or dependencies?▼

When an imported plan conflicts with existing architecture or dependencies, the system detects these issues during pre-import checks. It then presents resolution options and employs safe-merge behavior before updating the roadmap.

Can I import external design documents without overwriting my current project constraints?▼

Yes, you can safely import external design documents without overwriting current constraints. The system performs conflict detection against existing phases and constraints, preserving the original source for reference while only committing non-conflicting items.

How does external plan parsing handle dependencies and acceptance criteria?▼

External plan parsing extracts goals, tasks, dependencies, and acceptance criteria from the source document. It translates these validated components into distinct ROADMAP phases while emitting an import-complete signal upon success.

Do I need to manually resolve naming conflicts when importing specs?▼

You do not need to manually find naming conflicts when importing specs. The system automatically detects conflicts including naming and architecture, presenting you with resolution options to choose from before the commit phase.

What is the best way to integrate external specs into colony planning safely?▼

The best way to safely integrate external specs is using a conflict-aware import process. This approach validates the external plan against internal decisions, offers resolution options for conflicts, and translates the clean data into ROADMAP phases.