Skip to main content

Key Features

SpecWeave provides a comprehensive suite of tools and workflows for building production-grade software with AI assistance.

๐ŸŽฏ Specification-First Developmentโ€‹

Living Documentationโ€‹

  • Source of Truth: Specifications drive implementation
  • Auto-Update: Hooks automatically update docs after task completion
  • Never Diverge: Code and specs stay synchronized
  • Modular Organization: Scale from 10 pages to 1000+ pages

5-Pillar Documentation Structureโ€‹

.specweave/docs/
โ”œโ”€โ”€ internal/
โ”‚ โ”œโ”€โ”€ strategy/ # WHAT and WHY (PRDs, user stories)
โ”‚ โ”œโ”€โ”€ architecture/ # HOW (system design, ADRs, RFCs)
โ”‚ โ”œโ”€โ”€ delivery/ # Roadmap, release plans
โ”‚ โ”œโ”€โ”€ operations/ # Runbooks, SLOs, monitoring
โ”‚ โ””โ”€โ”€ governance/ # Security, compliance
โ””โ”€โ”€ public/ # Customer-facing documentation

๐Ÿง  Context Precision (70%+ Token Reduction)โ€‹

Selective Loadingโ€‹

  • Context Manifests: Each increment declares what it needs
  • Section Anchors: Load specific sections, not entire files
  • Glob Patterns: Match multiple related files
  • Cache-Friendly: Reuse frequently-loaded context

Example Manifestโ€‹

```yaml spec_sections:

  • .specweave/docs/internal/strategy/auth/login-spec.md
  • .specweave/docs/internal/strategy/auth/oauth.md#token-flow documentation:
  • .specweave/docs/internal/architecture/adr/0001-auth-method.md max_context_tokens: 10000 ```

Result: Load exactly what's needed, save 70%+ on AI costs.

๐Ÿค– AI Agents & Skillsโ€‹

14 Core Agentsโ€‹

AgentRoleExpertise
PMProduct ManagerRequirements, user stories, roadmap
ArchitectSystem ArchitectDesign, ADRs, component architecture
DevOpsDevOps EngineerInfrastructure, deployment, CI/CD
SRESite Reliability EngineerMonitoring, incidents, reliability
QA LeadQuality AssuranceTest strategy, test cases
SecuritySecurity EngineerThreat modeling, penetration testing
Tech LeadTechnical LeadCode review, best practices
FrontendFrontend DeveloperReact, UI/UX implementation
Next.jsNext.js SpecialistNext.js app development
Node.js BackendBackend DeveloperAPI, services, backend logic
Python BackendPython DeveloperFastAPI, Django, data services
.NET Backend.NET DeveloperC#, ASP.NET Core, enterprise apps
Docs WriterDocumentation WriterGuides, references, tutorials
PerformancePerformance EngineerOptimization, profiling, scaling

Auto-Role Routingโ€‹

Skills automatically detect expertise and route requests:

``` User: "Create authentication system" โ†’ specweave-detector activates โ†’ Routes to feature-planner โ†’ Invokes PM, Architect, DevOps agents โ†’ Generates complete spec + architecture + plan ```

๐Ÿงช Test-Validated Developmentโ€‹

4-Level Testing Strategyโ€‹

  1. Specification Acceptance Criteria (TC-0001 format)

    • Business-level test cases in specifications
    • Technology-agnostic validation
  2. Feature Test Strategy (tests.md)

    • Maps TC-0001 to implementations
    • Defines test types (E2E, Unit, Integration)
  3. Skill Test Cases (YAML-based)

    • Minimum 3 tests per skill
    • Structured validation
  4. Code Tests (Automated)

    • E2E with Playwright (MANDATORY for UI)
    • Unit and integration tests
    • 80% coverage for critical paths

Truth-Telling Requirementโ€‹

E2E tests MUST tell the truth:

  • โœ… If test passes โ†’ feature actually works
  • โœ… If test fails โ†’ exactly what failed
  • โŒ No false positives
  • โŒ No masking failures

๐Ÿ“Š Mermaid Diagrams (C4 Model)โ€‹

Architecture Visualizationโ€‹

SpecWeave uses the C4 Model for architecture diagrams:

  • C4-1: Context - System boundaries, external actors
  • C4-2: Container - Applications, services, databases
  • C4-3: Component - Internal structure
  • C4-4: Code - Class diagrams (optional)

Example Diagramโ€‹

```mermaid C4Context title System Context Diagram for SpecWeave

Person(user, "Developer", "Uses SpecWeave to build software") System(specweave, "SpecWeave", "Spec-Driven Development Framework") System_Ext(claude, "Claude Code", "AI coding assistant") System_Ext(github, "GitHub", "Version control and CI/CD")

Rel(user, specweave, "Uses") Rel(specweave, claude, "Invokes agents") Rel(specweave, github, "Syncs increments") ```

