get-shit-specd 0.2.0 → 0.3.0

package/README.md

@@ -140,6 +140,12 @@ bunx get-shit-specd update
 
 This updates GSS files while preserving your `spec-config.json`.
 
+## Acknowledgments
+
+GSS was heavily influenced by [get-shit-done (GSD)](https://github.com/glittercowboy/get-shit-done), an execution-focused workflow for Claude Code. Where GSD excels at **building** (phases, plans, atomic commits), GSS focuses on what comes **before** — ensuring you spec the right thing before you build it.
+
+They're designed to work together: GSS specs feed into GSD phases.
+
 ## License
 
 MIT

package/claude/get-shit-specd/VERSION

@@ -1 +1 @@
-0.2.0
+0.3.0

package/claude/get-shit-specd/templates/handoff-to-gsd.md

@@ -10,6 +10,7 @@ Translate a Ready spec into engineering-facing requirements. Engineering owns im
 
 ## Outputs
 - Requirement IDs mapped to acceptance scenarios
+- **Traceability matrix** (REQ → Acceptance → Spec section)
 - Risk notes and open questions
 - Success criteria summary
 

package/claude/get-shit-specd/templates/scope.md

@@ -1,24 +1,40 @@
 # Scope
 
-## In scope (v1 outcomes)
-1. {{IN_SCOPE_1}}
-2. {{IN_SCOPE_2}}
+## In Scope (v1 Outcomes)
+
+Requirements use stable IDs: `REQ-{SPEC_ID}-{PRIORITY}-{SEQ}`
+
+### P0 — Must Have
+
+- **REQ-{{SPEC_ID}}-P0-01:** {{P0_ITEM_1}}
+- **REQ-{{SPEC_ID}}-P0-02:** {{P0_ITEM_2}}
+
+### P1 — Should Have
+
+- **REQ-{{SPEC_ID}}-P1-01:** {{P1_ITEM_1}}
+
+### P2 — Nice to Have
+
+- **REQ-{{SPEC_ID}}-P2-01:** {{P2_ITEM_1}}
+
+## Out of Scope
 
-## Out of scope
 - {{OUT_SCOPE_1}}
 - {{OUT_SCOPE_2}}
 
 ## Dependencies
+
 - {{DEP_1}}
 
-## Rollout considerations
+## Rollout Considerations
 
 What matters for rollout (engineering determines approach):
 - Gradual exposure needed: {{GRADUAL_YN}}
 - Backout requirement: {{BACKOUT_NEED}}
 - Data migration scope: {{MIGRATION_SCOPE}}
 
-## Non-functional requirements
+## Non-Functional Requirements
+
 - Performance: {{PERF}}
 - Accessibility: {{A11Y}}
 - Security/privacy: {{SECURITY}}

package/claude/get-shit-specd/workflows/create-spec.md

@@ -69,6 +69,12 @@ Main flow writes:
 - 00-BRIEF.md (problem, JTBD, goal, constraints, risks)
 - 01-SCOPE.md (in/out with priorities, dependencies, NFRs)
 
+**Requirement ID Convention:**
+Generate stable IDs at spec time using format: `REQ-{SPEC_ID}-{PRIORITY}-{SEQ}`
+- Example: REQ-001-P0-01, REQ-001-P1-02
+- IDs remain stable across spec revisions
+- Enables traceability from spec → handoff → implementation
+
 These require intake context, so main flow handles them.
 </step>
 

package/claude/get-shit-specd/workflows/handoff.md

@@ -14,10 +14,26 @@ Read:
 </step>
 
 <step name="map_requirements">
-Create requirement IDs, each mapped to one or more acceptance scenarios.
+Use requirement IDs from SCOPE (REQ-{SPEC_ID}-{PRIORITY}-{SEQ}).
+Map each requirement to its acceptance scenarios from 04-ACCEPTANCE.md.
 Requirements describe OUTCOMES, not tasks.
 </step>
 
+<step name="generate_traceability_matrix">
+Create a traceability matrix linking:
+- Requirement ID → Acceptance scenario numbers → Spec source file:section
+
+Example format:
+| REQ ID | Acceptance Scenarios | Source |
+|--------|---------------------|--------|
+| REQ-001-P0-01 | 1.1.1, 1.1.2, 1.1.3 | 01-SCOPE.md#email-signup |
+
+This enables:
+- Coverage verification (every REQ has acceptance criteria)
+- Change impact analysis (which acceptance scenarios if REQ changes)
+- Engineering trace-back to product intent
+</step>
+
 <step name="summarize_context">
 Extract from BRIEF:
 - Problem statement (why this matters)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "get-shit-specd",
-  "version": "0.2.0",
+  "version": "0.3.0",
   "description": "Spec-first development workflow for Claude Code. Transform vague ideas into engineering-ready specs.",
   "type": "module",
   "bin": {