Start where the work starts.
Point to the most likely file. The brief begins with a real touchpoint, not a vague question about the whole repository.
↳src/services/checkout.ts
Open source · local first · Build Week 2026
Know the shape of a change before you make it.
StackBrief gives you a source-cited architectural brief before you edit code—or hand the work to an agent.
Public repository metrics · refreshed hourly
Offline analysisSource-citedAgent-neutral
route service change signal
The point of a brief
Documentation tells you what a system was. StackBrief helps you see what a change touches.
Not to slow a developer down. To make the consequences visible while there is still time to choose well.
A project with an origin
It started as a developer skill called stack.md.
Its first job was simple: help someone understand the technology stack in an unfamiliar repository. Repeated use exposed a larger problem.
READMEs drift. Architecture lives in people’s heads. The knowledge needed before a change is scattered across files, dependencies, routes, and runtime assumptions.
The rest, as they say, is history.
Read the launch postA daily practice, not a ceremony
Find the file. Read the shape. Make the change.
StackBrief belongs between “I think this is the place” and your first edit. The result is small enough to use every day—and grounded enough to inspect.
See the architecture around it.
Routes, services, databases, external APIs, affected files, and static unknowns—each carried with source evidence.
POST /api/checkoutBilling gateway via client.tsPostgreSQL
Change with intent.
Use the brief to choose the implementation and a review checklist. Keep runtime and product questions where they belong: with the developer.
human judgement
stays in the loop
stays in the loop
A short visual walkthrough
See the brief before the edit.
Follow a generic checkout change from its starting file to the architectural context around it—routes, data boundaries, dependencies, and the questions static analysis should leave visible.
32 seconds · rendered locally with Remotion · no repository data leaves the machine
The video shows a local StackBrief brief for a generic checkout file, including source-cited architecture and explicit static unknowns.
The home is still your terminal
A clear thought, right next to the code.
StackBrief makes no network request to analyze your repository. It keeps the evidence local and leaves runtime decisions with the developer.
stackbrief — sample-repository
$ stackbrief brief --file src/services/checkout.ts
StackBrief: src/services/checkout.ts
RELEVANT ARCHITECTURE
RoutePOST /api/checkout
APIBilling gateway via src/lib/billing/client.ts
DataPostgreSQL
UNKNOWN
○ Verify runtime configuration and production traffic separately.
$
01
Use the CLI
npx @blindspotlab/stackbrief brief --file <path>02
Bring your own agent
stackbrief agent install --path .agents/skillsA shared reference point
For anyone who needs to know before they go.
The new contributor
Find a sensible entry point and understand the constraints without spending days reconstructing the codebase from memory.
The long-time maintainer
Bring the hidden coupling around a change into view before the simple-looking edit becomes a production surprise.
The coding agent
Give an agent evidence before a prompt becomes a patch. StackBrief is agent-neutral by design, not locked to one model or tool.
Built by a practitioner
Built by Mojeeb Titilayo, for the moment before the code changes.
Mojeeb is an AI Product Engineer and founder of BlindspotLab—a historian turned builder who has shipped 30+ products across AI, developer tools, SaaS, and Web3.
StackBrief emerged from repository work, architectural review, and a simple requirement: the right context should be available before the edit.
2026
The genesis chapter
The first public release took shape during OpenAI Build Week 2026.
GPT-5.6 challenged the product and architecture; Codex accelerated implementation, tests, release preparation, and documentation. Engineering judgement remained with the maintainer.
From the origin postMake the map stronger
If it earns a place in your workflow, leave a mark.
Star the repository Evaluate the build Review on npm
Want to contribute a detector, framework adapter, or a better idea? Write to hello@mojeeb.xyz.