SDTK-SPEC — Plan & Specify Shipped

SDTK-SPEC owns the planning phase: it turns ideas into governed specifications through a PM → BA → ARCH → DEV → QA pipeline, scaffolds a traceable 17-file SDLC document set, and provides the orchestrator that routes every SDTK session.

• CLI: sdtk-spec (package sdtk-spec-kit)
• Full command list: sdtk-spec reference

What it does

• Orchestrator Intake — the default entry point for AI sessions. Classifies your request (raw idea vs. formal delivery vs. bounded task) and routes to the smallest sufficient workflow.
• Discovery gate — raw ideas become docs/discovery/REQUIREMENT_<FEATURE_KEY>.md and must reach READY_FOR_PM_INITIATION before PM starts.
• Phase pipeline — PM → BA → ARCH → DEV → QA role skills, each writing real artifacts with phase-gate transitions and end-to-end traceability.
• 17-file scaffold — sdtk-spec generate creates the full SDLC document set for a feature in one command.
• Atlas — a browsable knowledge graph/viewer over your spec artifacts.
• Project Intelligence Pro — ingest, audit, and refresh docs baselines for existing projects.

Get started

npm install -g sdtk-kit          # or: npm install -g sdtk-spec-kit
sdtk-spec init
sdtk-spec runtime install        # install skills for your runtime

Then in Claude Code:

/orchestrator
I want to build a lightweight CRM for solo consultants.

Scaffold a feature

sdtk-spec generate --feature-key CRM_LEADS --feature-name "Lead tracking"

Creates the 17-file SDLC set (PRD, BA docs, architecture, API design, screen specs, test cases, plans) wired for traceability.

Analyze an existing source

sdtk-spec analyze --source ./legacy-notes.md

Atlas: graph & viewer

sdtk-spec atlas init
sdtk-spec atlas build       # requires Python 3.8+
sdtk-spec atlas open
sdtk-spec atlas watch       # rebuild on change
sdtk-spec atlas status

Python only here

sdtk-spec atlas build needs Python 3.8+. The wiki's atlas (sdtk-wiki atlas build) is a native Node port with no Python requirement — see SDTK-WIKI.

Project Intelligence Pro

For existing codebases with thin docs:

sdtk-spec project ingest    # build a docs baseline from the code
sdtk-spec project audit     # find gaps and drift
sdtk-spec project refresh   # update the baseline as code evolves

Requires Pro activation (sdtk activate --license …); fails closed without an entitlement.

Skills installed

/orchestrator, /pm, /ba, /arch, /dev, /qa, plus sub-skills: /api-doc, /api-design-spec, /screen-design-spec, /design-layout, /test-case-spec, /dev-backend, /dev-frontend.

Boundaries

• The discovery artifact is a pre-PM clarification bridge — not a PRD or BA replacement.
• Phase gates are not skippable in formal delivery.
• analyze reads sources you point it at; it does not crawl the network.

Where to go next

Idea to ShipThe full pipeline SDTK-SPEC opens.

Command referenceEvery sdtk-spec command, option, and exit code.

Next phase: SDTK-DESIGNTurn the spec into screens and a prototype.