npm - specweave - Versions diffs - 0.1.8 → 0.3.0 - Mend

specweave 0.1.8 → 0.3.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (294) hide show

package/SPECWEAVE.md DELETED Viewed

@@ -1,711 +0,0 @@
-# SpecWeave - Spec-Driven Development Framework
-**THIS FILE IS YOUR QUICK REFERENCE GUIDE**
-**Note**: `CLAUDE.md` symlink exists for backward compatibility and points to this file.
-This file contains quick reference for developing with SpecWeave:
-- Core principles and project structure
-- Quick reference tables (agents, skills, commands)
-- Links to detailed guides (loaded on-demand by agents)
-**For detailed workflows**: See `.specweave/docs/internal/delivery/guides/`
----
-## Using SpecWeave with Slash Commands (CRITICAL)
-**IMPORTANT**: SpecWeave uses **EXPLICIT SLASH COMMANDS** - no auto-activation, no proactive detection!
-### How SpecWeave Works
-SpecWeave follows the **spec-kit approach**: You MUST use slash commands explicitly.
-**To use SpecWeave**: Type a slash command (e.g., `/inc "Feature description"`)
-### Quick Command Reference
-**Core Workflow** (4 commands):
-| Alias | Full Command | Purpose | Example |
-|-------|--------------|---------|---------|
-| `/inc` | `/increment` | **Plan Product Increment** (PM-led) | `/inc "User auth"` |
-| - | `/build` | Execute implementation (hooks after every task) | `/build 0001` |
-| - | `/validate` | Validate quality (optional LLM judge) | `/validate 0001 --quality` |
-| - | `/done` | Close increment (PM validates 3 gates) | `/done 0001` |
-**Supporting Commands**:
-- `/create-project` - Initialize SpecWeave project
-- `/list-increments` - List all increments
-- `/review-docs` - Review docs vs code
-- `/generate-docs` - Generate doc site
-- `/sync-github` - Sync to GitHub
-**Why ONE Alias (/inc)?**
-- ✅ `/inc` is THE most used command (every new feature starts here)
-- ✅ Append-only increment workflow: 0001 → 0002 → 0003 → ...
-- ✅ Other commands used once per increment (no aliases needed)
-- ✅ Clear and explicit workflow
-### Typical Workflow
-```bash
-# 1. Initialize project
-npx specweave init my-saas
-# 2. Plan your first increment (use /inc - the ONLY alias!)
-/inc "User authentication with JWT and RBAC"
-# 3. Review generated docs
-#    spec.md, plan.md, tasks.md (auto-generated!), tests.md
-# 4. Build it (hooks run after EVERY task)
-/build 0001
-# 5. Validate quality (optional)
-/validate 0001 --quality
-# 6. Close when done (PM validates: tasks ✅ + tests ✅ + docs ✅)
-/done 0001
-# 7. Repeat for next feature
-/inc "Payment processing"
-```
-**Remember**: Type `/inc` first, THEN build! Otherwise you lose all SpecWeave benefits (specs, architecture, auto-generated tasks, test strategy).
----
-## Project Philosophy
-**SpecWeave** is a specification-first AI development framework where **specifications and documentation are the SOURCE OF TRUTH**. Code is the expression of these specifications in a particular language.
-### Core Principles
-1. **Specification Before Implementation** - Define WHAT and WHY before HOW
-2. **Living Documentation** - Specs evolve with code, never diverge
-3. **Regression Prevention** - Document existing code before modification
-4. **Test-Validated Features** - Every feature proven through automated tests
-5. **Scalable from Solo to Enterprise** - Modular structure that grows with project size
-6. **Context Precision** - Load only relevant specs (70%+ token reduction)
-7. **Auto-Role Routing** - Skills detect and route to appropriate expertise automatically
-8. **Closed-Loop Validation** - E2E tests must tell the truth (no false positives)
-9. **🔄 Meta-Capability** - Agents build agents, skills build skills, SpecWeave builds SpecWeave
-**See**: [.specweave/docs/internal/architecture/meta-capability.md](.specweave/docs/internal/architecture/meta-capability.md) for complete meta-capability documentation
----
-## Documentation Approaches
-**SpecWeave supports TWO approaches**:
-1. **Comprehensive Upfront** (Enterprise/Production) - 500-600+ page specifications before coding
-2. **Incremental/Evolutionary** (Startup/Iterative) - Build documentation as you go
-Both approaches use the same framework, tools, and 5-pillar documentation structure.
-**See**: [.specweave/docs/internal/strategy/README.md](.specweave/docs/internal/strategy/README.md) for choosing your approach
----
-## 🚨 CRITICAL: File Organization (Keep Root Clean!)
-**MANDATORY**: ALL AI-generated supporting files MUST go into increment folders - NEVER in project root!
-**✅ ALLOWED in Root**:
-- `CLAUDE.md` (ONLY file SpecWeave adds to user's project)
-- User's existing files (unchanged)
-**❌ NEVER Create in Root**:
-- Logs → `.specweave/increments/{id}/logs/`
-- Scripts → `.specweave/increments/{id}/scripts/`
-- Reports → `.specweave/increments/{id}/reports/`
-**Example**:
-```
-❌ WRONG:                          ✅ CORRECT:
-project-root/                      .specweave/increments/0001-auth/
-├── analysis.md                    ├── reports/analysis.md
-├── script.py                      ├── scripts/script.py
-└── errors.log                     └── logs/errors.log
-```
-**Benefits**: Complete traceability, easy cleanup, clear context, no root clutter
----
-## Quick Reference: Directory Structure
-```
-your-project/
-├── .specweave/                     # Framework internals
-│   ├── config.yaml                 # Project configuration
-│   ├── docs/                       # 5-pillar documentation
-│   │   ├── internal/
-│   │   │   ├── strategy/           # Business specs (WHAT, WHY)
-│   │   │   ├── architecture/       # Technical design (HOW)
-│   │   │   ├── delivery/           # Roadmap, CI/CD, guides
-│   │   │   ├── operations/         # Runbooks, SLOs
-│   │   │   └── governance/         # Security, compliance
-│   │   └── public/                 # Published docs
-│   ├── increments/                 # Features (auto-numbered)
-│   │   └── 0001-feature-name/
-│   │       ├── spec.md             # WHAT & WHY (< 250 lines)
-│   │       ├── plan.md             # HOW (< 500 lines)
-│   │       ├── tasks.md            # Implementation checklist
-│   │       ├── tests.md            # Test strategy
-│   │       ├── context-manifest.yaml  # What to load (70%+ token reduction)
-│   │       ├── logs/               # ✅ Execution logs, errors, AI sessions
-│   │       ├── scripts/            # ✅ Helper scripts (migration, setup, validation)
-│   │       └── reports/            # ✅ Analysis, completion, performance reports
-│   └── tests/                      # Centralized test repository
-│
-├── .claude/                        # Installed components
-│   ├── agents/                     # Installed agents (selective)
-│   ├── skills/                     # Installed skills (selective)
-│   └── commands/                   # Slash commands
-│
-├── CLAUDE.md                       # This file (ONLY file we add)
-└── src/                            # Your source code (unchanged)
-```
-**See**: [.specweave/docs/internal/delivery/guides/development-workflow.md](.specweave/docs/internal/delivery/guides/development-workflow.md) for complete development workflow
----
-## Installation
-**Initialize New Project**:
-```bash
-npx specweave init                  # Auto-detects tech stack
-npx specweave init --type python    # Specify tech stack
-```
-**Selective Installation** (Recommended for user projects):
-```bash
-npx specweave install --detect      # Install only relevant agents/skills
-npx specweave install pm --local    # Install specific component
-npx specweave list --installed      # See what's installed
-```
-**Token Savings**: 60-71% reduction vs installing all components!
-**Required Model**: Claude Sonnet 4.5 (`claude-sonnet-4-5-20250929`)
-**See**: [Installation Guide](#) for complete installation instructions
----
-## Quick Reference: Slash Commands (MUST USE!)
-**CRITICAL**: SpecWeave uses **EXPLICIT SLASH COMMANDS** - type them to activate the framework!
-### Core Workflow (4 Commands)
-| Command | Alias | Purpose | Example |
-|---------|-------|---------|---------|
-| `/increment` | `/inc` | Plan Product Increment (PM-led, auto-generates tasks) | `/inc "user authentication"` |
-| `/build` | - | Execute implementation (hooks after EVERY task) | `/build 0001` |
-| `/validate` | - | Validate quality (optional LLM judge) | `/validate 0001 --quality` |
-| `/done` | - | Close increment (PM validates 3 gates: tasks, tests, docs) | `/done 0001` |
-### Supporting Commands
-| Command | Purpose | Example |
-|---------|---------|---------|
-| `/create-project` | Bootstrap new SpecWeave project | `/create-project --type python` |
-| `/list-increments` | List all increments with status | `/list-increments` |
-**All commands are framework-agnostic** (adapt to detected tech stack)
-**See**: [Command Reference](.claude/commands/) for all available commands
----
-## Quick Reference: Core Agents
-**Core Agents** (Complex workflows, separate context):
-| Agent | Purpose | Activates When |
-|-------|---------|----------------|
-| `pm` | Product requirements, user stories | Planning features, requirements analysis |
-| `architect` | System design, ADRs, architecture | Technical design, architecture decisions |
-| `diagrams-architect` | Mermaid diagrams (C4, sequence, ER) | Creating diagrams (invoked by diagrams-generator skill) |
-| `security` | Threat modeling, security review | Security concerns, vulnerability assessment |
-| `qa-lead` | Test strategy, test cases | Testing, quality assurance |
-| `devops` | Infrastructure, deployment | Deployment, CI/CD, infrastructure |
-| `sre` | Incident response, troubleshooting | Production incidents, debugging |
-| `tech-lead` | Code review, best practices | Code review, refactoring |
-| `docs-writer` | Documentation creation | Writing docs, API documentation |
-| `performance` | Performance optimization, profiling | Performance issues, optimization |
-**Invoke via**: `Task` tool with `subagent_type` parameter
-**See**: [src/agents/](src/agents/) for all available agents
----
-## Quick Reference: Core Skills
-**Framework Skills** (Core functionality):
-| Skill | Purpose | Activates When |
-|-------|---------|----------------|
-| `specweave-detector` | Slash command documentation | User asks about SpecWeave commands |
-| `increment-planner` | Plan features with context | `/inc` or `/increment` command |
-| `skill-router` | Route to appropriate skills | Ambiguous requests |
-| `context-loader` | Load context selectively | Working on increments |
-| `diagrams-generator` | Coordinate diagram creation | "create diagram", "draw diagram", C4, sequence, ER |
-**Technology Skills** (Implementation knowledge):
-| Skill | Purpose | Activates When |
-|-------|---------|----------------|
-| `nextjs` | Next.js App Router, Server Components | NextJS, Next.js, App Router |
-| `nodejs-backend` | Node.js/Express/NestJS APIs | Node.js, Express, NestJS |
-| `python-backend` | FastAPI/Django APIs | Python backend, FastAPI, Django |
-| `dotnet-backend` | ASP.NET Core APIs | .NET, C#, ASP.NET Core |
-| `frontend` | React/Vue/Angular frontend | React, Vue, Angular components |
-| `figma-implementer` | Figma to code conversion | Figma to code, implement design |
-| `figma-designer` | Figma design creation | Create Figma design, design system |
-**Integration Skills** (External tools):
-| Skill | Purpose | Activates When |
-|-------|---------|----------------|
-| `jira-sync` | Sync with JIRA | JIRA integration |
-| `ado-sync` | Sync with Azure DevOps | ADO integration |
-| `github-sync` | Sync with GitHub | GitHub integration |
-| `hetzner-provisioner` | Hetzner deployment | Deploying to Hetzner |
-| `cost-optimizer` | Infrastructure cost analysis | Cloud provider selection |
-| `specweave-jira-mapper` | SpecWeave ↔ JIRA mapping | JIRA sync, export to JIRA |
-| `specweave-ado-mapper` | SpecWeave ↔ ADO mapping | ADO sync, export to ADO |
-**Quality & Optimization Skills** (NEW):
-| Skill | Purpose | Activates When |
-|-------|---------|----------------|
-| `increment-quality-judge` | AI-powered quality assessment (LLM-as-judge) | Validate quality, quality check, assess spec |
-| `context-optimizer` | Second-pass context cleanup (80%+ reduction) | Optimize context, reduce tokens, smart context |
-**Skills activate automatically** based on description matching
-**See**: [src/skills/](src/skills/) for all available skills
----
-## Quick Reference: Increment Lifecycle
-**Status Progression**:
-```
-backlog → planned → in-progress → completed → closed
-```
-**WIP Limits**:
-- Framework development: 2-3 in progress
-- User projects (solo): 1-2 in progress
-- User projects (team): 3-5 in progress
-**Naming Convention**: 4-digit format (0001-9999), e.g., `0001-feature-name`, `0042-user-auth`, `0123-payment-flow`
-**Commands**:
-```bash
-/inc "feature name"                    # Plan increment (PM-led, auto-generates tasks)
-/build 0001                            # Execute implementation (hooks after EVERY task)
-/validate 0001 --quality               # Validate quality (optional)
-/done 0001                             # Close increment (PM validates 3 gates)
-```
-**See**: [Increment Lifecycle Guide](.specweave/docs/internal/delivery/guides/increment-lifecycle.md) for complete lifecycle management
----
-## Quick Reference: Testing
-**Four Levels of Test Cases**:
-1. **Specification** (`.specweave/docs/internal/strategy/`) - TC-0001 acceptance criteria
-2. **Feature** (`.specweave/increments/0001-feature-name/tests.md`) - Test coverage matrix
-3. **Skill** (`src/skills/{name}/test-cases/`) - 3+ YAML test cases (MANDATORY)
-4. **Code** (`tests/`) - Automated tests (Unit, Integration, E2E)
-**Requirements**:
-- ✅ Minimum 3 test cases per skill
-- ✅ E2E tests (Playwright) when UI exists
-- ✅ >80% coverage for critical paths
-- ✅ Tests MUST tell the truth (no false positives)
-**See**: [Testing Strategy Guide](.specweave/docs/internal/delivery/guides/testing-strategy.md) for complete testing philosophy
----
-## Quick Reference: Deployment
-**Deployment Target Detection**:
-Agents ask about deployment ONLY when:
-- User mentions "deploy", "production", "hosting"
-- DevOps agent is invoked
-- Infrastructure code is needed
-**Supported Targets**:
-- Local (Docker Compose)
-- Hetzner Cloud (cheapest)
-- Railway (easiest)
-- Vercel (best for Next.js)
-- AWS/Azure/GCP (enterprise)
-**Configuration**: `.specweave/config.yaml`
-**See**: [Deployment Intelligence Guide](.specweave/docs/internal/delivery/guides/deployment-intelligence.md) for complete deployment workflow
----
-## Quick Reference: C4 Diagrams
-**C4 Model Levels**:
-| Level | SpecWeave Equivalent | Location |
-|-------|----------------------|----------|
-| C4-1: Context | HLD Context Diagram | `.specweave/docs/internal/architecture/diagrams/` |
-| C4-2: Container | HLD Component Diagram | `.specweave/docs/internal/architecture/diagrams/` |
-| C4-3: Component | LLD Component Diagram | `.specweave/docs/internal/architecture/diagrams/{module}/` |
-| C4-4: Code | Source code + UML | Code comments or separate docs |
-**CRITICAL**: C4 diagrams start DIRECTLY with `C4Context` (NO `mermaid` keyword!)
-**See**: [Diagram Conventions Guide](.specweave/docs/internal/delivery/guides/diagram-conventions.md) for complete diagram rules
----
-## Quick Reference: Validation
-**Increment Validation** runs automatically on document save:
-**120 validation rules** across 4 categories:
-1. **Consistency** (47 rules) - Spec ↔ Plan ↔ Tasks alignment
-2. **Completeness** (23 rules) - All required sections present
-3. **Quality** (31 rules) - Technology-agnostic, testable criteria
-4. **Traceability** (19 rules) - TC-0001 → tests.md coverage
-**Validation happens automatically** when documents are saved. For manual quality assessment, ask Claude to "validate quality of increment 0001" to invoke the `increment-quality-judge` skill.
-**See**: [Increment Validation Guide](.specweave/docs/internal/delivery/guides/increment-validation.md) for complete validation workflow
----
-## Detailed Guides (On-Demand Loading)
-**For complete details, agents load guides from** `.specweave/docs/internal/delivery/guides/`:
-| Guide | Purpose | Loaded By |
-|-------|---------|-----------|
-| [increment-lifecycle.md](. specweave/docs/internal/delivery/guides/increment-lifecycle.md) | Complete increment lifecycle management | `increment-planner` |
-| [increment-validation.md](.specweave/docs/internal/delivery/guides/increment-validation.md) | Validation workflow and rules | `increment-validator` |
-| [development-workflow.md](.specweave/docs/internal/delivery/guides/development-workflow.md) | Greenfield and brownfield workflows | When starting development |
-| [deployment-intelligence.md](.specweave/docs/internal/delivery/guides/deployment-intelligence.md) | Deployment target detection and infrastructure | `devops` agent |
-| [testing-strategy.md](.specweave/docs/internal/delivery/guides/testing-strategy.md) | Complete testing philosophy (4 levels) | `qa-lead` agent |
-| [test-import.md](.specweave/docs/internal/delivery/guides/test-import.md) | Importing existing tests | `test-importer` skill |
-| [diagram-conventions.md](.specweave/docs/internal/delivery/guides/diagram-conventions.md) | C4 diagrams and Mermaid syntax | `diagrams-architect` skill |
-| [diagram-svg-generation.md](.specweave/docs/internal/delivery/guides/diagram-svg-generation.md) | SVG generation for production docs | When building docs site |
-**Agents automatically load relevant guides when activated** - you don't need to manage this manually.
----
-## Agents vs Skills: When to Use Which
-| Create Agent When | Create Skill When |
-|-------------------|-------------------|
-| Complex, multi-step workflows | Simple, focused tasks |
-| Needs separate context window | Can share main context |
-| Distinct personality/role needed | Capability extension |
-| Tool restrictions by role | All tools acceptable |
-| Long-running tasks | Quick operations |
-| **Example**: Security audit, PM planning | **Example**: Next.js knowledge, diagram creation |
-**Agents** (9 total): PM, Architect, Security, QA Lead, DevOps, SRE, Tech Lead, Docs Writer, Performance
-**Skills** (30+ total): Technology stacks (Next.js, Node.js, Python, .NET, Frontend), Integrations (JIRA, ADO, GitHub), Utilities (diagrams, Figma, cost optimizer)
-**Agents**: Invoked via `Task` tool with `subagent_type`
-**Skills**: Activate automatically based on description
----
-## Source of Truth: src/ Folder
-**CRITICAL RULE**: All SpecWeave framework components (agents, skills, commands, hooks) MUST be created in `src/` folder first, then installed to `.claude/` via install script.
-```
-src/
-├── agents/                    # ✅ Source of truth for ALL agents
-├── skills/                    # ✅ Source of truth for ALL skills
-├── commands/                  # ✅ Source of truth for ALL slash commands
-├── hooks/                     # ✅ Source of truth for ALL hooks
-└── templates/                 # ✅ ONLY files for user's project root
-```
-**Installation Flow**:
-1. Create in `src/agents/{name}/` or `src/skills/{name}/`
-2. Run `npm run install:agents` or `npm run install:skills`
-3. Components copied to `.claude/`
-**User Projects**: Can create custom agents/skills in `.claude/` or `~/.claude/`
----
-## Naming Conventions
-**Increments**: 4-digit format `0001-9999` (e.g., `0001-skills-framework`, `0042-user-auth`, `0123-payment-flow`)
-  - Always zero-padded to 4 digits
-  - Duplicate detection prevents conflicts
-  - Examples: `0001-core-framework`, `0002-multi-tool-support`, `0003-deployment-pipeline`
-**Modules**: `lowercase-kebab-case` (e.g., `payments/stripe/`)
-**ADRs**: 4-digit format `0001-decision-title.md` (e.g., `0001-tech-stack.md`, `0042-database-choice.md`)
-**Test Cases**: `TC-0001`, `TC-0002` format for traceability
----
-## Development Workflow Summary
-### Greenfield Projects
-**Option A: Comprehensive Upfront** (Enterprise)
-1. Create 500-600+ page specifications (`.specweave/docs/internal/strategy/`)
-2. Design architecture (`.specweave/docs/internal/architecture/`)
-3. Plan features in increments
-4. Implement with context manifests
-**Option B: Incremental** (Startup)
-1. Start with overview (10-20 pages)
-2. Build documentation as you go
-3. Add modules/specs as features are planned
-**See**: [Development Workflow Guide](.specweave/docs/internal/delivery/guides/development-workflow.md) for complete workflow
-### Brownfield Projects
-1. **Analyze** existing code (`brownfield-analyzer` skill)
-2. **Document** current behavior (retroactive specs + ADRs)
-3. **Create tests** for current functionality (user reviews)
-4. **Plan modifications** (new increment)
-5. **Implement** with regression monitoring
-**See**: [Development Workflow Guide](.specweave/docs/internal/delivery/guides/development-workflow.md) for brownfield details
----
-## Git Workflow
-**Branch naming**: `features/{increment-id}-{short-name}` (use 4-digit format without leading zeros in branch name for brevity)
-**Workflow**:
-1. Create increment folder (`.specweave/increments/0002-name/`)
-2. Create feature branch (`git checkout -b features/002-name` or `features/0002-name`)
-3. Implement in src/ (agents, skills, etc.)
-4. Commit regularly
-5. Create PR when complete
-6. Merge to develop
-**NEVER commit directly to `develop` or `main`**
-**Note**: Branch names can use either `features/002-name` (3-digit for brevity) or `features/0002-name` (4-digit for consistency), but increment folders MUST always use 4-digit format.
----
-## Context Precision (80%+ Token Reduction)
-### Pass 1: Context Loader (70% reduction)
-**Context Manifests** (`.specweave/increments/0001-feature-name/context-manifest.yaml`):
-```yaml
-spec_sections:
-  - .specweave/docs/internal/strategy/auth/spec.md
-documentation:
-  - .specweave/docs/internal/architecture/auth-design.md
-  - .specweave/docs/internal/architecture/adr/0003-auth-method.md
-max_context_tokens: 10000
-```
-**Result**: 150k tokens → 45k tokens (70% reduction)
-### Pass 2: Context Optimizer (80%+ total reduction) 🆕
-**Smart cleanup based on user intent**:
-```typescript
-User: "Fix login bug in authentication"
-Analyzer detects:
-  • Task: Bug fix (narrow scope)
-  • Domain: Authentication
-  • Scope: Single endpoint
-Removes unneeded:
-  ❌ payment-spec.md (different domain)
-  ❌ PM agent (not needed for bug fix)
-  ❌ Frontend skills (backend task)
-Keeps relevant:
-  ✅ auth-spec.md (core domain)
-  ✅ nodejs-backend skill
-  ✅ Tech Lead agent
-Result: 45k → 27k tokens (additional 40% reduction)
-Total: 150k → 27k (82% total reduction)
-```
-**Benefits**:
-- Two-pass optimization (manifest + intent)
-- 80%+ total token reduction
-- Scales to enterprise (500-1000+ page specs)
-- Automatic, no manual intervention
-**Loaded by**: `context-loader` (Pass 1) + `context-optimizer` (Pass 2)
----
-## Quality Assurance (AI-Powered Quality Judge)
-**Optional AI-powered quality assessment** beyond rule-based validation:
-### How to Use
-**Activate the `increment-quality-judge` skill** by asking:
-- "Validate quality of increment 0001"
-- "Quality check for increment 0003"
-- "Assess spec quality for authentication feature"
-- "How good is the spec for increment 0002?"
-The skill will evaluate:
-- **Clarity**: Are requirements clear and unambiguous?
-- **Testability**: Can acceptance criteria be tested?
-- **Completeness**: Are edge cases covered?
-- **Feasibility**: Is the plan technically sound?
-- **Maintainability**: Is the design sustainable?
-- **Architecture**: Are design decisions justified?
-**Example Output**:
-```
-🔍 Quality Assessment: Increment 0002-user-authentication
-Overall Score: 87/100 (GOOD)
-Dimension Scores:
-  • Clarity:         92/100 ✓✓
-  • Testability:     78/100 ✓  (Needs improvement)
-  • Completeness:    90/100 ✓✓
-  • Feasibility:     88/100 ✓✓
-  • Maintainability: 85/100 ✓
-  • Edge Cases:      72/100 ⚠️  (Action needed)
-Issues Found: 2 major, 1 minor
-Suggestions: 3 high priority improvements
-```
-**Features**:
-- 6-dimension quality scoring
-- Actionable suggestions with examples
-- LLM-as-Judge pattern for nuanced assessment
-- Complements rule-based validation
-**Configuration**: `.specweave/config.yaml` → `validation.quality_judge`
-**Provided by**: `increment-quality-judge` skill
----
-## Auto-Refinement (Feedback Loops) 🆕
-**Automatic quality improvement** through iterative refinement:
-### How It Works
-```
-Agent generates output
-       ↓
-Validate (rule-based + LLM-judge)
-       ↓
-Score < threshold? ──No──→ ✅ Accept
-       ↓ Yes
-Generate feedback with issues
-       ↓
-Agent regenerates with feedback
-       ↓ (max 3 attempts)
-Score improved? ──→ ✅ Accept best result
-```
-### Example: PM Agent with Auto-Refinement
-```markdown
-Attempt 1/3: Generating requirements...
-  Validation: 0.72/1.00 ⚠️ (Below threshold)
-  Issues: Acceptance criteria not testable, missing rate limiting
-Attempt 2/3: Refining with feedback...
-  Validation: 0.85/1.00 ✅ (Above threshold)
-  Improvements: Testable criteria added, rate limiting specified
-✅ Final Result: Requirements validated (0.85/1.00)
-```
-**Features**:
-- Max 3 refinement attempts per agent
-- Stops when quality threshold met (0.80 default)
-- Applies to PM, Architect, QA Lead agents
-- Shows progress and improvements
-- Optional (can disable per agent)
-**Configuration**: `.specweave/config.yaml` → `role_orchestrator.feedback_loops`
-**Provided by**: `role-orchestrator` skill
----
-## Summary
-**SpecWeave** replaces vibe coding with **Spec-Driven Development**:
-1. ✅ **Specifications are SOURCE OF TRUTH** - Code expresses specs
-2. ✅ **Framework-agnostic** - Works with ANY language/framework
-3. ✅ **Flexible documentation** - Comprehensive upfront OR incremental
-4. ✅ **Context precision** - 80%+ token reduction (two-pass optimization), scales 500-1000+ pages 🆕
-5. ✅ **Auto-role routing** - Skills detect expertise automatically
-6. ✅ **Deployment intelligence** - Asks about target before infrastructure
-7. ✅ **Test-validated** - 3+ tests per skill, E2E when UI exists
-8. ✅ **Living documentation** - Auto-update via Claude hooks
-9. ✅ **Brownfield-ready** - Analyze, document, then modify safely
-10. ✅ **Production-ready** - Supports enterprise scale
-11. ✅ **Quality assurance** - LLM-as-judge validation with 6-dimension scoring 🆕
-12. ✅ **Auto-refinement** - Feedback loops improve specs/designs automatically 🆕
-**This framework enables building software at ANY scale, with ANY tech stack, with confidence, clarity, minimal context usage, and automatic quality improvement.**
----
-**Quick Start**:
-**CRITICAL**: SpecWeave uses **EXPLICIT SLASH COMMANDS** - type `/inc` to activate!
-```bash
-# Initialize project
-npx specweave init my-project
-# Plan your first increment (use slash command!)
-/inc "feature description"
-# Typical workflow (append-only increments: 0001 → 0002 → 0003)
-1. /inc "feature" → PM creates specs + plan + auto-generates tasks
-2. /build 0001 → Execute implementation (hooks after EVERY task)
-3. /validate 0001 --quality → Optional quality check
-4. /done 0001 → PM validates 3 gates (tasks ✅ + tests ✅ + docs ✅)
-```
-**Remember**: Type `/inc` first to plan, THEN `/build` to implement! Otherwise you lose all SpecWeave benefits (specs, architecture, test strategy).
-**Need help?**: Type `/inc` to see examples, or ask about specific workflows.
-**SpecWeave Documentation**: https://spec-weave.com
-**Last Updated**: Auto-updated via `post-task-completion` hook