gitwtfhub

wtf is blizzard-discovery?

paul-gross/blizzard-discovery — explained in plain English

Analysis updated 2026-05-18

0HTMLAudience · pm founderComplexity · 1/5Setup · easy

TL;DR

A written design and planning corpus, with no code yet, for a proposed platform that runs a fleet of autonomous coding agents.

Mindmap

mindmap
  root((blizzard-discovery))
    What it does
      Design corpus
      No code yet
      Decision log
      Open questions
    Tech stack
      Markdown docs
      Claude Code
      GitHub issues
    Use cases
      Agent fleet design
      Cold review
      Planning reference
    Audience
      PMs and founders
      Architects

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

Why would anyone build with this?

REASON 1

Read the mission, personas, and MVP documents to understand a proposed AI agent orchestration platform

REASON 2

Review the decision log to see what design choices have already been settled

REASON 3

Cross-check the design proposal from a cold start as an outside reviewer or AI tool

REASON 4

Study the architecture and workflow-engine documents before an implementation begins

What's in the stack?

MarkdownClaude CodeGitHub Issues

How it stacks up

paul-gross/blizzard-discovery100/rutgers-pbl-dining-2015a15n/a15n_old
Stars0
LanguageHTMLHTMLHTML
Last pushed2015-12-012016-06-18
MaintenanceDormantDormant
Setup difficultyeasyeasyeasy
Complexity1/51/51/5
Audiencepm foundergeneralgeneral

Figures from each repo's GitHub metadata at analysis time.

How do you spin it up?

Difficulty · easy Time to first run · 5min

There is no code to run, this repository is a documentation and planning corpus only.

Wtf does this do

blizzard-discovery is not a working piece of software. It is a written design and planning corpus for a future project called blizzard, which aims to be a platform that runs a fleet of AI coding agents continuously on local machines. The idea behind blizzard is that work would flow in from a backlog, each task would run unattended in its own isolated environment, finished work would be merged automatically or held for a human to approve where that is configured, and a human would only be pulled in when an agent genuinely gets stuck. The repository states plainly that it contains no code. Instead it exists so the design can be written out, refined, and reviewed cold by other AI tools and by human reviewers before any building starts. Every document in the repository is described as a proposal rather than a finished decision. Settled choices are tracked in a decision log, while ideas still being debated are tracked separately as open questions, so a new reader can question the design rather than assume it is already final. The corpus is organized into five kinds of documents. Product documents describe what blizzard is for and who it serves. Design documents describe how the pieces would work, covering things like the workflow engine, how multiple agents would avoid conflicting with each other, and how the system would talk to different coding tools. Research documents record what the authors learned by studying similar existing projects. Decision documents track what has been settled versus what is still open. Implementation documents describe how the eventual build would be organized. The guiding philosophy stated in the README is that the core control logic of the system should be ordinary, predictable code, and that AI models would only be asked to make judgment calls at specific, well defined points rather than running the whole process. The project is planned to use a companion tool called winter for isolating work environments across multiple repositories, along with GitHub issues and pull requests, and Claude Code as the coding tool that actually does the work.

Yoink these prompts

Prompt 1
Summarize what problem blizzard is trying to solve based on the mission document
Prompt 2
Walk me through the recommended reading order for this design corpus
Prompt 3
Explain the difference between the decision log and the open questions document
Prompt 4
What is the deterministic shell, intelligent core philosophy described in this repo

Frequently asked questions

wtf is blizzard-discovery?

A written design and planning corpus, with no code yet, for a proposed platform that runs a fleet of autonomous coding agents.

What language is blizzard-discovery written in?

Mainly HTML. The stack also includes Markdown, Claude Code, GitHub Issues.

How hard is blizzard-discovery to set up?

Setup difficulty is rated easy, with roughly 5min to a first successful run.

Who is blizzard-discovery for?

Mainly pm founder.

View the repo → Decode another repo

This repo across BitVibe Labs

Don't trust strangers blindly. Verify against the repo.