feat: add /speckit.repo-story command and bump to v1.5.0

- New /speckit.repo-story command: evidence-based repository narrative
  generation for business and technical audiences
- Paired repo-story-context.sh and repo-story-context.ps1 scripts with
  commit-audit-ready JSON schema (anonymized roles, velocity metrics,
  quality signals, governance maturity)
- Branding sweep: consistent Spec Kit Spark / ASLCD messaging across
  all docs, CLI, and release generators
- README roadmap synced from stale v0.0.25 to v1.5.0
- CHANGELOG and release_notes.md updated for v1.5.0

Author: markhazleton

.documentation/critic-usage.md

@@ -480,5 +480,5 @@ If you encounter issues:
 
 ---
 
-*Part of the Spec Kit - Spec-Driven Development Toolkit*
+*Part of Spec Kit Spark - Adaptive System Life Cycle Development (ASLCD) Toolkit*
 *For more information: <https://github.com/MarkHazleton/spec-kit>*

.documentation/harvest-usage.md

@@ -339,5 +339,5 @@ If you encounter issues:
 
 ---
 
-*Part of the Spec Kit - Spec-Driven Development Toolkit*
+*Part of Spec Kit Spark - Adaptive System Life Cycle Development (ASLCD) Toolkit*
 *For more information: <https://github.com/MarkHazleton/spec-kit>*

.documentation/pr-review-usage.md

@@ -616,5 +616,5 @@ If you encounter issues or have questions:
 
 ---
 
-*Part of the Spec Kit - Spec-Driven Development Toolkit*  
+*Part of Spec Kit Spark - Adaptive System Life Cycle Development (ASLCD) Toolkit*  
 *For more information: <https://github.com/MarkHazleton/spec-kit>*

.documentation/site-audit-usage.md

@@ -401,5 +401,5 @@ If you encounter issues:
 
 ---
 
-*Part of the Spec Kit - Spec-Driven Development Toolkit*  
+*Part of Spec Kit Spark - Adaptive System Life Cycle Development (ASLCD) Toolkit*  
 *For more information: <https://github.com/MarkHazleton/spec-kit>*

.documentation/spec-driven-development.md

@@ -238,4 +238,4 @@ Software development needs better tools for maintaining alignment between intent
 
 ---
 
-> Part of the Spec Kit - Spec-Driven Development Toolkit
+> Part of Spec Kit Spark - Adaptive System Life Cycle Development (ASLCD) Toolkit

.github/workflows/release.yml

@@ -32,6 +32,24 @@ jobs:
         run: |
           chmod +x .github/workflows/scripts/get-next-version.sh
           .github/workflows/scripts/get-next-version.sh "${{ github.event.inputs.release_version || '' }}"
+      - name: Validate release version matches pyproject.toml
+        run: |
+          pyproject_version=$(grep -oE '^[[:space:]]*version[[:space:]]*=[[:space:]]*"[0-9]+\.[0-9]+\.[0-9]+"' pyproject.toml | head -n1 | sed -E 's/.*"([0-9]+\.[0-9]+\.[0-9]+)"/\1/')
+          if [ -z "$pyproject_version" ]; then
+            echo "Unable to read version from pyproject.toml"
+            exit 1
+          fi
+
+          release_version="${{ steps.get_tag.outputs.new_version }}"
+          release_version="${release_version#v}"
+
+          if [ "$pyproject_version" != "$release_version" ]; then
+            echo "Version mismatch: pyproject.toml=$pyproject_version release=$release_version"
+            echo "Update pyproject.toml before creating a release to keep Spec Kit Spark and Specify CLI in sync."
+            exit 1
+          fi
+
+          echo "Version parity check passed: $release_version"
       - name: Check if release already exists
         id: check_release
         run: |
@@ -57,9 +75,4 @@ jobs:
           .github/workflows/scripts/create-github-release.sh ${{ steps.get_tag.outputs.new_version }}
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-      - name: Update version in pyproject.toml (for release artifacts only)
-        if: steps.check_release.outputs.exists == 'false'
-        run: |
-          chmod +x .github/workflows/scripts/update-version.sh
-          .github/workflows/scripts/update-version.sh ${{ steps.get_tag.outputs.new_version }}
 

.github/workflows/scripts/README.md

