specweave 0.6.8 → 0.7.0

package/src/templates/README.md.template

@@ -14,16 +14,16 @@ Your project is initialized! Now describe what you want to build.
 
 ```bash
 # Plan a new feature
-/inc "user authentication with JWT"
+/specweave:increment "user authentication with JWT"
 
 # Execute the implementation
-/do
+/specweave:do
 
 # Check progress
-/progress
+/specweave:progress
 
 # Close when done
-/done 0001
+/specweave:done 0001
 ```
 
 3. **Or describe your project** in natural language (works with slash command workflows):
@@ -42,7 +42,7 @@ Your project is initialized! Now describe what you want to build.
    - Guide implementation
    - Generate tests
 
-That's it! All components ready - just use `/inc` to start!
+That's it! All components ready - just use `/specweave:increment` to start!
 
 ---
 
@@ -51,7 +51,8 @@ That's it! All components ready - just use `/inc` to start!
 ```
 {{PROJECT_NAME}}/
 ├── .specweave/             # SpecWeave framework
-│   ├── increments/         # Features (created via /inc)
+│   ├── config.json         # Project configuration
+│   ├── increments/         # Features (created via /specweave:increment)
 │   │   └── 0001-feature/
 │   │       ├── spec.md     # WHAT & WHY
 │   │       ├── plan.md     # HOW
@@ -78,7 +79,7 @@ That's it! All components ready - just use `/inc` to start!
 
 SpecWeave is a specification-first development framework where:
 - **Specifications are the source of truth** (code follows specs, not reverse)
-- **Slash commands drive workflow** (`/inc` → `/do` → `/done`)
+- **Slash commands drive workflow** (`/specweave:increment` → `/specweave:do` → `/specweave:done`)
 - **AI agents work autonomously** (PM, Architect, Security, QA, DevOps)
 - **All components pre-installed** (10 agents + 35+ skills ready!)
 - **Works with ANY tech stack** (TypeScript, Python, Go, Rust, Java, .NET, etc.)
@@ -89,18 +90,18 @@ SpecWeave is a specification-first development framework where:
 ## 🔧 Core Workflow
 
 ```
-/inc "feature" → /do → /progress → /done → repeat
+/specweave:increment "feature" → /specweave:do → /specweave:progress → /specweave:done → repeat
 ```
 
 | Command | Purpose | When to Use |
 |---------|---------|-------------|
-| `/inc "feature"` | Plan new increment | Starting new feature |
-| `/do` | Execute tasks | Ready to implement |
-| `/progress` | Check status | Want to see progress |
-| `/validate 0001` | Validate quality | Before completion |
-| `/done 0001` | Close increment | Feature finished |
-| `/sync-github` | Sync to GitHub | Export to issues |
-| `/sync-jira` | Sync to Jira | Export to Jira |
+| `/specweave:increment "feature"` | Plan new increment | Starting new feature |
+| `/specweave:do` | Execute tasks | Ready to implement |
+| `/specweave:progress` | Check status | Want to see progress |
+| `/specweave:validate 0001` | Validate quality | Before completion |
+| `/specweave:done 0001` | Close increment | Feature finished |
+| `/specweave:sync-github` | Sync to GitHub | Export to issues |
+| `/specweave:sync-jira` | Sync to Jira | Export to Jira |
 
 See `CLAUDE.md` for complete workflow guide.
 
@@ -152,7 +153,7 @@ SpecWeave works with:
 
 **Start with your first feature**:
 ```bash
-/inc "describe your feature here"
+/specweave:increment "describe your feature here"
 ```
 
 Or just describe what you want to build, and SpecWeave will guide you through the process! 🚀

package/src/templates/docs/README.md

@@ -1,6 +1,6 @@
 # Document Templates
 
-This directory contains templates for all standard document types in the PRD/HLD/RFC/Runbook pattern.
+This directory contains templates for all standard document types in the PRD/HLD/Spec/Runbook pattern.
 
 ## Available Templates
 
@@ -27,15 +27,16 @@ This directory contains templates for all standard document types in the PRD/HLD
     cp templates/docs/adr-template.md docs/internal/architecture/adr/${NEXT}-decision-title.md
     ```
 
