SDTK-CODE

Workflow-first coding execution after SDTK-SPEC handoff

SDTK-CODE is the public downstream coding product in the suite. It starts from formal handoff inputs, drives start -> plan -> build -> verify -> ship, and has already been validated end-to-end on a real Workflow project.

Public packageWorkflow-first CLIClaude + CodexReal Workflow validated

> ANATOMY OF A GOVERNED PR

Your AI doesn't just write code — it runs through five review gates before the PR is a PR.

Vibecoding is fast until it isn't. SDTK-CODE separates "AI typing on your behalf" from "PR ready to merge" with explicit gates between them. Each stage produces a concrete artifact you can read — so you can stop trusting blindly and start reviewing the evidence.

Without SDTK-CODE

AI starts coding from a vague paragraph in a chat
You skim the diff, hit merge, hope for the best
No record of what was actually reviewed
Next week you don't remember what you decided

With SDTK-CODE

Starts from CODE_HANDOFF.json — scope is explicit
Plan confirmed before any file changes
REVIEW_PACKET.md attached with concrete evidence
OPS_HANDOFF emitted so deployment owns the next step

Gate 1start
Reads CODE_HANDOFF from SPEC. Loads scope, files-to-touch, acceptance criteria.
Workflow state initialized — no code yet, just contract.
Gate 2plan
AI proposes file inventory + task order. You confirm the seeded candidates.
Plan locked. AI now knows exactly what it owns.
Gate 3build
Implementation with bounded edits. Tests written alongside the code, not at the end.
Code + unit tests, contained to planned scope.
Gate 4verify
Review gate runs: code-review skill checks against checklist, runs tests, surfaces gaps.
REVIEW_PACKET.md — explicit pass/fail with evidence.
Gate 5ship
Final closeout: bundles preflight checks, emits OPS_HANDOFF for downstream deployment.
docs/dev/OPS_HANDOFF_<FEATURE>.json — SDTK-OPS can pick up.

When a solo founder reaches for this

Sunday morning. Spec is locked, design is reviewed. You want code, but not vibecoding — you want a PR you can actually read. sdtk-code start reads the handoff, plan locks scope, build stays inside the plan, verify produces a REVIEW_PACKET.md, ship emits OPS_HANDOFF. Hours later you have a feature with evidence, not just a diff.

Product truth

What this toolkit does today

These cards summarize the current shipped or internal surface exactly as it exists in the local source tree.

Public package surface

The shipped public package is sdtk-code-kit with the sdtk-code CLI. The core public workflow surface is start, plan, build, verify, and ship, with init/update/runtime/help/version support around it.

Formal handoff intake

SDTK-CODE sits downstream from SDTK-SPEC. It expects CODE_HANDOFF first, then falls back to bounded compatibility inputs only when the formal handoff file is missing and the remaining source set is sufficient.

Usability-hardened closeout

The current local source already hardened seeded-candidate plan adoption, finish vs ship guidance, final closeout rendering, and stronger ship-closeout bundle handling.

Current command and workflow surface

Workflow commands

sdtk-code start

sdtk-code plan

sdtk-code build

sdtk-code verify

sdtk-code ship

Support commands

sdtk-code init

sdtk-code update

sdtk-code runtime install

sdtk-code runtime status

sdtk-code runtime uninstall

sdtk-code help

sdtk-code --version

Current workflow truth

plan --use-seeded-candidates confirms seeded handoff slices explicitly

feature-lane finish expects a stronger closeout bundle than bugfix-lane finish

ship is the stronger closure decision and uses multi-preflight bundles

Runtime support

Runtime	Project	User	Notes
Claude	Yes	Yes	Installs code-* skills and supports project-local workflow use.
Codex	Yes	Yes	Default scope is user; project-local installs require the explicit local CODEX_HOME=<project>/.codex contract.

Validated truth

Validated on a real Workflow project through start -> plan -> build -> verify -> ship (finish).
Stage B pilot flow proved UI -> API -> PostgreSQL -> list refresh on both codex and claude runtimes.
Pre-ship hardening review tightened auth/settings truth before bounded finish closeout.
Final workflow closeout now persists nextPhase = none instead of leaving a stale actionable state.

Boundaries and honest limits

SDTK-CODE does not replace upstream specification, handoff generation, or SDTK-SPEC planning phases.
generate is not part of the current public SDTK-CODE CLI surface.
Codex project-local runtime installation is supported only through the explicit local CODEX_HOME=<project>/.codex contract; native .codex/skills auto-discovery is not claimed.
Workflow proof exists for a bounded pilot slice, not for every possible product topology.
`runtime uninstall` removes only SDTK-CODE-managed skill folders for the selected runtime and scope; `npm uninstall -g sdtk-code-kit` removes the package only.

Source-of-truth docs

Canonical usage guide

products/sdtk-code/governance/SDTKCODE_TOOLKIT_USAGE_GUIDE.md

Step-by-step install, runtime setup, workflow usage, finish vs ship guidance, and troubleshooting.

Package landing page

products/sdtk-code/distribution/sdtk-code-kit/README.md

npm-facing package truth for sdtk-code-kit, including command surface and upstream dependency boundary.

Workflow contract

products/sdtk-code/governance/workflow-contract.md

Artifact-level contract for workflow state, evidence capture, and closeout semantics.

Boundary doc

products/sdtk-code/toolkit/SDTKCODE_TOOLKIT.md

Suite-level product boundary, architecture framing, and companion-document map.

Position in the SDTK control plane

Where SDTK-CODE sits in the chain

SDTK-CODE is the DEV implementation pack. It consumes CODE_HANDOFF from SPEC, produces verified code + review evidence, and emits OPS_HANDOFF for downstream operations.

Orch—
PM—
BA—
ARCH—
DEVuses
QAuses

Highlighted owners actively use SDTK-CODE as their execution pack.

Family links

Move across the SDTK suite without losing context

These product pages map the current suite boundaries so users can move from specification to coding to operations deliberately.

Upstream