@sniper.ai/core 1.0.0

package/framework/teams/doc.yaml

@@ -0,0 +1,76 @@
+team_name: sniper-doc
+phase: doc
+
+teammates:
+  - name: doc-analyst
+    compose:
+      process: doc-analyst
+      technical: null
+      cognitive: user-empathetic
+      domain: from-config
+    tasks:
+      - id: analyze-project
+        name: "Analyze Project Structure & Artifacts"
+        output: "docs/.sniper-doc-index.json"
+        description: >
+          Scan the codebase and SNIPER artifacts. Produce a documentation
+          index: what exists, what's missing, what's stale. Map source
+          files to documentation topics. Detect whether this is a SNIPER
+          project (has .sniper/config.yaml with completed phases) or a
+          standalone project (codebase analysis only).
+
+  - name: doc-writer
+    compose:
+      process: doc-writer
+      technical: from-config
+      cognitive: mentor-explainer
+      domain: from-config
+    tasks:
+      - id: write-readme
+        name: "Generate README.md"
+        output: "README.md"
+        template: ".sniper/templates/doc-readme.md"
+        blocked_by: [analyze-project]
+        description: >
+          Write the project README from artifacts and codebase analysis.
+          Include: overview, quick start, features, tech stack, project
+          structure, contributing link, license. Use the doc index to
+          determine what sources to read.
+
+      - id: write-guides
+        name: "Generate Documentation Guides"
+        output: "docs/"
+        template: ".sniper/templates/doc-guide.md"
+        blocked_by: [analyze-project]
+        description: >
+          Generate the documentation files requested by the user (setup,
+          architecture, API, deployment, etc.) based on the doc index.
+          Each guide follows the doc-guide template. Use the doc index
+          to determine which guides to generate and what sources to read.
+
+  - name: doc-reviewer
+    compose:
+      process: doc-reviewer
+      technical: null
+      cognitive: devils-advocate
+      domain: null
+    tasks:
+      - id: review-docs
+        name: "Review & Validate Documentation"
+        output: "docs/.sniper-doc-review.md"
+        blocked_by: [write-readme, write-guides]
+        description: >
+          Review all generated docs for accuracy, completeness, and
+          consistency. Verify code examples compile, links resolve,
+          and setup instructions actually work. Produce a review report
+          with PASS/WARN/FAIL for each file.
+
+coordination:
+  - from: doc-analyst
+    to: doc-writer
+    trigger: analyze-project.complete
+    message: "Doc index ready at docs/.sniper-doc-index.json — read it to see what to generate"
+
+review_gate:
+  checklist: ".sniper/checklists/doc-review.md"
+  mode: flexible

package/framework/teams/plan.yaml