@@ -16,7 +16,6 @@ This directory contains PowerShell versions of the GitHub Actions workflow scrip
 | `generate-release-notes.ps1` | Generate release notes from commits | `-NewVersion`, `-LastTag` |
 | `check-release-exists.ps1` | Check if release exists on GitHub | `-Version` |
 | `create-github-release.ps1` | Create GitHub release with packages | `-Version` |
-| `update-version.ps1` | Update pyproject.toml version | `-Version` |
 | `create-release-packages.ps1` | Create all agent template packages | `-Version` |
 
 ## Testing the Release Process Locally
@@ -61,16 +60,7 @@ This creates `release_notes.md` with your fork-specific branding.
 
 This creates all agent-specific ZIP packages in `.genreleases/` directory.
 
-### 5. Update pyproject.toml Version
-
-```powershell
-.\.github\workflows\scripts\update-version.ps1 `
-    -Version "v1.0.0"
-```
-
-**Note:** This is typically only needed for PyPI releases.
-
-### 6. Create GitHub Release (Requires `gh` CLI)
+### 5. Create GitHub Release (Requires `gh` CLI)
 
 ```powershell
 # Ensure you're authenticated with gh CLI
@@ -114,6 +104,8 @@ Write-Host ".\.github\workflows\scripts\create-github-release.ps1 -Version $vers
 - **GitHub Actions uses bash scripts** (`.sh` files) on `ubuntu-latest` runners
 - **PowerShell scripts** (`.ps1` files) are for local Windows testing only
 - Both versions are kept in sync for the same functionality
+- `pyproject.toml` is the single source of truth for release versioning
+- Explicit release versions must match `pyproject.toml` or the workflow will fail
 - Uses standard semantic versioning (vMAJOR.MINOR.PATCH)
 
 ## Differences from GitHub Actions

.github/workflows/scripts/generate-release-notes.ps1

