feat: use .documentation/ instead of .specify/ as Spark fork identifier

- Updated all templates, scripts, and documentation to use .documentation/
- Modified CLI to create .documentation/ directory instead of .specify/
- Updated build scripts to output .documentation/ in release packages
- This distinguishes Spec Kit Spark from upstream GitHub spec-kit
- Consolidates all AI agent output in .documentation/ separate from code

Author: markhazleton

.devcontainer/devcontainer.json

@@ -68,8 +68,8 @@
 			"speckit.implement": true
 		},
 		"chat.tools.terminal.autoApprove": {
-			".specify/scripts/bash/": true,
-			".specify/scripts/powershell/": true
+			".documentation/scripts/bash/": true,
+			".documentation/scripts/powershell/": true
 		}
       }
     }

.documentation/installation.md

@@ -38,7 +38,7 @@ uvx --from git+https://github.com/MarkHazleton/spec-kit.git specify init --here
 uvx --from git+https://github.com/MarkHazleton/spec-kit.git specify init .
 ```
 
-This adds the Spec Kit structure (`.specify/`, `.documentation/memory/`, templates, scripts) to your existing project without disrupting your current files.
+This adds the Spec Kit structure (`.documentation/`, `.documentation/memory/`, templates, scripts) to your existing project without disrupting your current files.
 
 > [!TIP]
 > **Brownfield Tip**: After initialization, use the `/speckit.discover-constitution` command to help create a constitution from your existing codebase patterns. This analyzes your code conventions, architecture decisions, and established practices to draft a constitution that reflects how your project already works.
@@ -104,7 +104,7 @@ These commands only need a constitution and work independently on any codebase:
 - `/speckit.pr-review` - Review pull requests against constitution
 - `/speckit.site-audit` - Comprehensive codebase audit for security, quality, and compliance
 
-The `.specify/scripts` directory will contain both `.sh` and `.ps1` scripts.
+The `.documentation/scripts` directory will contain both `.sh` and `.ps1` scripts.
 
 ## Troubleshooting
 

.documentation/upgrade.md

@@ -51,8 +51,8 @@ When Spec Kit releases new features (like new slash commands or updated template
 Running `specify init --here --force` will update:
 
 - ✅ **Slash command files** (`.claude/commands/`, `.github/prompts/`, etc.)
-- ✅ **Script files** (`.specify/scripts/`)
-- ✅ **Template files** (`.specify/templates/`)
+- ✅ **Script files** (`.documentation/scripts/`)
+- ✅ **Template files** (`.documentation/templates/`)
 - ✅ **Shared memory files** (`.documentation/memory/`) - **⚠️ See warnings below**
 
 ### What stays safe?
@@ -126,11 +126,11 @@ git restore .documentation/memory/constitution.md
 
 ### 2. Custom template modifications
 
-If you customized any templates in `.specify/templates/`, the upgrade will overwrite them. Back them up first:
+If you customized any templates in `.documentation/templates/`, the upgrade will overwrite them. Back them up first:
 
 ```bash
 # Back up custom templates
-cp -r .specify/templates .specify/templates-backup
+cp -r .documentation/templates .documentation/templates-backup
 
 # After upgrade, merge your changes back manually
 ```
@@ -179,7 +179,7 @@ git restore .documentation/memory/constitution.md
 ```bash
 # 1. Back up customizations
 cp .documentation/memory/constitution.md /tmp/constitution-backup.md
-cp -r .specify/templates /tmp/templates-backup
+cp -r .documentation/templates /tmp/templates-backup
 
 # 2. Upgrade CLI
 uv tool install specify-cli --force --from git+https://github.com/MarkHazleton/spec-kit.git
@@ -327,15 +327,15 @@ This warning appears when you run `specify init --here` (or `specify init .`) in
 
 1. **The directory has existing content** - In the example, 25 files/folders
 2. **Files will be merged** - New template files will be added alongside your existing files
-3. **Some files may be overwritten** - If you already have Spec Kit files (`.claude/`, `.specify/`, etc.), they'll be replaced with the new versions
+3. **Some files may be overwritten** - If you already have Spec Kit files (`.claude/`, `.documentation/`, etc.), they'll be replaced with the new versions
 
 **What gets overwritten:**
 
 Only Spec Kit infrastructure files:
 
 - Agent command files (`.claude/commands/`, `.github/prompts/`, etc.)
-- Scripts in `.specify/scripts/`
-- Templates in `.specify/templates/`
+- Scripts in `.documentation/scripts/`
+- Templates in `.documentation/templates/`
 - Memory files in `.documentation/memory/` (including constitution)
 
 **What stays untouched:**

.github/workflows/scripts/create-release-packages.ps1

