AI-powered SDLC documentation and project intelligence
SDTK-SPEC scaffolds the upstream artifact chain first, adds a free local Atlas document graph, and unlocks premium project ingest, audit, and refresh workflows before downstream coding handoff into SDTK-CODE.
When a solo founder reaches for this
Saturday morning. You have a one-line MVP idea from last night. You need a real plan — PRD, BA spec, architecture, API design — before you waste the weekend coding the wrong thing. Run sdtk-spec generate and 5 roles fill the scaffold in order. By lunch, you have something an AI coder can actually implement.
> YOUR INSTALLABLE PRODUCT TEAM
SDTK-SPEC installs 5 specialist roles that run sequentially with explicit handoffs. No more skipping straight to code with a vague brief. Each role produces a concrete file that the next role consumes — so the chain stays traceable from a one-line idea to a release-ready sign-off.
Step 1
PM
Frames the project — goals, scope, stakeholders, success criteria.
Produces
PROJECT_INITIATION.md
Hands off to: BA
## Goals - Reduce order-tracking support tickets by 40% ## Scope - In: customer self-serve tracking - Out: carrier-side integrations
Step 2
BA
Turns goals into use cases, business rules, and acceptance criteria.
Produces
BA_SPEC.md
Hands off to: ARCH
## UC-01 View live order status Actor: Customer Precondition: Order exists Flow: 1) open tracking page 2) enter order ID … Acceptance: status, ETA, last update visible
Step 3
ARCH
Designs the system: APIs, DB schema, flows, integration boundaries.
Produces
OrderTracking_API.yaml
Hands off to: DEV
/api/v1/orders/{id}/status:
get:
responses:
'200':
schema: { $ref: '#/Order' }
'404':
$ref: '#/NotFound'Step 4
DEV
Plans the implementation: file inventory, task split, code handoff packet.
Produces
FEATURE_IMPL_PLAN_ORDER_TRACKING.md
Hands off to: QA
## Files to change - app/api/orders/status/route.ts (new) - lib/orders/tracking.ts (new) - tests/orders.spec.ts (new) ## Task order: schema → handler → tests → wiring
Step 5
QA
Writes test cases, runs the suite, makes the release decision.
Produces
TEST_CASES.md + RELEASE_SIGNOFF.md
→ Release
## TC-01 Track valid order Given order ID 'ORD-123' … When GET /api/v1/orders/ORD-123/status Then 200 + status, ETA in body ## Release sign-off: APPROVED
Core capability
The product surface stays honest: scaffold first, then phase-by-phase enrichment with explicit quality contracts.
Run PM, BA, ARCH, DEV planning, and QA with 14 core SDTK-SPEC skills, shared planning, mandatory phase order, and bounded mailbox delegation.
Every completion claim requires fresh command evidence, and DEV/QA handoffs enforce two-stage review gates.
The shipped upstream product includes a canonical catalog for the 14 core SDTK-SPEC skills so runtime/docs drift stays visible.
PM, BA, ARCH, DEV, and QA transitions use standard templates to reduce ambiguity before the next phase starts.
One feature command creates the 17-file scaffold contract, then teams enrich the artifacts phase-by-phase.
Build a local markdown knowledge graph under .sdtk/atlas/, open it in the browser, and keep it project-local by default.
From Django, Laravel, React, FastAPI, Flask and more — extract API routes, database schema, dependencies, and env vars into 9 staged docs with file:line references. Zero existing docs required.
Public example packs document enterprise CRUD, API-only, admin flow-action, and bugfix/hotfix workflows.
Maintainers can verify Claude or Codex runtime readiness before support, testing, or release validation.
The current shipped runtimes are Claude Code and Codex, with an explicit scope matrix and shared toolkit core.
Keep every artifact in Git so PR review, version history, and traceability remain first-class.
How it works
The workflow stays intentionally CLI-first so teams can automate, audit, and rerun the scaffold without overclaiming one-shot full-pipeline generation.
Install sdtk-spec-kit globally once on your machine.
Initialize the project for Claude or Codex and write the runtime guidance files.
Create the 17-file SDLC scaffold contract for your product/MVP (or a single feature), or branch into the Atlas / premium project lane after initialization.
Drive PM, BA, ARCH, DEV planning, and QA in SDTK-SPEC, or use Atlas plus premium ingest/audit/refresh before downstream implementation handoff into SDTK-CODE.
Deliverables
These examples reflect the current scaffold contract, shared planning flow, and review discipline so teams can inspect them directly in Git.
Phase tracker, owners, blockers, and handoff status across the current SDTK-SPEC upstream workflow and handoff boundary.
# SHARED_PLANNING
Current phase: ARCH
Next handoff: DEV
Open blockers: 1
Quality gate status: BA PASS, PM PASSPosition in the SDTK control plane
SDTK-SPEC is the execution pack used by PM, BA, ARCH, and DEV-Plan. It is the planning surface every other pack hands off to or from.
Highlighted owners actively use SDTK-SPEC as their execution pack.
Companion products
Once SDTK-SPEC has produced your 17-file scaffold and CODE_HANDOFF, the rest of the suite picks up: DESIGN turns it into a reviewable prototype, CODE implements it, OPS deploys it, and WIKI remembers all of it.
Turn the SPEC handoff into a static reviewable MVP prototype before code starts.
Open page ->PublicConsume CODE_HANDOFF and run governed start → plan → build → verify → ship.
Open page ->PublicPick up OPS_HANDOFF from CODE for deploy, smoke, and operational verification.
Open page ->PublicThe memory layer that remembers everything SPEC produced across sessions.
Open page ->Pricing
Free is available now. Pro checkout is live via Lemon Squeezy.
$0
Start with the public SDTK toolkit, local Atlas graph compatibility, and the SDTK-WIKI project memory layer.
Popular next
$39
One-time purchase with activation-key unlock
Enterprise rollout
Enterprise support is handled as a sales conversation, not as a separate public account tier. Start with Pro for self-serve access, or contact us if your team needs rollout planning.
Built for engineers who need AI-assisted work they can audit — on Claude Code or Codex.
6 toolkits·17-file scaffold·5 phase gates·local-first ledger
> GOVERNED. AUDITABLE. RESUMABLE.