All Insights
#SpecDrivenDevelopment
August 2026

Sunday Coffee & Code: SDD (spec-kit) in Claude Code Web - Part3, Making It Portable

Part 1 got Spec Kit working inside Claude Code's web client. Part 2 ran the full pipeline against a brownfield repo, ending in a PR. This week: pulling the workflow out into a public seed - steveh250/spec-kit-seed.

By Steve Harris

๐—ฆ๐˜‚๐—ป๐—ฑ๐—ฎ๐˜† ๐—–๐—ผ๐—ณ๐—ณ๐—ฒ๐—ฒ & ๐—–๐—ผ๐—ฑ๐—ฒ: ๐—ฆ๐——๐—— (๐˜€๐—ฝ๐—ฒ๐—ฐ-๐—ธ๐—ถ๐˜) ๐—ถ๐—ป ๐—–๐—น๐—ฎ๐˜‚๐—ฑ๐—ฒ ๐—–๐—ผ๐—ฑ๐—ฒ ๐—ช๐—ฒ๐—ฏ โ€” ๐—ฃ๐—ฎ๐—ฟ๐˜ ๐Ÿฏ, ๐— ๐—ฎ๐—ธ๐—ถ๐—ป๐—ด ๐—œ๐˜ ๐—ฃ๐—ผ๐—ฟ๐˜๐—ฎ๐—ฏ๐—น๐—ฒ

Part 1 got Spec Kit working inside Claude Codeโ€™s web client. Part 2 ran the full pipeline against a brownfield repo, ending in a PR. This week: pulling the workflow out into a public seed - steveh250/spec-kit-seed.

๐—ช๐—ต๐—ฎ๐˜โ€™๐˜€ ๐—ถ๐—ป ๐—ถ๐˜: GitHubโ€™s Spec Kit repackaged as Claude skills plus their gate scripts and docs - the whole SDD pipeline (constitution โ†’ specify โ†’ clarify โ†’ plan โ†’ tasks โ†’ analyze โ†’ implement โ†’ converge) runnable from a browser-only Claude Code Web session. No terminal or CLI install required.

Getting it there wasnโ€™t a five-minute job. :)

๐——๐—ฒ๐˜๐—ฎ๐—ฐ๐—ต๐—ถ๐—ป๐—ด ๐—ถ๐˜ ๐—ณ๐—ฟ๐—ผ๐—บ ๐˜„๐—ต๐—ฒ๐—ฟ๐—ฒ ๐—ถ๐˜ ๐˜€๐˜๐—ฎ๐—ฟ๐˜๐—ฒ๐—ฑ

The workflow was proven inside the Part 2 brownfield repo - which means it was entangled with it. Extraction meant resetting to a genuinely clean state (constitution back to the unfilled template etc.) and scrubbing every trace of the source project. A verification check confirmed it: no references to the private repo, no local paths, no secrets or PII, all skills valid, doc links resolving, scripts executing. A fresh preflight test then reported exactly what a new user should see: still a template & start at constitution.

Ran into a small problems copying files into the new repo - no big deal really - let Claude Code take care of that.

๐—ง๐—ต๐—ถ๐—ป๐—ธ ๐—ฎ๐—ฏ๐—ผ๐˜‚๐˜ ๐—น๐—ถ๐—ฐ๐—ฒ๐—ป๐˜€๐—ถ๐—ป๐—ด

The seed redistributes adapted MIT licensed content - preserved GitHub, Inc.โ€™s notice. Claude fetched the actual upstream LICENSE at the pinned tag rather than guessing - it did the legwork with me answering some minor questions on usernames.

๐—ง๐—ต๐—ถ๐—ป๐—ด๐˜€ ๐—œ ๐—น๐—ฒ๐—ฎ๐—ฟ๐—ป๐—ฒ๐—ฑ

  • Extraction is real work: reset the state, scrub the source project, verify with a gate - donโ€™t just copy files out - obviously.
  • Dotfolders donโ€™t survive drag-and-drop. Verify the tree on the remote - basic stuf.
  • Attribution is part of shipping. Verify the upstream licence from the source at the version you pinned.

The seed: https://github.com/steveh250/spec-kit-seed

That wraps the spec-kit modification series - install it, run it end-to-end, carry it with you. If you take it for a spin, Iโ€™d like to hear where it fights you. Next step for me is to use it for real with a project.

Time to get back to drinking coffee.

๐—ง๐—ต๐—ถ๐—ป๐—ธ. ๐— ๐—ผ๐—ฑ๐—ฒ๐—น. ๐—”๐—ฐ๐˜.

Want to Discuss This Topic?

Steve is always happy to have a direct conversation.