@@ -0,0 +1,86 @@
+team_name: sniper-plan
+phase: plan
+model_override: opus
+
+teammates:
+  - name: product-manager
+    compose:
+      process: product-manager
+      technical: api-design
+      cognitive: systems-thinker
+      domain: null
+    tasks:
+      - id: prd
+        name: "Product Requirements Document"
+        output: "docs/prd.md"
+        template: ".sniper/templates/prd.md"
+        reads: ["docs/brief.md", "docs/personas.md", "docs/risks.md"]
+        description: >
+          Write a comprehensive PRD covering: problem statement, user stories,
+          feature requirements (P0/P1/P2), success metrics, constraints,
+          and out-of-scope items. This is the single source of truth for what to build.
+
+  - name: architect
+    compose:
+      process: architect
+      technical: backend
+      cognitive: security-first
+      domain: null
+    tasks:
+      - id: architecture
+        name: "System Architecture Document"
+        output: "docs/architecture.md"
+        template: ".sniper/templates/architecture.md"
+        reads: ["docs/prd.md", "docs/brief.md", "docs/risks.md"]
+        blocked_by: [prd]
+        plan_approval: true
+        description: >
+          Design the complete system architecture. Include: component diagram,
+          data models, API contracts, infrastructure topology, technology choices
+          with rationale, and non-functional requirements.
+
+  - name: ux-designer
+    compose:
+      process: ux-designer
+      technical: frontend
+      cognitive: user-empathetic
+      domain: null
+    tasks:
+      - id: ux-spec
+        name: "UX Specification"
+        output: "docs/ux-spec.md"
+        template: ".sniper/templates/ux-spec.md"
+        reads: ["docs/prd.md", "docs/personas.md"]
+        blocked_by: [prd]
+        description: >
+          Define the UX: information architecture, screen inventory,
+          key user flows (with decision trees), component hierarchy,
+          interaction patterns, and responsive breakpoints.
+
+  - name: security-analyst
+    compose:
+      process: architect
+      technical: security
+      cognitive: security-first
+      domain: null
+    tasks:
+      - id: security
+        name: "Security & Compliance Requirements"
+        output: "docs/security.md"
+        template: ".sniper/templates/security.md"
+        reads: ["docs/prd.md", "docs/risks.md"]
+        blocked_by: [prd]
+        description: >
+          Define security architecture: auth model, data encryption strategy,
+          compliance requirements (with specific regulations), threat model,
+          and security testing requirements.
+
+coordination:
+  - between: [architect, security-analyst]
+    topic: "Align security architecture with system architecture"
+  - between: [architect, ux-designer]
+    topic: "Align frontend component boundaries with backend API contracts"
+
+review_gate:
+  checklist: ".sniper/checklists/plan-review.md"
+  mode: strict

package/framework/teams/solve.yaml

