SNIPER

Spec In, Code Out

Describe your project. SNIPER produces a brief, PRD, architecture, UX spec, security analysis, epics, stories — then implements them all with parallel agent teams.

42 Expert Personas

Agents are composed from process, technical, and cognitive persona layers — architect + backend + systems-thinker — creating specialists for every task.

17 Pre-Built Teams

From 3-agent discovery squads to 5-agent sprint teams, every phase has a purpose-built team with file ownership and coordination rules.

Quality Gates

STRICT gates block until you approve. FLEXIBLE gates auto-advance with async review. 15 checklists ensure nothing ships without scrutiny.

Works on Any Codebase

Greenfield? Run /sniper-discover. Existing project? Run /sniper-ingest to reverse-engineer architecture and conventions, then iterate from there.

18 Slash Commands

Every phase is a single command. /sniper-plan spawns 4 agents that produce your PRD, architecture, UX spec, and security analysis in parallel.

Two Paths, One Framework

Whether you're starting from scratch or working with an existing codebase, SNIPER has a workflow for you.

Greenfield Projects

Full Lifecycle

Start with an idea. SNIPER's discovery team researches the market, assesses risks, and defines user personas. Then the planning team produces a PRD, architecture, UX spec, and security analysis. The solve phase shards everything into epics and stories. Finally, sprint teams implement story by story — with tests, PRs, and code review at every step.

→ /sniper-discover
→ /sniper-plan
→ /sniper-solve
→ /sniper-sprint

Existing Codebases

Ingest + Iterate

Already have code? SNIPER's ingest team reverse-engineers your architecture, extracts coding conventions, and produces a project brief from your source. From there, use /sniper-feature for scoped additions, /sniper-debug for structured bug investigation, or /sniper-audit for security, performance, and test coverage analysis.

→ /sniper-ingest
→ /sniper-feature
→ /sniper-debug
→ /sniper-audit

SNIPER In Action

Real terminal output from SNIPER orchestrating Claude Code agent teams.

SNIPER plan phase showing 4 agents coordinating on PRD, architecture, UX, and security — Plan phase: 4 agents coordinating on PRD, architecture, UX, and security

SNIPER solve phase showing story selection with dependencies — Solve phase: stories sharded with dependencies, sizes, and ownership

SNIPER sprint with frontend-dev and qa-engineer working in parallel — Sprint: parallel agents with task dependencies and coordination

Sprint complete with PR created and test results — Sprint complete: stories implemented, tests passing, PR created

The Spec Driven Workflow

Every artifact is a spec. Every spec drives the next phase. Nothing is implemented without a spec.

1. Discover

3 agents

An analyst, risk researcher, and user researcher work in parallel. They produce a project brief with competitive analysis, a risk assessment with mitigations, and user personas with journey maps.

2. Plan

4 agents · Opus

A product manager writes the PRD. Once complete, an architect, UX designer, and security analyst work in parallel — each reading the PRD and producing their own spec. STRICT gate: you approve before moving on.

3. Solve

1 agent

A scrum master reads the PRD, architecture, and UX spec, then shards everything into epics and self-contained stories. Each story embeds the relevant context from upstream specs so developers never need to cross-reference.

4. Sprint

2-5 agents