@@ -44,7 +44,7 @@ if ($LastTag -eq "v0.0.0") {
 $releaseNotes = @"
 # Spec Kit Spark
 
-A community extension of GitHub Spec Kit with constitution-powered commands for enhanced development workflows. Part of the WebSpark demonstration suite.
+Spec Kit Spark is an Adaptive System Life Cycle Development (ASLCD) toolkit with constitution-powered commands and right-sized workflows. Part of the WebSpark demonstration suite.
 
 ## Spark-Specific Features
 
@@ -64,7 +64,7 @@ $commits
 
 ---
 
-*Based on upstream GitHub Spec Kit. Spec Kit Spark is a community extension that may contain features not yet available in the upstream project.*
+*Maintained as a fork of github/spec-kit. Spec Kit Spark is independently evolved and may contain Spark-specific capabilities not present upstream.*
 "@
 
 # Write to file

.github/workflows/scripts/generate-release-notes.sh

@@ -30,7 +30,7 @@ fi
 cat > release_notes.md << EOF
 # Spec Kit Spark
 
-A community extension of GitHub Spec Kit with constitution-powered commands for enhanced development workflows. Part of the WebSpark demonstration suite.
+Spec Kit Spark is an Adaptive System Life Cycle Development (ASLCD) toolkit with constitution-powered commands and right-sized workflows. Part of the WebSpark demonstration suite.
 
 ## Spark-Specific Features
 
@@ -50,7 +50,7 @@ $COMMITS
 
 ---
 
-*Based on upstream GitHub Spec Kit. Spec Kit Spark is a community extension that may contain features not yet available in the upstream project.*
+*Maintained as a fork of github/spec-kit. Spec Kit Spark is independently evolved and may contain Spark-specific capabilities not present upstream.*
 
 EOF
 

.github/workflows/scripts/get-next-version.ps1

@@ -2,16 +2,70 @@
 #requires -Version 7.0
 <#
 .SYNOPSIS
-    Calculate the next version based on the latest git tag
+    Calculate the next release version
 .DESCRIPTION
-    Get-next-version.ps1 - Calculate the next version and output GitHub Actions variables
+    Get-next-version.ps1 - Calculate the next version and output GitHub Actions variables.
+    Behavior mirrors the bash workflow script:
+      1. Explicit input version wins (and must match pyproject.toml when present)
+      2. Otherwise, prefer pyproject.toml version when not already tagged
+      3. Otherwise, increment the latest tag patch version
     Uses standard semantic versioning (MAJOR.MINOR.PATCH)
+.PARAMETER ExplicitVersion
+    Optional explicit version (e.g., 1.4.6 or v1.4.6)
 .EXAMPLE
     .\get-next-version.ps1
+.EXAMPLE
+    .\get-next-version.ps1 -ExplicitVersion "v1.4.6"
 #>
 
+param(
+    [string]$ExplicitVersion = ""
+)
+
 $ErrorActionPreference = 'Stop'
 
+function Normalize-Version {
+    param([string]$Raw)
+
+    if (-not $Raw) {
+        return $null
+    }
+
+    $trimmed = $Raw -replace '^v', ''
+    if ($trimmed -match '^\d+\.\d+\.\d+$') {
+        return "v$trimmed"
+    }
+
+    return $null
+}
+
+function Get-PyprojectVersion {
+    $pyprojectPath = "pyproject.toml"
+    if (-not (Test-Path $pyprojectPath)) {
+        return $null
+    }
+
+    $match = Select-String -Path $pyprojectPath -Pattern '^\s*version\s*=\s*"(\d+\.\d+\.\d+)"' | Select-Object -First 1
+    if ($match) {
+        return "v$($match.Matches[0].Groups[1].Value)"
+    }
+
+    return $null
+}
+
+function Increment-PatchVersion {
+    param([string]$Tag)
+
+    if ($Tag -match '^v(\d+)\.(\d+)\.(\d+)$') {
+        $major = [int]$matches[1]
+        $minor = [int]$matches[2]
+        $patch = [int]$matches[3] + 1
+        return "v$major.$minor.$patch"
+    }
+
+    return "v1.0.0"
+}
+
 # Get the latest tag, or use v0.0.0 if no tags exist
 try {
     $latestTag = git describe --tags --abbrev=0 2>$null
@@ -25,20 +79,42 @@ if ($env:GITHUB_OUTPUT) {
 }
 Write-Host "Latest tag: $latestTag"
 
-# Parse semantic version
-if ($latestTag -match '^v(\d+)\.(\d+)\.(\d+)') {
-    # Increment patch version
-    $major = [int]$matches[1]
-    $minor = [int]$matches[2]
-    $patch = [int]$matches[3]
-    $patch++
-    $newVersion = "v$major.$minor.$patch"
-} else {
-    # First release - start with v1.0.0
-    $newVersion = "v1.0.0"
+# 1) Explicit manual input wins
+if ($ExplicitVersion) {
+    $newVersion = Normalize-Version $ExplicitVersion
+    if (-not $newVersion) {
+        throw "Invalid explicit version '$ExplicitVersion'. Use MAJOR.MINOR.PATCH (optionally prefixed with v)."
+    }
+
+    $pyprojectVersion = Get-PyprojectVersion
+    if ($pyprojectVersion -and $newVersion -ne $pyprojectVersion) {
+        throw "Explicit version '$newVersion' does not match pyproject.toml version '$pyprojectVersion'. Update pyproject.toml first to keep Spec Kit Spark and Specify CLI versions in sync."
+    }
+
+    if ($env:GITHUB_OUTPUT) {
+        "new_version=$newVersion" | Out-File -FilePath $env:GITHUB_OUTPUT -Append -Encoding utf8
+    }
+    Write-Host "New version will be: $newVersion (source: explicit input)"
+    exit 0
 }
 
+# 2) Prefer pyproject.toml version when present and not already tagged
+$pyprojectVersion = Get-PyprojectVersion
+if ($pyprojectVersion) {
+    $tagExists = (& git rev-parse -q --verify "refs/tags/$pyprojectVersion" 2>$null)
+    if (-not $tagExists) {
+        if ($env:GITHUB_OUTPUT) {
+            "new_version=$pyprojectVersion" | Out-File -FilePath $env:GITHUB_OUTPUT -Append -Encoding utf8
+        }
+        Write-Host "New version will be: $pyprojectVersion (source: pyproject.toml)"
+        exit 0
+    }
+}
+
+# 3) Fallback: increment latest tag
+$newVersion = Increment-PatchVersion $latestTag
+
 if ($env:GITHUB_OUTPUT) {
     "new_version=$newVersion" | Out-File -FilePath $env:GITHUB_OUTPUT -Append -Encoding utf8
 }
-Write-Host "New version will be: $newVersion"
+Write-Host "New version will be: $newVersion (source: latest tag increment)"