Skip to main content
Longshot examples demonstrate how to structure projects using the framework’s spec-driven swarm execution model. Each example includes complete project specifications, agent configuration, and living documentation.

​
Available Examples

​
Basic Project Template

The foundational template for creating new Longshot projects. Includes all required documents with placeholders and guidance.
  • Path: examples/example/
  • Purpose: Bootstrap template for new projects
  • Key Files: SPEC.md, AGENTS.md, README.md, RUNBOOK.md, DECISIONS.md, ENTRY_POINT.md
View Basic Project →

​
Decagon Assistant

A full-stack conversational AI assistant built for the Decagon AI challenge. Demonstrates complex multi-document coordination for a production-ready Next.js application.
  • Stack: Next.js 14, TypeScript, PostgreSQL, Anthropic Claude API
  • Key Features: Real-time streaming, persistent memory, context retention
  • Deployment: Vercel
  • Timeline: 24 hours from first commit to deployed demo
View Decagon Assistant →

​
Minecraft Browser Edition

A browser-based Minecraft clone built with React Three Fiber. Shows how Longshot handles game development with complex 3D rendering and physics.
  • Stack: React, Three.js, React Three Fiber, TypeScript
  • Key Features: Procedural terrain, voxel rendering, physics, day/night cycle
  • Runtime: Fully client-side, offline-capable
  • Timeline: 1-2 hours swarm run
View Minecraft Browser →

​
Example Structure

Each Longshot project follows a consistent documentation structure:

​
Core Specification Files

SPEC.md

Product requirements, success criteria, acceptance tests, and scope boundaries

AGENTS.md

Execution policies, code style, dependencies, testing, and commit conventions

README.md

Quick start guide, setup commands, and demo flow

RUNBOOK.md

Operational procedures, monitoring, and recovery steps

​
Supporting Documents

DECISIONS.md

Architecture decisions with rationale and status tracking

ENTRY_POINT.md

Document ownership and update responsibilities

​
Bootstrapping New Projects

Longshot provides a plan-mode bootstrap process for creating new projects: 
mkdir -p target-repo/<project-name>
cp examples/example/*.md target-repo/<project-name>/

​
Bootstrap Workflow

1

Create Folder + Copy Templates

Create new project folder and copy template markdowns from the example directory.
2

Collect Inputs

Gather project name, high-level description, and known constraints (time, budget, stack).
3

Ask Required Questions

Structured questions in batches:
  • Product and success criteria
  • Acceptance tests and demo flows
  • Architecture and dependencies
  • Scope control (must-have, nice-to-have, out-of-scope)
  • Operations and reliability
4

Fill Files

Complete all template sections with specific project details, removing all placeholders.
5

Validate Quality Gates

Ensure no placeholders remain, acceptance tests are runnable, and all required sections are complete.

​
Quality Gates

Bootstrap is complete only when:
  • ✅ No placeholder tokens remain (<...> or TODO text)
  • ✅ SPEC.md has explicit acceptance tests with runnable commands
  • ✅ SPEC.md includes must-have, nice-to-have, and out-of-scope sections
  • ✅ AGENTS.md has concrete allowed/banned dependency policy
  • ✅ README.md can be followed from clean machine assumptions
  • ✅ RUNBOOK.md has restart and partial failure handling
  • ✅ DECISIONS.md has at least one active decision

​
Validation Command

rg -n "<.*>|TODO|TBD" target-repo/<project-name>/*.md
This should return no results when bootstrap is complete.

​
Document Ownership Model

​
Before First Swarm Run

DocumentOwnerPurpose
SPEC.mdUserProduct requirements and success criteria
AGENTS.mdUserExecution policies and conventions
README.mdTemplateInitial setup guide (agent updates)
RUNBOOK.mdTemplateInitial operations guide (agent updates)
DECISIONS.mdTemplateInitial architecture log (agent updates)

​
During Swarm Run

DocumentUpdatesAuthority
SPEC.mdAgent proposesUser approves
AGENTS.mdAgent proposesUser approves
README.mdAgent maintainsAgent owns
RUNBOOK.mdAgent maintainsAgent owns
DECISIONS.mdAgent maintainsAgent owns

​
File Translation Rules

When creating project documentation, distribute information using these rules:
  • “What and why” → SPEC.md
  • “How to execute work” → AGENTS.md
  • “How to run now” → README.md
  • “How to recover when broken” → RUNBOOK.md
  • “Why architecture choices were made” → DECISIONS.md
  • “Who owns which doc” → ENTRY_POINT.md
If a requirement appears in multiple files, keep one source of truth:
  • Product intent: SPEC.md
  • Execution policy: AGENTS.md
  • Operational steps: RUNBOOK.md

​
Next Steps

Basic Project Template

Learn the template structure and bootstrap process

Decagon Assistant

Full-stack AI assistant with streaming and persistence

Minecraft Browser

3D game development with React Three Fiber

Project Structure

Deep dive into project organization

Build docs developers (and LLMs) love

Get started for freeTalk to us