Eye of the Storm
Archive
Series

Research, in arcs

AI Basics16 posts
A ground-up introduction to working with AI tools — from prompting fundamentals to integrating AI into your development workflow.
Building in Public2 posts
Behind-the-scenes posts on how this devblog gets built — workflow, tooling, and the decisions behind the decisions.
LLM Driven SDLC1 post
How large language models are reshaping every phase of the software development lifecycle — from requirements and planning through implementation, review, testing, and deployment. A practitioner's view of what actually changes when AI enters the loop.
AI Engineering Research2 posts
Deep-dive research notes on building AI-powered tools — from designing LLM-driven requirements generators to understanding architecture, inference, and production AI systems.
On GitHub

Projects in flight

codagatchiTypeScript
A tamagotchi-style desktop pet built with Tauri — a small always-on-top companion whose stats decay in real time and need tending.
groundworkTypeScript
SDLC discipline plugin for Claude Code — requirements, plans, and structured development workflows.
— Updated as projects evolveAll research & projects
GalleryActivityAbout
GitHubXRSS
© 2026 stormbreaker9000 · charted with care
Projects

// project

groundwork

My attempt at making a claude code plugin that helps users adhere to a set of SDLC standards

★ 1 · ⑂ 0 · ● 0 open
Pythonpushed 2026-09-26T19:10:37ZView on GitHub ↗

README

groundwork — the stages before the code gets written

groundwork

A Claude Code plugin that brings structure to software development — requirements gathering, planning, and SDLC discipline before you write a line of code.

Built as an alternative to "vibe coding": lay the groundwork first.

What it does

Groundwork intercepts vague implementation requests and guides you through a lightweight requirements process before anything gets built. Instead of jumping straight to code, you get atomic, validated requirement artifacts — each with a rationale and a fit criterion — that both you and Claude agree on before implementation starts.

Installation

From Claude Code:

/plugin marketplace add https://github.com/Stormbreaker9000/groundwork

Then install the plugin:

/plugin install groundwork@groundwork-dev

Usage

Run /groundwork in any Claude Code session to see available workflows.

When you make a vague request like "build me a login form" or "add dark mode", the requirements skill will pause and ask clarifying questions before touching code.

Workflows

WorkflowTriggerDescription
requirements"build X", "add Y", "make it do Z"Turns a vague request into atomic, validated requirement artifacts under .sdlc/requirements/ — functional and non-functional requirements, constraints, business rules, assumptions, a glossary and a Definition of Done
designa validated requirement set existsTurns requirements into an architecture under .sdlc/design/ — components, interface contracts, MADR architecture decision records and C4 diagrams, each traced back to the requirements that motivated it

Claude will not write code until you sign off.

Documentation

Full documentation, including the content-rule reference, is published from this repository to https://stormbreaker9000.github.io/groundwork/.

Previewing the site locally

The site is built with a /groundwork base path, so plain http://localhost:3000/ returns a 404 — open /groundwork/ instead.

cd site
npm install     # first time only
npm run dev     # http://localhost:3000/groundwork/

The Pagefind search index is produced by the postbuild step, not by , so site search returns nothing under . To preview the exact static output that gets deployed, build it and serve it from a directory where it sits under :

Read the full README on GitHub ↗

Recent Commits

  • f71e79ffeat(sto-309): regenerate the worked example DoDs at the set root (PR 1 …Mark D'Adamo · Sep 26
  • bd5ddaffeat(sto-307): QA stage shape adjustments — two registers, a renamed sea…Mark D'Adamo · Sep 17
  • 7911198feat(sto-104): the Definition of Done generator — a script at the root o…Mark D'Adamo · Sep 12
  • 8ac1360feat(sto-103): the QA strategy stage — atomic TS- artifacts, a projected…Mark D'Adamo · Sep 07
  • 096e233refactor(sto-257): move the plugin runtime under plugin/ so docs and fix…Mark D'Adamo · Sep 06
  • 5e0bd92feat(sto-220): the architecture guide — stage map, generated hand-off co…Mark D'Adamo · Sep 06
  • d5f2433feat(sto-250): the user guide — five prose pages, three generated refere…Mark D'Adamo · Sep 05
  • f9e0706feat(sto-250): docs site skeleton — Nextra on GitHub Pages, with a gener…Mark D'Adamo · Sep 04

Related Posts

  • Groundwork Dev Log 2: Closing the Gaps the Tamagotchi FoundJul 13A while back I ran a desktop tamagotchi through Groundwork's requirements workflow and wrote down everything it got wrong. This is the re-run — same pet, same prompt, after building the fixes.
  • Dev Log: Building GroundworkJun 11Dogfooding Groundwork's requirements workflow on Codagatchi: the baseline it generated, and — graded against my requirements research — exactly where the gaps are to fix next.
next dev
npm run dev
groundwork/