design-import

A command that converts a Markdown, JSON, or HTML design document into designdoc.json, a structured file used by Plan Cascade. HTML inputs can include exports from Confluence or Notion.

In plain words
What is it for?
Use it to import design notes, specifications, or exported documentation before running Plan Cascade planning steps.
Why use it?
It avoids manually rewriting an existing design document into the format the planning workflow expects.

Command

Part of the plan-cascade plugin — 7 skills, 33 commands shipped together

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add commands/taoidle/plan-cascade/design-import
Clone the repo
git clone --depth 1 https://github.com/Taoidle/plan-cascade

Or install plan-cascade, the plugin that ships this one along with the rest of its 7 skills, 33 commands.

Per session 32 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,030 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00032 $0.02030
Opus 5 $0.00016 $0.01015
Sonnet 5 $0.00006 $0.00406
Haiku 4.5 $0.00003 $0.00203

Measured 3d ago against content hash 868d29d1480b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

design-import scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

commands/design-import.md · 301 lines

How it starts

The opening of the file, as written. The whole thing — 301 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Plan Cascade - Import Design Document

Import an external design document and convert it to the unified design_doc.json format used by Plan Cascade.

Path Storage Modes

Design documents are user-visible files and remain in the working directory in both modes:

  • design_doc.json: Created in current working directory (project root or worktree)

This command does not use PathResolver since it works with user-provided paths and creates user-visible documentation files.

Supported Formats

Format Extensions Source
Markdown .md, .markdown Any markdown document
JSON .json Structured JSON documents
HTML .html, .htm Confluence/Notion exports

Tool Usage Policy (CRITICAL)

To avoid command confirmation prompts:

  1. Use Read tool for file reading - NEVER use cat via Bash

    • Read("design.md"), Read("architecture.html")
    • Bash("cat design.md")
  2. Use Write tool for file creation

    • Write("design_doc.json", content)
    • Bash("echo '...' > design_doc.json")

Step 1: Parse Arguments

Get the input file path from arguments:

INPUT_FILE="{{args}}"

If no file provided:

ERROR: Please provide a path to the design document to import.

Usage:
  /plan-cascade:design-import <path>

Examples:
  /plan-cascade:design-import docs/architecture.md
  /plan-cascade:design-import design-spec.json
  /plan-cascade:design-import confluence-export.html

Step 2: Read and Detect Format

Read the input file and detect its format:

content = Read(INPUT_FILE)

# Detect format from extension
if INPUT_FILE ends with .md or .markdown:
    FORMAT = "markdown"
elif INPUT_FILE ends with .json:
    FORMAT = "json"
elif INPUT_FILE ends with .html or .htm:
    FORMAT = "html"
else:
    FORMAT = "markdown"  # default

Step 3: Convert Based on Format

3.1: Markdown Conversion

Parse the markdown structure to extract design information:

Heading Mapping:

Markdown Heading Design Doc Section
# Title overview.title
## Overview/Summary/Introduction overview.summary
## Goals/Objectives overview.goals
## Non-Goals/Out of Scope overview.non_goals
## Architecture/Design architecture section
## Components/Modules architecture.components
## Patterns architecture.patterns
## Decisions/ADR decisions
## API/Endpoints interfaces.apis
## Data Models/Schema interfaces.data_models

Read the full file on GitHub · 301 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 3d ago First seen · 301 lines · 32 tokens per session scan A 868d29d1480b

Subscribe to this mod's changes

design-import is a command published in the GitHub repository Taoidle/plan-cascade (131 stars, last pushed 5mo ago), licensed MIT. It adds 32 tokens to every session and 2,030 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.