A command that imports a Spec Kit feature's tasks.md file into an AI software-development backlog. Spec Kit is a format for planning a software feature, and the file lists its work items.

Use it to add every task from a feature plan to the backlog, while detecting missing or unfamiliar task-file formats.

It turns planned work into separate backlog tasks and keeps each task linked to the original planning document.

import-spec — Command for Claude Code by ai-sdlc-framework/ai-sdlc

Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code

/plugin marketplace add ai-sdlc-framework/ai-sdlc

Claude Code

/plugin install ai-sdlc

Made for: Claude Code.

Or install ai-sdlc, the plugin that ships this one along with the rest of its 1 skill, 23 commands, 14 agents.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/commands/ai-sdlc-framework/ai-sdlc/import-spec/github.svg)](https://agentmods.dev/commands/ai-sdlc-framework/ai-sdlc/import-spec)

Your own site

<a href="https://agentmods.dev/commands/ai-sdlc-framework/ai-sdlc/import-spec"><img src="https://agentmods.dev/badge/commands/ai-sdlc-framework/ai-sdlc/import-spec/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/commands/ai-sdlc-framework/ai-sdlc/import-spec"><img src="https://agentmods.dev/badge/commands/ai-sdlc-framework/ai-sdlc/import-spec.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 48 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 889 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00048	$0.00889
Opus 5.5	$0.00019	$0.00356
Sonnet 5.5	$0.00010	$0.00178
Haiku 4.5	$0.00005	$0.00089

Measured today against content hash e637bb835544, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

import-spec 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 today.

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.

ai-sdlc-plugin/commands/import-spec.md · 75 lines

How it starts

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

Import a spec-kit feature into the AI-SDLC backlog. The spec-kit tasks.md at --from <path> is parsed; one backlog task is created per upstream task entry, each carrying a specRef: frontmatter block pointing back to the upstream artifact.

Per RFC-0036 OQ-1 + OQ-11 (resolved 2026-05-16)

tasks.md only. No fallback to spec.md. Missing tasks.md → Decision: incomplete-spec-detected is opened in the Decision Catalog and a clarification task is filed back in the backlog asking the operator to run /speckit.tasks upstream and re-run the import.
Auto-detect schema; refuse unknown. Unrecognised tasks.md layout → Decision: upstream-schema-unknown is opened + an upgrade-framework task is filed asking for parser support.

Phase scope (Phase 4 of RFC-0036)

✓ CLI + slash command
✓ specRef: back-references on every generated task
✗ DoR at import time (Phase 5 / AISDLC-330)
✗ Reconcile / drift handling (Phase 6 / AISDLC-331)

Usage

node "$PIPELINE_CLI_BIN/cli-import-spec.mjs" --from .specify/specs/<feature>/

$ARGUMENTS is the path. Accepts either the feature directory (containing tasks.md) or the tasks.md file directly.

ARGS="${ARGUMENTS:-}"
if [[ -z "$ARGS" ]]; then
  echo "Usage: /ai-sdlc import-spec --from <path-to-spec-kit-feature>"
  exit 1
fi

# Pass the operator's args straight through. `--from` is the only required
# flag; `--work-dir` defaults to cwd; `--format` defaults to text.
PLUGIN_SCRIPTS_DIR="${CLAUDE_PLUGIN_DIR:-${CLAUDE_PLUGIN_ROOT:-$(pwd)/ai-sdlc-plugin}}/scripts"
if [ -z "${PIPELINE_CLI_BIN:-}" ]; then
  PIPELINE_CLI_BIN=$(bash "$PLUGIN_SCRIPTS_DIR/resolve-pipeline-cli.sh") || exit 1
fi
node "$PIPELINE_CLI_BIN/cli-import-spec.mjs" $ARGS

Output

Imported: one line per task written, formatted as IMP-N (upstream T-NNN) → <path>.
Incomplete spec: the Decision id (DEC-NNNN) + path of the clarification task created in backlog/tasks/.
Unknown schema: same, but the clarification task asks for parser support rather than an upstream re-run.

Read the full file on GitHub · 75 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.

today Changed · +2 lines e637bb835544
5d ago Changed ac676cf39934
7d ago Changed · +4 lines 022b9589682e
8d ago Changed 36e808e7dbec
1mo ago First seen · 69 lines · 48 tokens per session scan A b3753b0bd1b5

Subscribe to this mod's changes

import-spec is a command published in the GitHub repository ai-sdlc-framework/ai-sdlc (415 stars, last pushed yesterday), licensed Apache-2.0. It adds 48 tokens to every session and 889 once invoked, about $0.0002 per session on Opus 5.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.

DevOps and cloud Go Project management ai-agents ai-coding-agents ai-governance developer-tools

import-spec

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Per RFC-0036 OQ-1 + OQ-11 (resolved 2026-05-16)

Phase scope (Phase 4 of RFC-0036)

Usage

Output

What this file has done since we first saw it

Other commands, from other repositories

backlog

service-assessment

plan

risk

evidence

gcloud-search