๐ŸŒ Framework-Agnosticโ€‹

Supports ANY Tech Stackโ€‹

  • TypeScript/JavaScript: Next.js, NestJS, Express, React
  • Python: FastAPI, Django, Flask
  • Go: Gin, Echo, Fiber
  • Rust: Actix, Rocket, Axum
  • Java: Spring Boot, Quarkus
  • C#/.NET: ASP.NET Core, Blazor

Auto-Detectionโ€‹

SpecWeave detects your tech stack from:

  • package.json โ†’ TypeScript/JavaScript
  • requirements.txt / pyproject.toml โ†’ Python
  • go.mod โ†’ Go
  • Cargo.toml โ†’ Rust
  • pom.xml / build.gradle โ†’ Java
  • *.csproj โ†’ C#/.NET

๐Ÿ”„ Incremental Developmentโ€‹

Auto-Numbered Incrementsโ€‹

``` .specweave/increments/ โ”œโ”€โ”€ 0001-user-authentication/ โ”‚ โ”œโ”€โ”€ spec.md # What and Why โ”‚ โ”œโ”€โ”€ plan.md # How โ”‚ โ”œโ”€โ”€ tasks.md # Checklist โ”‚ โ”œโ”€โ”€ tests.md # Test strategy โ”‚ โ”œโ”€โ”€ logs/ # Execution logs โ”‚ โ”œโ”€โ”€ scripts/ # Helper scripts โ”‚ โ””โ”€โ”€ reports/ # Completion reports โ””โ”€โ”€ 0002-payment-processing/ โ””โ”€โ”€ ... ```

WIP Limitsโ€‹

Prevent context-switching:

  • Solo/small teams: 1-2 in progress
  • Large teams: 3-5 in progress
  • Force override: Available but discouraged

๐Ÿ”— External Integrationsโ€‹

JIRA Syncโ€‹

  • Bidirectional conversion
  • Epics โ†” Increments
  • Stories โ†” PRDs/RFCs
  • Tasks โ†” Tasks

Azure DevOps Syncโ€‹

  • 4-level hierarchy support
  • Epics โ†’ Features โ†’ User Stories โ†’ Tasks
  • Area Paths and Iterations
  • Work item synchronization

GitHub Syncโ€‹

  • Milestones โ†” Release Plans
  • Issues โ†” RFCs/Tasks
  • Checkable subtasks

๐Ÿ›ก๏ธ Regression Preventionโ€‹

Brownfield Safetyโ€‹

Before modifying existing code:

  1. โœ… Analyze current implementation
  2. โœ… Generate retroactive documentation
  3. โœ… Create baseline tests
  4. โœ… User reviews and approves
  5. โœ… Implement modifications safely

Impact Analysisโ€‹

  • Dependency graph generation
  • Affected modules identification
  • Regression risk assessment
  • User approval required

๐ŸŽจ Documentation Approachesโ€‹

Comprehensive Upfront (Enterprise)โ€‹

  • 500-600+ page specifications before coding
  • Full architecture and ADRs upfront
  • Complete API contracts
  • Best for: Enterprise, regulated industries

Incremental/Evolutionary (Startup)โ€‹

  • Start with overview (10-20 pages)
  • Build documentation as you go
  • Adapt to changing requirements
  • Best for: Startups, MVPs, prototypes

Both approaches fully supported!

โš™๏ธ Claude Hooks (Auto-Update)โ€‹

Post-Task-Completion Hookโ€‹

Automatically:

  • Updates CLAUDE.md when structure changes
  • Updates API/CLI reference
  • Updates changelog
  • Commits doc changes

Pre-Implementation Hookโ€‹

Checks regression risk before modifying existing code.

Human-Input-Required Hookโ€‹

Logs and notifies when AI needs clarification.

๐Ÿ“ฆ Slash Commandsโ€‹

Framework-agnostic commands:

  • /create-project - Initialize new SpecWeave project
  • /create-increment - Create new feature/increment
  • /review-docs - Review specs vs implementation
  • /sync-github - Sync to GitHub issues

All commands adapt to detected tech stack.

๐Ÿš€ Coming Soonโ€‹

  • Vector search: Semantic spec search (v2.0)
  • Multi-language support: i18n for docs
  • Figma integration: Design โ†’ Code
  • Cost optimization: Infrastructure cost analysis
  • Enterprise features: Compliance tracking, advanced analytics

Ready to get started?

Previous: What is SpecWeave? | Next: Philosophy โ†’