@@ -61,9 +61,11 @@ New-Item -ItemType Directory -Path $GenReleasesDir -Force | Out-Null
 function Rewrite-Paths {
     param([string]$Content)
 
-    $Content = $Content -replace '(/?)\bmemory/', '.specify/memory/'
-    $Content = $Content -replace '(/?)\bscripts/', '.specify/scripts/'
-    $Content = $Content -replace '(/?)\btemplates/', '.specify/templates/'
+    # Spec Kit Spark uses .documentation/ instead of .specify/ to distinguish from upstream
+    $Content = $Content -replace '(/?)\.specify/', '.documentation/'
+    $Content = $Content -replace '(/?)\bmemory/', '.documentation/memory/'
+    $Content = $Content -replace '(/?)\bscripts/', '.documentation/scripts/'
+    $Content = $Content -replace '(/?)\btemplates/', '.documentation/templates/'
     return $Content
 }
 
@@ -212,13 +214,13 @@ function Build-Variant {
     New-Item -ItemType Directory -Path $baseDir -Force | Out-Null
 
     # Copy base structure but filter scripts by variant
-    $specDir = Join-Path $baseDir ".specify"
+    $specDir = Join-Path $baseDir ".documentation"
     New-Item -ItemType Directory -Path $specDir -Force | Out-Null
 
     # Copy memory directory
     if (Test-Path "memory") {
         Copy-Item -Path "memory" -Destination $specDir -Recurse -Force
-        Write-Host "Copied memory -> .specify"
+        Write-Host "Copied memory -> .documentation"
     }
 
     # Only copy the relevant script variant directory
@@ -230,13 +232,13 @@ function Build-Variant {
             'sh' {
                 if (Test-Path "scripts/bash") {
                     Copy-Item -Path "scripts/bash" -Destination $scriptsDestDir -Recurse -Force
-                    Write-Host "Copied scripts/bash -> .specify/scripts"
+                    Write-Host "Copied scripts/bash -> .documentation/scripts"
                 }
             }
             'ps' {
                 if (Test-Path "scripts/powershell") {
                     Copy-Item -Path "scripts/powershell" -Destination $scriptsDestDir -Recurse -Force
-                    Write-Host "Copied scripts/powershell -> .specify/scripts"
+                    Write-Host "Copied scripts/powershell -> .documentation/scripts"
                 }
             }
         }
@@ -261,7 +263,7 @@ function Build-Variant {
             New-Item -ItemType Directory -Path $destFileDir -Force | Out-Null
             Copy-Item -Path $_.FullName -Destination $destFile -Force
         }
-        Write-Host "Copied templates -> .specify/templates"
+        Write-Host "Copied templates -> .documentation/templates"
     }
 
     # Generate agent-specific command files

.github/workflows/scripts/create-release-packages.sh