-- **`rfc-template.md`** - Request for Comments
+- **`spec-template.md`** - Specification (formerly RFC)
   - **Purpose**: Propose API designs, schema changes, major features
-  - **Location**: `docs/internal/architecture/rfc/0001-feature-title.md`
+  - **Location**: `docs/internal/specs/spec-0001-feature-title/spec.md`
   - **Format**: Sequential numbering (0001, 0002, etc.)
   - **Usage**:
     ```bash
     # Find next number
-    NEXT=$(printf "%04d" $(($(ls docs/internal/architecture/rfc/ | grep -E '^[0-9]{4}' | tail -1 | cut -d'-' -f1) + 1)))
-    cp templates/docs/rfc-template.md docs/internal/architecture/rfc/${NEXT}-feature-title.md
+    NEXT=$(printf "%04d" $(($(ls docs/internal/specs/ | grep -E '^spec-[0-9]{4}' | tail -1 | cut -d'-' -f2) + 1)))
+    mkdir -p docs/internal/specs/spec-${NEXT}-feature-title
+    cp templates/docs/spec-template.md docs/internal/specs/spec-${NEXT}-feature-title/spec.md
     ```
 
 ### Operations Documents
@@ -66,10 +67,11 @@ This directory contains templates for all standard document types in the PRD/HLD
    cp templates/docs/adr-template.md docs/internal/architecture/adr/${NEXT}-use-postgresql.md
    ```
 
-4. **Create RFC** (for API design):
+4. **Create Spec** (for API design):
    ```bash
