ctx-import-plans
Import plan files into project specs directory. Use to convert external plans into project-tracked specs.
Best use case
ctx-import-plans is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Import plan files into project specs directory. Use to convert external plans into project-tracked specs.
Teams using ctx-import-plans should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/ctx-import-plans/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How ctx-import-plans Compares
| Feature / Agent | ctx-import-plans | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Import plan files into project specs directory. Use to convert external plans into project-tracked specs.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
Import plan files into the project's `specs/` directory.
## When to Use
- When plan files exist outside the project (e.g., from AI
tool plan modes)
- When converting external design docs to project specs
- When the user says "import that plan"
## When NOT to Use
- Plan is already in `specs/`
- Plan is too vague to be a spec (brainstorm first)
## Process
### 1. Locate the plan
If path provided, read it. Otherwise, check common locations:
- Current conversation context
- Session workspace files
### 2. Convert to spec format
Map plan sections to the spec template structure:
- Problem → Problem
- Steps/Tasks → Implementation
- Goals → Happy Path
- Risks → Edge Cases
### 3. Handle conflicts
If `specs/{name}.md` already exists:
- Compare contents
- Offer to merge, replace, or rename
### 4. Write the spec
Write to `specs/{name}.md`.
### 5. Create tasks (optional)
Offer to break the spec into tasks in TASKS.md.
## Quality Checklist
- [ ] Spec follows project template structure
- [ ] No conflicts with existing specs
- [ ] File written to correct location
- [ ] Tasks offered if applicableRelated Skills
ctx-plan-import
Import Claude Code plan files into project specs. Use when plan files in ~/.claude/plans/ should become permanent project specs.
ctx-verify
Verify before claiming completion. Use before saying work is done, tests pass, or builds succeed.
ctx-skill-creator
Create, improve, test, and deploy skills. Full skill lifecycle from intent to working skill file.
ctx-sanitize-permissions
Audit tool permissions for dangerous or overly broad entries. Use to ensure safe agent configuration.
ctx-recall
Browse session history. Use when referencing past discussions or finding context from previous work.
ctx-prompt
Apply, list, and manage saved prompt templates from .context/prompts/. Use when the user asks to apply, list, or create a reusable template like code-review or refactor.
ctx-journal-normalize
Normalize journal source markdown for clean rendering. Use after journal site shows rendering issues: fence nesting, metadata formatting, broken lists.
ctx-compact
Archive completed tasks and trim context. Use when context files are growing large.
ctx-check-links
Audit docs for dead links. Use before releases, after restructuring docs, or when running a documentation audit.
ctx-add-task
Add a task. Use when follow-up work is identified or when breaking down complex work into subtasks.
ctx-add-learning
Record a learning. Use when discovering gotchas, bugs, or unexpected behavior that future sessions should know about.
ctx-add-decision
Record architectural decision. Use when a trade-off is resolved or a non-obvious design choice is made that future sessions need to know.