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โ
| Agent | Role | Expertise |
|---|---|---|
| PM | Product Manager | Requirements, user stories, roadmap |
| Architect | System Architect | Design, ADRs, component architecture |
| DevOps | DevOps Engineer | Infrastructure, deployment, CI/CD |
| SRE | Site Reliability Engineer | Monitoring, incidents, reliability |
| QA Lead | Quality Assurance | Test strategy, test cases |
| Security | Security Engineer | Threat modeling, penetration testing |
| Tech Lead | Technical Lead | Code review, best practices |
| Frontend | Frontend Developer | React, UI/UX implementation |
| Next.js | Next.js Specialist | Next.js app development |
| Node.js Backend | Backend Developer | API, services, backend logic |
| Python Backend | Python Developer | FastAPI, Django, data services |
| .NET Backend | .NET Developer | C#, ASP.NET Core, enterprise apps |
| Docs Writer | Documentation Writer | Guides, references, tutorials |
| Performance | Performance Engineer | Optimization, 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โ
-
Specification Acceptance Criteria (TC-0001 format)
- Business-level test cases in specifications
- Technology-agnostic validation
-
Feature Test Strategy (tests.md)
- Maps TC-0001 to implementations
- Defines test types (E2E, Unit, Integration)
-
Skill Test Cases (YAML-based)
- Minimum 3 tests per skill
- Structured validation
-
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/JavaScriptrequirements.txt/pyproject.tomlโ Pythongo.modโ GoCargo.tomlโ Rustpom.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:
- โ Analyze current implementation
- โ Generate retroactive documentation
- โ Create baseline tests
- โ User reviews and approves
- โ 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?
- Quickstart Guide - Get up and running in 5 minutes
- Installation - Detailed installation instructions
Previous: What is SpecWeave? | Next: Philosophy โ