@@ -0,0 +1,48 @@
+team_name: null
+phase: solve
+
+agent:
+  compose:
+    process: scrum-master
+    technical: null
+    cognitive: systems-thinker
+    domain: null
+  reads:
+    - "docs/prd.md"
+    - "docs/architecture.md"
+    - "docs/ux-spec.md"
+    - "docs/security.md"
+
+  tasks:
+    - id: epic-sharding
+      name: "Epic Sharding"
+      output: "docs/epics/"
+      template: ".sniper/templates/epic.md"
+      description: >
+        Break the PRD into 6-12 epics. Each epic file must include:
+        - Scope and clear boundaries (what's in, what's out)
+        - Relevant sections from architecture doc (EMBEDDED, not just referenced)
+        - Dependencies on other epics
+        - Acceptance criteria for the epic as a whole
+        - Estimated total story points
+
+    - id: story-creation
+      name: "Story Creation"
+      output: "docs/stories/"
+      template: ".sniper/templates/story.md"
+      blocked_by: [epic-sharding]
+      description: >
+        For each epic, create 3-8 stories. Each story file must include:
+        - Full context from PRD + Architecture (EMBEDDED in the story file)
+        - Acceptance criteria as testable assertions
+        - Test requirements (unit, integration, e2e as applicable)
+        - File ownership (which directories this story's implementation touches)
+        - Dependencies on other stories
+        - Complexity estimate (S/M/L/XL)
+
+        CRITICAL: Stories must be self-contained. A teammate reading ONLY the story
+        file must have enough context to implement it without reading any other docs.
+
+review_gate:
+  checklist: ".sniper/checklists/story-review.md"
+  mode: flexible

package/framework/teams/sprint.yaml

@@ -0,0 +1,68 @@
+team_name: "sniper-sprint-{number}"
+phase: sprint
+
+available_teammates:
+  - name: backend-dev
+    compose:
+      process: developer
+      technical: backend
+      cognitive: systems-thinker
+      domain: null
+    owns_from_config: backend
+    model: sonnet
+
+  - name: frontend-dev
+    compose:
+      process: developer
+      technical: frontend
+      cognitive: user-empathetic
+      domain: null
+    owns_from_config: frontend
+    model: sonnet
+
+  - name: infra-dev
+    compose:
+      process: developer
+      technical: infrastructure
+      cognitive: systems-thinker
+      domain: null
+    owns_from_config: infrastructure
+    model: sonnet
+
+  - name: ai-dev
+    compose:
+      process: developer
+      technical: ai-ml
+      cognitive: performance-focused
+      domain: null
+    owns_from_config: ai
+    model: opus
+
+  - name: qa-engineer
+    compose:
+      process: qa-engineer
+      technical: backend
+      cognitive: devils-advocate
+      domain: null
+    owns_from_config: tests
+    model: sonnet
+
+sprint_rules:
+  - "Each teammate reads their assigned story file(s) COMPLETELY before writing any code"
+  - "Backend and frontend must agree on API contracts via inter-agent messaging BEFORE implementing"
+  - "All new code must include tests — no story is complete without passing tests"
+  - "QA engineer is blocked until implementation stories are complete"
+  - "Every teammate messages the team lead when their task is complete"
+  - "If any teammate is blocked for > 10 minutes, message the lead immediately"
+
+coordination:
+  - between: [backend-dev, frontend-dev]
+    topic: "API contracts — agree on endpoints, payloads, and auth before coding"
+  - between: [backend-dev, ai-dev]
+    topic: "AI pipeline integration points — data flow, WebSocket events, API boundaries"
+  - between: [backend-dev, qa-engineer]
+    topic: "Share testable endpoints as they're completed"
+
+review_gate:
+  checklist: ".sniper/checklists/sprint-review.md"
+  mode: strict

package/framework/templates/architecture.md

@@ -0,0 +1,72 @@
+# System Architecture: {project_name}
+
+> **Status:** Draft
+> **Author:** Planning Team — Architect
+> **Date:** {date}
+> **Source:** `docs/prd.md`, `docs/brief.md`
+
+## 1. Architecture Overview
+<!-- High-level system description. Include an ASCII or Mermaid component diagram. -->
+
+## 2. Technology Choices
+| Component | Choice | Why | Alternatives Considered |
+|-----------|--------|-----|------------------------|
+| Language | | | |
+| Frontend | | | |
+| Backend | | | |
+| Database | | | |
+| Cache | | | |
+| Queue | | | |
+| Infrastructure | | | |
+
+## 3. Component Architecture
+<!-- Describe each major component, its responsibility, and its interfaces -->
+
+### 3.1 {Component Name}
+- **Responsibility:**
+- **Interfaces:**
+- **Dependencies:**
+
+## 4. Data Models
+<!-- Entity-relationship descriptions with field types, constraints, indexes -->
+
+### 4.1 {Entity Name}
+| Field | Type | Constraints | Index | Notes |
+|-------|------|------------|-------|-------|
+| | | | | |
+
+## 5. API Contracts
+<!-- RESTful endpoints with methods, paths, request/response payloads -->
+
+### 5.1 {Resource}
+```
+METHOD /api/v1/{resource}
+Request: { }
+Response: { }
+Status Codes: 200, 400, 401, 404, 500
+Auth: Required
+```
+
+## 6. Infrastructure Topology
+<!-- Compute, storage, networking, scaling strategy -->
+
+## 7. Cross-Cutting Concerns
+
+### 7.1 Authentication & Authorization
+### 7.2 Logging & Monitoring
+### 7.3 Error Handling
+### 7.4 Configuration Management
+
+## 8. Non-Functional Requirements
+| Requirement | Target | Strategy |
+|-------------|--------|----------|
+| Response time (p95) | | |
+| Availability | | |
+| Throughput | | |
+| Data retention | | |
+
+## 9. Migration & Deployment Strategy
+<!-- How the system gets deployed. CI/CD, blue-green, rollback strategy. -->
+
+## 10. Security Architecture
+<!-- Reference docs/security.md for detailed security requirements -->

package/framework/templates/brief.md

@@ -0,0 +1,52 @@
+# Project Brief: {project_name}
+
+> **Status:** Draft
+> **Author:** Discovery Team — Analyst
+> **Date:** {date}
+
+## Executive Summary
+<!-- 2-3 sentence overview of the project and its value proposition -->
+
+## Problem Statement
+<!-- What problem does this solve? Who has this problem? How is it currently solved? -->
+
+## Market Landscape
+
+### Direct Competitors
+| Competitor | Key Features | Pricing | Market Position | Weaknesses |
+|-----------|-------------|---------|-----------------|------------|
+| | | | | |
+
+### Indirect Competitors / Alternatives
+<!-- How are users solving this problem today without a dedicated tool? -->
+
+## Target Market
+- **Primary segment:** <!-- Who is the ideal customer? -->
+- **Market size:** <!-- TAM/SAM/SOM estimates if available -->
+- **Growth trends:** <!-- Is this market growing? Why? -->
+
+## Unique Value Proposition
+<!-- What makes this product different from everything else? Be specific. -->
+
+## Key Assumptions
+<!-- List assumptions that need validation. These are things you believe but haven't proven. -->
+1.
+2.
+3.
+
+## Technical Constraints
+<!-- Known technical limitations, required integrations, regulatory requirements -->
+
+## Initial Scope Recommendation
+<!-- What should v1 include? What should it NOT include? -->
+
+### In Scope (v1)
+-
+
+### Out of Scope (v1)
+-
+
+## Open Questions
+<!-- Questions that need answers before planning can begin -->
+1.
+2.

package/framework/templates/doc-api.md

@@ -0,0 +1,53 @@
+# API Reference
+
+> {one_line_description}
+
+<!-- sniper:managed:start -->
+
+## Base URL
+```
+{base_url}
+```
+
+## Authentication
+<!-- Auth method: API key, JWT, OAuth, etc. -->
+
+## Endpoints
+
+### {Resource Group 1}
+
+#### `{METHOD} {path}`
+{description}
+
+**Request**
+```json
+{
+}
+```
+
+**Response** `{status_code}`
+```json
+{
+}
+```
+
+**Error Codes**
+| Code | Description |
+|------|-------------|
+| | |
+
+<!-- Repeat for each endpoint -->
+
+## Common Error Responses
+| Status | Code | Description |
+|--------|------|-------------|
+| 400 | BAD_REQUEST | Invalid request parameters |
+| 401 | UNAUTHORIZED | Missing or invalid authentication |
+| 403 | FORBIDDEN | Insufficient permissions |
+| 404 | NOT_FOUND | Resource does not exist |
+| 500 | INTERNAL_ERROR | Unexpected server error |
+
+## Rate Limiting
+<!-- Rate limit details if applicable -->
+
+<!-- sniper:managed:end -->

package/framework/templates/doc-guide.md

@@ -0,0 +1,35 @@
+# {guide_title}
+
+> {one_line_summary}
+
+<!-- sniper:managed:start -->
+
+## Overview
+<!-- What this guide covers and who it's for -->
+
+## Prerequisites
+<!-- What the reader needs before starting -->
+-
+
+## Steps
+
+### 1. {first_step}
+<!-- Detailed instructions with code examples -->
+
+### 2. {second_step}
+<!-- Continue as needed -->
+
+## Examples
+<!-- Working examples that demonstrate the key concepts -->
+
+## Troubleshooting
+<!-- Common issues and their solutions -->
+| Problem | Solution |
+|---------|----------|
+| | |
+
+## Related Documentation
+<!-- Links to other relevant docs -->
+-
+
+<!-- sniper:managed:end -->

package/framework/templates/doc-readme.md

@@ -0,0 +1,49 @@
+# {project_name}
+
+> {one_line_description}
+
+<!-- sniper:managed:start -->
+
+## Overview
+<!-- 2-3 sentences explaining what the project does and who it's for -->
+
+## Features
+<!-- Bullet list of key features. Source from PRD P0/P1 or infer from codebase -->
+-
+
+## Quick Start
+
+### Prerequisites
+<!-- List runtime requirements: Node.js version, database, etc. -->
+-
+
+### Installation
+```bash
+# Clone, install, and run commands — must actually work
+```
+
+### Usage
+```bash
+# Primary usage example
+```
+
+## Tech Stack
+| Layer | Technology |
+|-------|-----------|
+| | |
+
+## Project Structure
+```
+project-root/
+├── src/
+│   └── ...
+└── ...
+```
+
+<!-- sniper:managed:end -->
+
+## Contributing
+<!-- Link to CONTRIBUTING.md if it exists, or brief instructions -->
+
+## License
+<!-- License type and link -->

package/framework/templates/epic.md

@@ -0,0 +1,33 @@
+# Epic {number}: {title}
+
+> **Status:** Draft
+> **Priority:** P{0|1|2}
+> **Estimated Points:** {total}
+> **Dependencies:** {epic dependencies or "None"}
+
+## Scope
+<!-- What this epic covers and what it explicitly does NOT cover -->
+
+### In Scope
+-
+
+### Out of Scope
+-
+
+## Architecture Context
+<!-- EMBED relevant sections from docs/architecture.md — don't just reference -->
+
+## Stories
+| # | Story | Complexity | Dependencies | Owner |
+|---|-------|-----------|-------------|-------|
+| {epic}.1 | | S/M/L/XL | | backend/frontend/infra |
+| {epic}.2 | | | | |
+
+## Acceptance Criteria
+<!-- Epic-level acceptance criteria — what must be true when ALL stories are done -->
+1.
+2.
+3.
+
+## Technical Notes
+<!-- Any technical considerations specific to this epic -->

package/framework/templates/personas.md

@@ -0,0 +1,118 @@
+# User Personas & Journey Maps: {project_name}
+
+> **Status:** Draft
+> **Author:** Discovery Team — User Researcher
+> **Date:** {date}
+
+## Persona Overview
+<!-- Brief summary of who uses this product and why -->
+
+---
+
+## Persona 1: {persona_name}
+
+### Demographics & Context
+- **Role:** <!-- Job title or role -->
+- **Experience Level:** <!-- Junior / Mid / Senior / Executive -->
+- **Tech Savviness:** <!-- Low / Medium / High -->
+- **Usage Frequency:** <!-- Daily / Weekly / Monthly -->
+
+### Goals
+1.
+2.
+3.
+
+### Pain Points
+1.
+2.
+3.
+
+### Current Workflow
+<!-- How does this persona solve the problem today without this product? -->
+
+### User Journey Map
+
+| Stage | Action | Touchpoint | Emotion | Opportunity |
+|-------|--------|------------|---------|-------------|
+| Awareness | | | | |
+| Onboarding | | | | |
+| First Use | | | | |
+| Regular Use | | | | |
+| Advanced Use | | | | |
+
+### Key Scenarios
+<!-- 2-3 specific scenarios where this persona interacts with the product -->
+
+#### Scenario 1: {scenario_name}
+- **Context:** <!-- When and where does this happen? -->
+- **Trigger:** <!-- What initiates this scenario? -->
+- **Steps:** <!-- What does the user do? -->
+- **Success Criteria:** <!-- How does the user know they succeeded? -->
+
+---
+
+## Persona 2: {persona_name}
+
+### Demographics & Context
+- **Role:**
+- **Experience Level:**
+- **Tech Savviness:**
+- **Usage Frequency:**
+
+### Goals
+1.
+2.
+3.
+
+### Pain Points
+1.
+2.
+3.
+
+### Current Workflow
+
+### User Journey Map
+
+| Stage | Action | Touchpoint | Emotion | Opportunity |
+|-------|--------|------------|---------|-------------|
+| Awareness | | | | |
+| Onboarding | | | | |
+| First Use | | | | |
+| Regular Use | | | | |
+| Advanced Use | | | | |
+
+### Key Scenarios
+
+#### Scenario 1: {scenario_name}
+- **Context:**
+- **Trigger:**
+- **Steps:**
+- **Success Criteria:**
+
+---
+
+## Cross-Persona Analysis
+
+### Shared Needs
+<!-- What do all personas have in common? -->
+
+### Conflicting Needs
+<!-- Where do personas' needs diverge? How should the product handle this? -->
+
+### Prioritization
+| Persona | Priority | Justification |
+|---------|----------|---------------|
+| | P0 | |
+| | P1 | |
+
+## Friction Points Summary
+<!-- Top friction points across all personas, ranked by severity -->
+1.
+2.
+3.
+
+## Moments of Delight
+<!-- Opportunities to exceed user expectations -->
+1.
+2.
+3.