SDTK

> FOR SOLO FOUNDERS BUILDING SIDE BUSINESSES AT NIGHT

Turn 6 weekend hours into a shipped MVP, not another restart.

SDTK gives your nights and weekends an AI-native operating system — so the progress you make tonight still compounds next week.

  1. IDEA
  2. SPEC
  3. DESIGN
  4. CODE
  5. SHIP
  6. REMEMBER
Get Started - 90 secSee a weekend in SDTK

Built for solo founders shipping in limited time 100% local Your project context survives between sessions

The SDLC chain your AI runs through — click any node to explore

SDTK Knowledge Graph

The full pipeline, five agents wiring 17 artifact templates together.

  1. PM - Product

    3 docs
    PROJECT_INITIATIONPRDBACKLOG

  2. BA - Business

    2 docs
    BA_SPECFLOW_ACTION_SPEC

  3. ARCH - Architect

    5 docs
    ARCH_DESIGNDATABASE_SPECDESIGN_LAYOUTAPI_ENDPOINTSAPI_DESIGN_DETAIL

  4. DEV - Dev Plan

    3 docs
    FEATURE_IMPL_PLANCODE_WORKFLOWREVIEW_PACKET

  5. QA - Testing

    4 docs
    TEST_CASESQA_RELEASE_REPORTCONTROLLER_ACCEPTANCERELEASE_NOTES

  1. CONTROL

    Orchestrator·Routes

  2. SPEC

    PM·Product

  3. SPEC

    BA·Business

  4. SPEC

    ARCH·Architect

  5. BRIDGE

    DEV·Spec · Code · Ops

  6. RELEASE

    QA·Testing

> ONE CONTROL PLANE. THREE EXECUTION PACKS.

The architecture nobody else ships: a real SDLC chain, not a chat thread.

SDTK gives your AI the same operating model that Google, Microsoft, and Apple use internally: one orchestrator routes work through PM → BA → ARCH → DEV → QA, and each owner picks the right execution pack. DEV is the bridge that spans planning, coding, and operations. QA closes the loop with evidence from all three.

> THE SOLO FOUNDER PROBLEM

Your nights look like this.

  • Friday you had a plan. Monday you spend 45 min figuring out where you stopped.
  • Your AI chat forgot the spec. Your repo forgot the decisions. Nothing connects.
  • You started coding without a spec because there was no time — now the MVP drifts.
  • Every side-project session starts with re-orienting instead of shipping.

> ONE FEATURE, ONE WEEKEND

Friday-night idea. Monday-morning ship. Nothing lost in between.

Six moves across one weekend. Every artifact stays in your repo.

  1. FRI 22:00

    Capture

    docs/discovery/REQUIREMENT_<FEATURE>.md

    SDTK-SPEC discovery
  2. SAT 09:00

    Plan

    PRD + BA_SPEC + ARCH_DESIGN + API_YAML

    SDTK-SPEC
  3. SAT 14:00

    Prototype

    docs/design/prototype/index.html

    SDTK-DESIGN
  4. SUN 10:00

    Build

    PR + REVIEW_PACKET

    SDTK-CODE
  5. SUN 21:00

    Ship

    Release runbook + smoke report

    SDTK-OPS
  6. NEXT FRI —

    Remember

    wiki/ + decision log + local query

    SDTK-WIKI

> ARTIFACTS, NOT CHAT HISTORY

What you actually get — real files in your repo, not lost messages.

Every SDTK phase writes concrete artifacts to your project tree. Click a tab to see a real sample of what lands on disk.

Generated path

docs/product/PRD_ORDER_TRACKING.md

PM phase output: goals, scope, success metrics — written from the discovery brief.

Produced by SDTK-SPEC
PRD_ORDER_TRACKING.md
# PRD: Order Tracking

## Goal
Reduce "where is my order" support tickets by 40%
via customer self-serve tracking.

## Success metrics
- Tracking page p95 load < 500 ms
- 70%+ of tracking inquiries deflected from support
- Zero PII leak in tracking page

## Scope
- In: customer self-serve tracking page, status polling
- Out: carrier-side integration, refund flow

All artifacts live in your repo. None of this leaves your machine.

> FIVE LOCAL TOOLKITS, EACH WITH A JOB

Each toolkit owns one phase of your weekend. Together, they cover idea to ship.

SDTK-SPEC

v0.4.7 + MIT

Your PM, BA, Architect, and QA — as installable skills

Sample output

17-file scaffold + PM-QA gates

Learn more ->

SDTK-DESIGN

v0.3.0 + MIT

Static MVP prototype your code agent can hand off to

Sample output

docs/design + prototype + handoff

Learn more ->

SDTK-CODE

v0.1.3 + MIT

Governed coding — your PR is reviewed before it's a PR

Sample output

Verified PR + review evidence

Learn more ->

SDTK-OPS

v0.2.4 + MIT

Deploy with a runbook + smoke + sign-off in one flow

Sample output

Release runbook + smoke report

Learn more ->

SDTK-WIKI

v0.1.4 + MIT

Your project memory — so next weekend doesn't start from zero

Sample output

wiki/ + graph + local query

Learn more ->

> QUICKSTART

From zero to scaffold in 90 seconds.

Runtime:
  1. 01
    $ npm install -g sdtk-kit

    Installs all five SDTK toolkits in one command

  2. 02
    $ sdtk-spec init --runtime claude

    Scaffolds 14 skill bundles + governance docs

  3. 03
    $ sdtk-spec generate --feature-key ORDER_TRACKING

    Produces 17 traceable spec files, ready for /pm phase

Full install guide ->

Built for solo founders shipping side businesses on Claude Code or Codex.

14 skills·17-file scaffold·5 phase gates·100% local

FAQ

Answers before you install

It's the opposite. SDTK exists because 6 hours is not enough to also rebuild context every session. The 17-file scaffold + local wiki are how those 6 hours compound week over week instead of resetting. You don't need to use every skill — start with SDTK-SPEC and SDTK-WIKI on weekend one.

> YOUR NEXT WEEKEND, BUT IT COMPOUNDS

Stop restarting from scratch. Give your nights and weekends the structure they need to ship.

Get Started - 90 secRead the docs ->