specweave 0.3.10 → 0.3.12

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.
package/CLAUDE.md CHANGED
@@ -101,7 +101,7 @@ src/ ← SOURCE OF TRUTH (version controlled)
101
101
  .specweave/ ← FRAMEWORK DATA (always present)
102
102
  ├── increments/ ← Feature development
103
103
  ├── docs/ ← Strategic documentation
104
- └── config.yaml Configuration
104
+ └── logs/ Logs and execution history
105
105
  ```
106
106
 
107
107
  **Rules**:
@@ -191,7 +191,6 @@ specweave/
191
191
  │ ├── docs/
192
192
  │ │ ├── internal/ # Strategic docs
193
193
  │ │ └── public/ # Published docs
194
- │ ├── config.yaml # SpecWeave's config
195
194
  │ └── logs/
196
195
 
197
196
  ├── tests/
@@ -259,6 +258,28 @@ All AI-generated files MUST go into increment folders:
259
258
  - ✅ Clear context (all files for a feature in one place)
260
259
  - ✅ No root clutter
261
260
 
261
+ ### Runtime Artifacts (NOT Source Controlled)
262
+
263
+ **Logs and ephemeral files** should NEVER be committed:
264
+
265
+ ```
266
+ ❌ NEVER COMMIT:
267
+ .specweave/logs/ # Framework runtime logs
268
+ .specweave/logs/last-hook-fire # Hook execution timestamps
269
+ .specweave/increments/*/logs/ # Increment execution logs
270
+ .specweave/cache/ # Temporary cache
271
+ *.tmp # Temporary files
272
+ ```
273
+
274
+ **Why?**
275
+ - ✅ Logs are execution artifacts, not source code
276
+ - ✅ They change on every run (noise in git history)
277
+ - ✅ They cause unnecessary merge conflicts
278
+ - ✅ They bloat the repository over time
279
+ - ✅ They're developer-specific, not shared state
280
+
281
+ **Enforcement**: `.gitignore` excludes these patterns automatically.
282
+
262
283
  ---
263
284
 
264
285
  ## Development Workflow
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "specweave",
3
- "version": "0.3.10",
3
+ "version": "0.3.12",
4
4
  "description": "Replace vibe coding with spec-driven development. Smart workflow: /specweave inc auto-closes previous, /specweave build auto-resumes, /specweave progress shows status. PM-led planning, 10 agents, 35+ skills. spec-weave.com",
5
5
  "type": "module",
6
6
  "main": "dist/index.js",
@@ -548,36 +548,10 @@ Check progress: /list-increments
548
548
 
549
549
  ## Configuration
550
550
 
551
- **File**: `.specweave/config.yaml`
552
-
553
- ```yaml
554
- increment_closure:
555
- pm_validation:
556
- enabled: true # ← MUST be true
557
- strict_mode: true # Require all 3 gates to pass
558
-
559
- gates:
560
- tasks:
561
- require_p1_complete: true
562
- require_p2_complete: false # P2 can be deferred
563
- allow_scope_transfer: true
564
-
565
- tests:
566
- require_all_passing: true
567
- min_coverage: 80 # 80% coverage required
568
- allow_skipped: false
569
-
570
- documentation:
571
- require_claude_md: true
572
- require_readme: true
573
- require_changelog: true # For public APIs
574
- allow_inline_only: false
575
-
576
- scope_creep:
577
- detect: true
578
- max_additional_tasks: 10 # Warn if >10 tasks added
579
- auto_transfer: true # Auto-transfer to next increment
580
- ```
551
+ All PM validation settings use sensible defaults:
552
+ - Tasks: P1 required, P2 can be deferred
553
+ - Tests: All tests must pass, 80% coverage required
554
+ - Documentation: CLAUDE.md, README.md, and CHANGELOG.md must be updated
581
555
 
582
556
  ---
583
557
 
@@ -468,27 +468,11 @@ Your choice? [A/B/C] _
468
468
 
469
469
  ## Configuration
470
470
 
471
- **File**: `.specweave/config.yaml`
472
-
473
- ```yaml
474
- workflow:
475
- auto_close:
476
- enabled: true # Enable auto-close in /next
477
- strict_mode: true # Require all 3 gates to pass
478
- suggest_next: true # Suggest next work after closure
479
-
480
- pm_validation:
481
- gates:
482
- tasks:
483
- require_p1_complete: true
484
- require_p2_complete: false # P2 can be deferred
485
- tests:
486
- require_all_passing: true
487
- min_coverage: 80
488
- documentation:
489
- require_claude_md: true
490
- require_readme: true
491
- ```
471
+ Auto-close uses sensible defaults:
472
+ - PM validation gates must pass (tasks, tests, docs)
473
+ - P1 tasks required, P2 can be deferred
474
+ - Tests must pass with 80% coverage
475
+ - Documentation must be updated
492
476
 
493
477
  ---
494
478
 
@@ -22,7 +22,6 @@ You are helping the user validate a SpecWeave increment with optional AI-powered
22
22
  - `--quality`: Run AI quality assessment (LLM-as-judge, ~2k tokens, 1-2 minutes)
23
23
  - `--export`: Export AI suggestions to tasks.md automatically
24
24
  - `--fix`: Auto-fix HIGH priority issues (experimental, requires confirmation)
25
- - `--always`: Save quality assessment as default in config.yaml
26
25
 
27
26
  ## Workflow
28
27
 
@@ -132,8 +131,7 @@ Action required:
132
131
  **Check in this order**:
133
132
 
134
133
  1. **If `--quality` flag provided**: Run quality assessment (skip prompt)
135
- 2. **Else if `config.yaml` has `validation.quality_judge.always_run: true`**: Run quality assessment (skip prompt)
136
- 3. **Else**: Prompt user
134
+ 2. **Else**: Prompt user
137
135
 
138
136
  **Prompt format** (if needed):
139
137
  ```
@@ -730,53 +728,7 @@ fi
730
728
 
731
729
  ## Configuration
732
730
 
733
- **File**: `.specweave/config.yaml`
734
-
735
- ```yaml
736
- validation:
737
- enabled: true
738
- auto_validate: true
739
- severity_threshold: warning
740
-
741
- # Quality judge settings
742
- quality_judge:
743
- enabled: true
744
- always_run: false # Set to true with --always flag
745
- auto_prompt: true # Prompt user if always_run is false
746
- thresholds:
747
- excellent: 90
748
- good: 80
749
- acceptable: 70
750
- needs_work: 0
751
- dimensions:
752
- clarity: true
753
- testability: true
754
- completeness: true
755
- feasibility: true
756
- maintainability: true
757
- edge_cases: true
758
- max_tokens: 2000
759
- export_to_tasks: false # Set to true to auto-export suggestions
760
-
761
- # Auto-fix settings
762
- auto_fix:
763
- enabled: true
764
- require_confirmation: true # Always ask before applying fixes
765
- max_fixes_per_run: 5 # Limit fixes to avoid large changes
766
-
767
- # Report settings
768
- reports:
769
- save_to: "reports/validation-report.md"
770
- format: markdown
771
- include_line_numbers: true
772
- include_suggestions: true
773
- include_history: true
774
-
775
- # Hooks
776
- hooks:
777
- post_document_save: true
778
- pre_implementation: true
779
- ```
731
+ All validation settings use sensible defaults. Quality assessment is prompted each time unless `--quality` flag is used.
780
732
 
781
733
  ## Related Commands
782
734
 
@@ -260,17 +260,10 @@ Suggestions: 3 high priority
260
260
  [Full report shown above]
261
261
  ```
262
262
 
263
- ### Example 2: Always-On Mode
264
-
265
- ```yaml
266
- # config.yaml
267
- validation:
268
- quality_judge:
269
- always_run: true
270
- ```
263
+ ### Example 2: Auto-Run Mode
271
264
 
272
265
  ```bash
273
- User: "Validate increment 001"
266
+ User: "Validate increment 001 --quality"
274
267
 
275
268
  increment-quality-judge:
276
269
  ✅ Rule-based: 120/120 passed
@@ -439,9 +432,9 @@ Show detailed report
439
432
  **When:** User selects "Export to tasks"
440
433
  **Then:** 3 tasks added to tasks.md with priority labels
441
434
 
442
- ### TC-005: Always-On Mode
443
- **Given:** config.yaml has always_run: true
444
- **When:** User requests validation ("validate quality of increment 001")
435
+ ### TC-005: Auto-Run Mode
436
+ **Given:** User provides --quality flag
437
+ **When:** User requests validation ("validate increment 001 --quality")
445
438
  **Then:** Quality check runs automatically without prompt
446
439
 
447
440
  ## Best Practices