-   NEXT=$(printf "%04d" $(($(ls docs/internal/architecture/rfc/ 2>/dev/null | grep -E '^[0-9]{4}' | tail -1 | cut -d'-' -f1 | sed 's/^0*//' || echo 0) + 1)))
-   cp templates/docs/rfc-template.md docs/internal/architecture/rfc/${NEXT}-booking-api.md
+   NEXT=$(printf "%04d" $(($(ls docs/internal/specs/ 2>/dev/null | grep -E '^spec-[0-9]{4}' | tail -1 | cut -d'-' -f2 | sed 's/^0*//' || echo 0) + 1)))
+   mkdir -p docs/internal/specs/spec-${NEXT}-booking-api
+   cp templates/docs/spec-template.md docs/internal/specs/spec-${NEXT}-booking-api/spec.md
    ```
 
 5. **Create Runbook** (Operations):
@@ -94,7 +96,7 @@ This directory contains templates for all standard document types in the PRD/HLD
 ### Cross-Link Documents
 - PRD → HLD (link from PRD to HLD)
 - HLD → ADR (link to all relevant ADRs)
-- RFC → HLD (link from RFC to HLD)
+- Spec → HLD (link from spec to HLD)
 - Runbook → HLD (link from runbook to architecture)
 
 ### Use Diagrams

package/src/templates/docs/spec-template.md

@@ -0,0 +1,229 @@
+# SPEC 0001: [Feature Title]
+
+**Status**: draft | review | approved | deprecated
+**Author**: [Your Name]
+**Created**: YYYY-MM-DD
+**Last Updated**: YYYY-MM-DD
+**Reviewers**: @architect, @tech-lead, @security
+
+---
+
+## Summary
+
+**One-sentence description**
+
+[Brief description of what this spec proposes]
+
+## Motivation
+
+**Why is this needed?**
+
+Explain the problem and why this specification is necessary:
+- What problem does this solve?
+- What user needs does it address?
+- What business value does it provide?
+
+**Link to PRD**: [PRD: Feature Name](../../strategy/prd-{feature}.md)
+
+## Proposal (API / Schema / Flow)
+
+**What are we proposing?**
+
+### API Design
+
+**Endpoint**: `POST /api/v1/{resource}`
+
+**Request**:
+```json
+{
+  "field1": "value",
+  "field2": 123,
+  "field3": {
+    "nested": "object"
+  }
+}
+```
+
+**Response**:
+```json
+{
+  "id": "uuid",
+  "field1": "value",
+  "field2": 123,
+  "created_at": "2025-01-01T00:00:00Z"
+}
+```
+
+**Status Codes**:
+- `200 OK`: Success
+- `400 Bad Request`: Invalid input
+- `401 Unauthorized`: Not authenticated
+- `403 Forbidden`: Not authorized
+- `500 Internal Server Error`: Server error
+
+### Data Schema
+
+**Database Schema**:
+```sql
+CREATE TABLE resource (
+    id UUID PRIMARY KEY DEFAULT gen_random_uuid(),
+    field1 VARCHAR(255) NOT NULL,
+    field2 INTEGER NOT NULL,
+    created_at TIMESTAMP NOT NULL DEFAULT NOW(),
+    updated_at TIMESTAMP NOT NULL DEFAULT NOW()
+);
+```
+
+### Flow Diagram
+
+**Process Flow**:
+```mermaid
+sequenceDiagram
+    participant Client
+    participant API
+    participant Service
+    participant Database
+
+    Client->>API: POST /api/v1/resource
+    API->>API: Validate request
+    API->>Service: Process request
+    Service->>Database: Insert record
+    Database-->>Service: Return ID
+    Service-->>API: Return response
+    API-->>Client: 200 OK
+```
+
+## Backwards Compatibility
+
+**Breaking changes?**
+
+- [ ] **No breaking changes** - Fully backwards compatible
+- [ ] **Breaking changes** - Describe impact:
+  - Change 1: Impact and migration plan
+  - Change 2: Impact and migration plan
+
+**Migration Strategy**:
+- How will existing clients be migrated?
+- What is the deprecation timeline?
+- Are there versioned endpoints?
+
+## Rollout Plan
+
+**How to deploy?**
+
+### Phase 1: Development
+- [ ] Implement feature
+- [ ] Write unit tests
+- [ ] Write integration tests
+
+### Phase 2: Testing
+- [ ] Deploy to staging
+- [ ] QA testing
+- [ ] Performance testing
+- [ ] Security testing
+
+### Phase 3: Production Rollout
+- [ ] Deploy to production
+- [ ] Feature flag (if applicable): `feature_{name}_enabled`
+- [ ] Gradual rollout: 5% → 25% → 50% → 100%
+- [ ] Monitor metrics
+
+### Rollback Plan
+- How to rollback if issues occur?
+- What are the rollback criteria?
+
+## Observability & SLO Impact
+
+**Monitoring and performance**
+
+### Metrics
+- **Latency**: p95 < XXms, p99 < XXms
+- **Throughput**: XX req/sec
+- **Error Rate**: < X%
+- **Availability**: XX% uptime
+
+### Logging
+- Log all requests/responses (excluding sensitive data)
+- Log errors with stack traces
+- Log performance metrics
+
+### Alerting
+- Alert if latency > XXms
+- Alert if error rate > X%
+- Alert if availability < XX%
+
+### Dashboards
+- Create Grafana dashboard for this feature
+- Link: [Dashboard URL]
+
+## Security / Compliance Considerations
+
+**Risks and mitigations**
+
+### Security
+- **Authentication**: How is the API authenticated?
+- **Authorization**: Who can access this API?
+- **Input Validation**: How is input validated?
+- **Data Encryption**: Is data encrypted in transit/at rest?
+- **Rate Limiting**: What are the rate limits?
+
+### Compliance
+- **GDPR**: Does this handle PII? How is data deleted?
+- **HIPAA**: (if applicable) Does this handle PHI?
+- **SOC 2**: Are access controls in place?
+
+### Threat Model
+- **Threat 1**: Description
+  - **Mitigation**: How we address it
+- **Threat 2**: Description
+  - **Mitigation**: How we address it
+
+## Alternatives
+
+**Other approaches considered**
+
+### Alternative 1: [Name]
+- **Description**: What is it?
+- **Pros**: Benefits
+- **Cons**: Drawbacks
+- **Why not chosen**: Reason
+
+### Alternative 2: [Name]
+- **Description**: What is it?
+- **Pros**: Benefits
+- **Cons**: Drawbacks
+- **Why not chosen**: Reason
+
+## Decision & Next Steps
+
+**Outcome and action items**
+
+### Decision
+- [ ] **Approved** - Proceed with implementation
+- [ ] **Rejected** - Do not proceed
+- [ ] **Deferred** - Revisit later
+
+### Next Steps
+- [ ] Create implementation tasks
+- [ ] Assign owners
+- [ ] Set timeline
+- [ ] Update roadmap
+
+### Action Items
+- [ ] **Task 1**: Description - Owner: @name - Due: YYYY-MM-DD
+- [ ] **Task 2**: Description - Owner: @name - Due: YYYY-MM-DD
+
+## Related Documentation
+
+- [PRD: Product Requirements](../../strategy/prd-{feature}.md)
+- [HLD: System Design](../hld-{system}.md)
+- [ADR: Architecture Decisions](../adr/)
+- [Runbook: Operations](../../operations/runbook-{service}.md)
+
+---
+
+**Approval**:
+- [ ] Architect: @name
+- [ ] Tech Lead: @name
+- [ ] Security: @name
+- [ ] Product Owner: @name

package/plugins/specweave/commands/inc.md

@@ -1,85 +0,0 @@
----
-name: inc
-description: Shorthand for /increment - Plan new Product Increment (PM-led process)
----
-
-# Plan Product Increment (Quick Alias)
-
-**⚡ Quick Alias**: This is a shorthand for `/increment`.
-
-This is the **most frequently used command** in SpecWeave's append-only increment workflow. Every new feature starts here.
-
----
-
-## Why This Alias Exists
-
-In an append-only increment workflow:
-- `/increment` is your starting point for ALL new work
-- You'll use it dozens/hundreds of times
-- Short alias saves time and mental overhead
-- Other commands are used less frequently (no aliases needed)
-
----
-
-## Usage
-
-```bash
-/inc "feature description"
-```
-
-**Examples**:
-```bash
-/inc "User authentication with JWT"
-/inc "Payment processing with Stripe"
-/inc "Real-time notifications"
-```
-
----
-
-## What This Does
-
-Runs the full `/increment` command, which:
-
-1. **Detects tech stack** (TypeScript, Python, Go, etc.)
-2. **PM-led planning**:
-   - Market research
-   - Create spec.md (WHAT & WHY)
-   - Create plan.md (HOW)
-   - **Auto-generate tasks.md** from plan
-   - Create tests.md (test strategy)
-3. **Strategic agent review**:
-   - Architect designs system
-   - Security reviews threats
-   - QA defines test strategy
-   - DevOps plans infrastructure
-4. **User review checkpoint**
-5. **Ready to build**: `/do 0001`
-
----
-
-## Typical Workflow
-
-```bash
-# 1. Plan increment (most common command - use alias!)
-/inc "User authentication"
-
-# 2. Review generated docs
-#    spec.md, plan.md, tasks.md, tests.md
-
-# 3. Build it
-/do 0001
-
-# 4. Validate quality (optional)
-/validate 0001 --quality
-
-# 5. Close when done
-/done 0001
-```
-
----
-
-**💡 Pro Tip**: Common commands have convenient short forms: `/inc`, `/do`, `/done`, `/validate`. For explicit namespacing or to avoid conflicts in brownfield projects, use `/specweave:inc`, `/specweave:do`, `/specweave:done`, `/specweave:validate`.
-
----
-
-For complete documentation, see `/increment`.

package/plugins/specweave/commands/list-increments.md

@@ -1,180 +0,0 @@
-# /list-increments - View All Increments
-
-**Command**: `/list-increments [options]`
-
-**Purpose**: View all increments with status, completion, and WIP tracking
-
-**Framework**: Framework-agnostic (works with all tech stacks)
-
----
-
-## Usage
-
-```bash
-/list-increments                          # All increments
-/list-increments --status in-progress     # Filter by status
-/list-increments --priority P1            # Filter by priority
-/list-increments --verbose                # Include task details
-```
-
-## Arguments
-
-- `--status` (optional): Filter by status (backlog, planned, in-progress, completed, closed)
-- `--priority` (optional): Filter by priority (P1, P2, P3)
-- `--verbose` (optional): Show task breakdown
-- `--wip-only` (optional): Show only in-progress increments
-
----
-
-## Output
-
-### Default View
-
-```
-📊 SpecWeave Increments Overview
-
-WIP Status: 2/2 (at limit) ⚠️
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-Status: in-progress (2)
-
-├── 001-core-framework [P1]
-│   ├── Progress: 88% (44/50 tasks)
-│   ├── Started: 2025-02-01 (8 months ago)
-│   ├── P1: 100% (30/30) ✅
-│   ├── P2: 80% (12/15) - 3 remaining
-│   ├── P3: 40% (2/5) - 3 remaining
-│   └── Ready to close (all P1 complete)
-│
-└── 003-jira-integration [P1]
-    ├── Progress: 40% (8/20 tasks)
-    ├── Started: 2025-09-15 (1 month ago)
-    ├── P1: 50% (5/10) ⏳
-    ├── P2: 30% (3/10)
-    └── In progress
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-Status: planned (3)
-
-├── 002-enhancements [P2] - Ready to start
-│   └── 15 tasks (transferred from 001)
-│
-├── 004-github-sync [P2] - Ready to start
-│   └── 18 tasks
-│
-└── 005-cost-optimizer-v2 [P3] - Ready to start
-    └── 10 tasks
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-Status: backlog (10 ideas)
-
-├── Design system improvements
-├── Performance optimizations
-├── Mobile app support
-├── Advanced analytics
-└── ... (6 more)
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-Status: closed (1)
-
-└── 000-project-setup [P1]
-    ├── Closed: 2025-01-15
-    ├── Completion: 100% (10/10 tasks)
-    └── Duration: 2 weeks
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-⚠️  Action needed:
-→ WIP limit reached (2/2)
-→ Close 001-core-framework to free WIP slot (88% complete, ready)
-→ Run: /close-increment 001
-
-Next steps:
-1. Close 001 to free WIP slot
-2. Start 002-enhancements
-```
-
-### Verbose View
-
-```bash
-/list-increments --verbose --status in-progress
-
-📊 In-Progress Increments (Verbose)
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-001-core-framework [P1]
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-Title: SpecWeave Core Framework
-Status: in-progress
-Priority: P1
-Started: 2025-02-01 (8 months ago)
-Progress: 88% (44/50 tasks)
-WIP Slot: 1
-
-Task Breakdown:
-  P1 (Critical): 100% (30/30) ✅
-    ✅ T001-T030: All complete
-
-  P2 (Important): 80% (12/15)
-    ✅ T031-T042: Complete
-    ⏳ T043: In progress
-    ❌ T044-T045: Not started
-
-  P3 (Nice-to-have): 40% (2/5)
-    ✅ T046-T047: Complete
-    ❌ T048-T050: Not started
-
-Dependencies: None
-Dependent increments: 002-enhancements, 004-github-sync
-
-Ready to close: YES (all P1 complete)
-Leftover tasks: 6 (3 P2, 3 P3)
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-```
-
-### Filtered Views
-
-```bash
-# Only P1 increments
-/list-increments --priority P1
-
-📊 P1 (Critical) Increments
-
-in-progress (2):
-  - 001-core-framework: 88% complete
-  - 003-jira-integration: 40% complete
-
-planned (0): None
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-# Only WIP increments
-/list-increments --wip-only
-
-📊 WIP Increments (2/2 - at limit)
-
-001-core-framework [P1]: 88% → Ready to close
-003-jira-integration [P1]: 40% → In progress
-
-⚠️ At WIP limit - close 001 to start new work
-```
-
----
-
-## Related Documentation
-
-- [CLAUDE.md](../../CLAUDE.md#increment-lifecycle-management) - Lifecycle guide
-- [.specweave/increments/README.md](../../.specweave/increments/README.md) - Increments overview
-
----
-
-**Command Type**: Status reporting
-**Framework Support**: All
-**Output**: Summary of all increments with actionable recommendations