@@ -31,10 +31,12 @@ mkdir -p "$GENRELEASES_DIR"
 rm -rf "$GENRELEASES_DIR"/* || true
 
 rewrite_paths() {
+  # Spec Kit Spark uses .documentation/ instead of .specify/ to distinguish from upstream
   sed -E \
-    -e 's@(/?)memory/@.specify/memory/@g' \
-    -e 's@(/?)scripts/@.specify/scripts/@g' \
-    -e 's@(/?)templates/@.specify/templates/@g'
+    -e 's@(/?)\.specify/@.documentation/@g' \
+    -e 's@(/?)memory/@.documentation/memory/@g' \
+    -e 's@(/?)scripts/@.documentation/scripts/@g' \
+    -e 's@(/?)templates/@.documentation/templates/@g'
 }
 
 generate_commands() {
@@ -128,29 +130,29 @@ build_variant() {
   mkdir -p "$base_dir"
 
   # Copy base structure but filter scripts by variant
-  SPEC_DIR="$base_dir/.specify"
+SPEC_DIR="$base_dir/.documentation"
   mkdir -p "$SPEC_DIR"
-  
-  [[ -d memory ]] && { cp -r memory "$SPEC_DIR/"; echo "Copied memory -> .specify"; }
+
+  [[ -d memory ]] && { cp -r memory "$SPEC_DIR/"; echo "Copied memory -> .documentation"; }
 
   # Only copy the relevant script variant directory
   if [[ -d scripts ]]; then
     mkdir -p "$SPEC_DIR/scripts"
     case $script in
       sh)
-        [[ -d scripts/bash ]] && { cp -r scripts/bash "$SPEC_DIR/scripts/"; echo "Copied scripts/bash -> .specify/scripts"; }
+        [[ -d scripts/bash ]] && { cp -r scripts/bash "$SPEC_DIR/scripts/"; echo "Copied scripts/bash -> .documentation/scripts"; }
         # Copy any script files that aren't in variant-specific directories
         find scripts -maxdepth 1 -type f -exec cp {} "$SPEC_DIR/scripts/" \; 2>/dev/null || true
         ;;
       ps)
-        [[ -d scripts/powershell ]] && { cp -r scripts/powershell "$SPEC_DIR/scripts/"; echo "Copied scripts/powershell -> .specify/scripts"; }
+        [[ -d scripts/powershell ]] && { cp -r scripts/powershell "$SPEC_DIR/scripts/"; echo "Copied scripts/powershell -> .documentation/scripts"; }
         # Copy any script files that aren't in variant-specific directories
         find scripts -maxdepth 1 -type f -exec cp {} "$SPEC_DIR/scripts/" \; 2>/dev/null || true
         ;;
     esac
   fi
 
-  [[ -d templates ]] && { mkdir -p "$SPEC_DIR/templates"; find templates -type f -not -path "templates/commands/*" -not -name "vscode-settings.json" -exec cp --parents {} "$SPEC_DIR"/ \; ; echo "Copied templates -> .specify/templates"; }
+  [[ -d templates ]] && { mkdir -p "$SPEC_DIR/templates"; find templates -type f -not -path "templates/commands/*" -not -name "vscode-settings.json" -exec cp --parents {} "$SPEC_DIR"/ \; ; echo "Copied templates -> .documentation/templates"; }
 
   # NOTE: We substitute {ARGS} internally. Outward tokens differ intentionally:
   #   * Markdown/prompt (claude, copilot, cursor-agent, opencode): $ARGUMENTS

README.md

@@ -797,7 +797,7 @@ At this stage, your project folder contents should resemble the following:
 │   └── specs
 │       └── 001-create-taskify
 │           └── spec.md
-└── .specify
+└── .documentation
     ├── scripts
     │   ├── check-prerequisites.sh
     │   ├── common.sh
@@ -867,7 +867,7 @@ The output of this step will include a number of implementation detail documents
 │           ├── quickstart.md
 │           ├── research.md
 │           └── spec.md
-└── .specify
+└── .documentation
     ├── scripts
     │   ├── check-prerequisites.sh
     │   ├── common.sh

scripts/bash/create-new-feature.sh

@@ -71,7 +71,7 @@ fi
 find_repo_root() {
     local dir="$1"
     while [ "$dir" != "/" ]; do
-        if [ -d "$dir/.git" ] || [ -d "$dir/.specify" ]; then
+        if [ -d "$dir/.git" ] || [ -d "$dir/.documentation" ]; then
             echo "$dir"
             return 0
         fi
@@ -280,7 +280,7 @@ fi
 FEATURE_DIR="$SPECS_DIR/$BRANCH_NAME"
 mkdir -p "$FEATURE_DIR"
 
-TEMPLATE="$REPO_ROOT/.specify/templates/spec-template.md"
+TEMPLATE="$REPO_ROOT/.documentation/templates/spec-template.md"
 SPEC_FILE="$FEATURE_DIR/spec.md"
 if [ -f "$TEMPLATE" ]; then cp "$TEMPLATE" "$SPEC_FILE"; else touch "$SPEC_FILE"; fi
 

scripts/bash/setup-plan.sh

@@ -37,7 +37,7 @@ check_feature_branch "$CURRENT_BRANCH" "$HAS_GIT" || exit 1
 mkdir -p "$FEATURE_DIR"
 
 # Copy plan template if it exists
-TEMPLATE="$REPO_ROOT/.specify/templates/plan-template.md"
+TEMPLATE="$REPO_ROOT/.documentation/templates/plan-template.md"
 if [[ -f "$TEMPLATE" ]]; then
     cp "$TEMPLATE" "$IMPL_PLAN"
     echo "Copied plan template to $IMPL_PLAN"

scripts/bash/update-agent-context.sh

@@ -77,7 +77,7 @@ Q_FILE="$REPO_ROOT/AGENTS.md"
 BOB_FILE="$REPO_ROOT/AGENTS.md"
 
 # Template file
-TEMPLATE_FILE="$REPO_ROOT/.specify/templates/agent-file-template.md"
+TEMPLATE_FILE="$REPO_ROOT/.documentation/templates/agent-file-template.md"
 
 # Global variables for parsed plan data
 NEW_LANG=""

scripts/powershell/create-new-feature.ps1

@@ -41,7 +41,7 @@ $featureDesc = ($FeatureDescription -join ' ').Trim()
 function Find-RepositoryRoot {
     param(
         [string]$StartDir,
-        [string[]]$Markers = @('.git', '.specify')
+        [string[]]$Markers = @('.git', '.documentation')
     )
     $current = Resolve-Path $StartDir
     while ($true) {
@@ -254,7 +254,7 @@ if ($hasGit) {
 $featureDir = Join-Path $specsDir $branchName
 New-Item -ItemType Directory -Path $featureDir -Force | Out-Null
 
-$template = Join-Path $repoRoot '.specify/templates/spec-template.md'
+$template = Join-Path $repoRoot '.documentation/templates/spec-template.md'
 $specFile = Join-Path $featureDir 'spec.md'
 if (Test-Path $template) { 
     Copy-Item $template $specFile -Force