fix: remove issue tracker integration

Author: kanfil

CHANGELOG.md

@@ -2,6 +2,20 @@
 
 All notable changes to the Specify CLI and templates are documented here.
 
+## [0.3.46] - 2026-04-13
+
+### Changed
+
+- **Removed issue tracker integration**: Cleaned up `@issue-tracker` references and traceability features
+  - Removed Smart Trace Validation section from `/spec.analyze` command
+  - Removed issue tracker references from docs/quickstart.md examples
+  - Removed issue tracker integration from levelup trace scripts and templates
+  - Removed issue tracker integration from implement command
+
+### Fixed
+
+- **RELEASE.md**: Trimmed to release instructions only (removed Lessons Learned historical debug notes)
+
 ## [0.3.45] - 2026-04-13
 
 ### Fixed

RELEASE.md

@@ -221,141 +221,4 @@ git push origin "agentic-sdlc-v$VERSION"
 
 echo "Released agentic-sdlc-v$VERSION"
 ```
-
-## Lessons Learned
-
-### Session 2026-04-11: Path Resolution Bug
-
-**Problem**: `common.sh` used `$repo_root/memory` but constitution stored in `.specify/memory/`
-
-**Impact**: Validation script failed silently, `get_feature_paths()` returned wrong path
-
-**Fix**: Changed line 318 to `$repo_root/.specify/memory`
-
-**Prevention**: Always verify path consistency between:
-- `common.sh` `memory_dir` variable
-- Where files are actually stored (`.specify/memory/`)
-- Template references
-
-### Session 2026-04-11: Tag Before Version Update
-
-**Problem**: Created tag `agentic-sdlc-v0.3.32` before updating `pyproject.toml`
-
-**Impact**: Tag pointed to commit with wrong version (0.3.31), installation showed old version
-
-**Fix**: Re-tagged at correct commit after updating version file
-
-**Prevention**: Always update `pyproject.toml` BEFORE creating tag
-
-### Session 2026-04-12: Check Remote Before Local Version
-
-**Problem**: Local files showed version `0.3.36` but remote/origin was at `0.3.35`. Attempted to bump to `0.3.37` based on stale local state.
-
-**Impact**: Confusion about which version to release; wasted time correcting version numbers.
-
-**Fix**: Checked `git show origin/main:pyproject.toml` to verify actual remote version.
-
-**Prevention**: Before any release, always verify remote state:
-
-```bash
-# Check what's actually pushed (not local state)
-git fetch origin
-git show origin/main:pyproject.toml | grep "^version"
-
-# Compare with local
-cat pyproject.toml | grep "^version"
-
-# Check for uncommitted changes
-git status
-```
-
-**Key insight**: Local uncommitted changes can make `pyproject.toml` show a different version than what's actually released. Always verify against origin before deciding the next version number.
-
-### Session 2026-04-13: Releasing from a Submodule
-
-**Problem**: When working in a parent repo with spec-kit as a submodule, `git commit` and `git tag` commands run in the wrong directory (parent repo instead of submodule).
-
-**Impact**: 
-- Tag `agentic-sdlc-v0.3.40` was initially created in the parent repo instead of the spec-kit submodule
-- Commands like `git diff --stat` showed changes but `git commit` failed with "no changes added"
-
-**Fix**: Always explicitly set the working directory when releasing from a submodule:
-```bash
-cd /path/to/agentic-sdlc-spec-kit
-git add -A && git commit -m "fix: description"
-git tag agentic-sdlc-vX.Y.Z
-git push origin main
-git push origin agentic-sdlc-vX.Y.Z
-```
-
-**Prevention**: Before any release commit/tag operation:
-```bash
-# Verify you're in the correct directory
-pwd  # Should show .../agentic-sdlc-spec-kit
-
-# Verify pyproject.toml exists in current directory
-ls pyproject.toml
-
-# Then proceed with release
-```
-
-**Key insight**: When spec-kit is used as a submodule, always navigate into the submodule directory before running any git operations for releases.
-
-### Session 2026-04-13: Tag Format Convention
-
-**Problem**: Used `v0.3.43` tag format instead of the project's `agentic-sdlc-vX.Y.Z` convention.
-
-**Impact**: Inconsistent tag naming, potential confusion with upstream spec-kit tags.
-
-**Correct format**: `agentic-sdlc-v0.3.43` (not `v0.3.43`)
-
-**Prevention**: Before tagging, verify the format:
-```bash
-# Check existing tag format
-git tag | grep "^agentic-sdlc-v" | sort -V | tail -3
-
-# Use consistent format
-git tag agentic-sdlc-vX.Y.Z
-```
-
-**Key insight**: This fork uses the `agentic-sdlc-v` prefix to distinguish from upstream `spec-kit` tags.
-
-### Session 2026-04-13: Draft Release Not Visible
-
-**Problem**: The `release.yml` workflow created a release as "Draft", which is not visible on the public releases page.
-
-**Impact**: Release `agentic-sdlc-v0.3.43` existed but showed as "Draft" - users couldn't see it at https://github.com/tikalk/agentic-sdlc-spec-kit/releases
-
-**Fix**: Publish the draft release using the GitHub CLI:
-```bash
-gh release edit <tag> --draft=false
-```
-
----
-
-### Session 2026-04-13: Hook Commands Should Be Lightweight
-
-**Problem**: The `before_specify` hook pointed to `adlc.product.specify`, a full interactive product exploration command (~535 lines). When no PDRs existed, it still ran and generated noisy AI output like "No PDR file found - skipping Phase 2".
-
-**Impact**: Every `/spec.specify` invocation triggered noisy output even for users not using the product extension workflow.
-
-**Fix**: Created lightweight `adlc.product.link` command that:
-- Checks for PDRs in team-directives, memory, and drafts locations
-- **Silent exit** if no PDRs exist (no output at all)
-- Full selection flow only if PDRs exist
-
-**Prevention**: When creating hooks for commands:
-- Design hook-specific commands to be lightweight
-- Use silent exit patterns when data doesn't exist
-- Don't use full interactive commands as hooks (too much noise)
-- Consider the "no data" case as the default, not an error
-
-**Prevention**: After tagging and pushing, verify the release is visible. If it shows as "Draft" in `gh release list`, publish it:
-```bash
-# Check release status
-gh release list
-
-# If draft, publish it
-gh release edit <tag> --draft=false
-```
 ```

docs/quickstart.md

@@ -33,19 +33,19 @@ This guide will help you get started with Spec-Driven Development using Agentic
 **Alignment with 12 Factors:** This stage focuses on [III. Mission Definition](https://tikalk.github.io/agentic-sdlc-12-factors/content/mission-definition.html), translating intent into formal, version-controlled specifications.
 
 1. **Craft the Directive (`/specify`)**  
-   **Action:** Author a single, comprehensive natural-language directive that blends the issue tracker mission, personas, constraints, and any clarifications.  
+   **Action:** Author a single, comprehensive natural-language directive that blends the mission, personas, constraints, and any clarifications.  
    **Purpose:** Front-load human judgment so the AI can draft an accurate `spec.md` aligned with the constitution.
 2. **Execute the Command**  
-   **Action:** Run `/specify` in the IDE; Agentic SDLC Spec Kit loads `memory/constitution.md`, resolves `@team/...` references against the directives repo, and captures any `@issue-tracker ISSUE-###` reference in the prompt so the resulting spec links back to the originating ticket.  
-   **Purpose:** Generates the structured specification artifact under `specs/<feature>/spec.md` with shared principles and traceability already in context.
+   **Action:** Run `/specify` in the IDE; Agentic SDLC Spec Kit loads `memory/constitution.md`, resolves `@team/...` references against the directives repo.  
+   **Purpose:** Generates the structured specification artifact under `specs/<feature>/spec.md` with shared principles already in context.
 3. **Review and Commit**  
    **Action:** Perform a macro-review of the generated `spec.md`, refine if needed, then commit it.  
    **Purpose:** Locks in the requirements that all later stages will honor.
 
 **Example Command:**
 
 ```text
-/specify "Generate the specification for the feature in @issue-tracker ISSUE-123. The target user is the @team/personas/data_analyst.md. The operation must be asynchronous to handle large dashboards. The PDF title must include the dashboard name and an export timestamp."
+/specify "Generate the specification for a feature. The target user is the @team/personas/data_analyst.md. The operation must be asynchronous to handle large dashboards. The PDF title must include the dashboard name and an export timestamp."
 ```
 
 **Outcome:** A committed `spec.md` ready to drive planning in Stage 2.

extensions/levelup/commands/trace.md

@@ -84,7 +84,6 @@ Human-friendly 3-part narrative placed at the top:
 - Testing strategy (TDD, risk-based)
 - Process decisions (SYNC/ASYNC breakdown)
 - Integration choices (APIs, external services)
-- Issue tracking integration
 - Dynamic count based on feature complexity
 - Example: "1. Chose React with TypeScript 2. Implemented TDD approach 3. Applied dual execution loop..."
 
@@ -94,7 +93,6 @@ Human-friendly 3-part narrative placed at the top:
 - Quality gate pass rate
 - User story completion count
 - Commit reference
-- Issue tracker count
 - Example: "Delivered implementation with 8/8 quality gates passed (100%). All 4 user stories validated. Documented in commit a1b2c3d."
 
 ---
@@ -127,7 +125,6 @@ Human-friendly 3-part narrative placed at the top:
 #### Section 5: Evidence Links
 
 - Implementation commits and messages
-- Issue tracker references (@issue-tracker links)
 - Modified code paths
 - Feature artifact locations
 

extensions/levelup/scripts/bash/generate-trace.sh

@@ -160,13 +160,6 @@ extract_key_decisions() {
         fi
     fi
 
-    # 6. Issue tracking (if used)
-    local issue_refs=$(grep -oh '@issue-tracker' "$FEATURE_SPEC" "$IMPL_PLAN" "$TASKS" 2>/dev/null | wc -l)
-    if [[ $issue_refs -gt 0 ]]; then
-        decisions+=("Integrated issue tracking with $issue_refs @issue-tracker references for traceability")
-        decision_count=$((decision_count + 1))
-    fi
-    
     # Format as numbered list (dynamic count based on what we found)
     local output=""
     for i in "${!decisions[@]}"; do
@@ -221,14 +214,6 @@ extract_final_solution() {
         fi
     fi
 
-    # Add issue tracker count
-    local issue_count=$(grep -oh '@issue-tracker' "$FEATURE_SPEC" "$IMPL_PLAN" "$TASKS" 2>/dev/null | wc -l)
-    if [[ $issue_count -gt 0 ]]; then
-        solution+=" with $issue_count supporting issue tracker references."
-    else
-        solution+="."
-    fi
-    
     echo "$solution"
 }
 
@@ -383,16 +368,6 @@ extract_evidence_links() {
         fi
     fi
 
-    # Extract issue references from spec/plan/tasks
-    local issue_refs=$(grep -oh '@issue-tracker [A-Z0-9\-#]\+' "$FEATURE_SPEC" "$IMPL_PLAN" "$TASKS" 2>/dev/null | sort -u | sed 's/@issue-tracker //' || echo "")
-    if [[ -n "$issue_refs" ]]; then
-        evidence+="**Issue References**:\n"
-        while IFS= read -r issue; do
-            evidence+="- $issue\n"
-        done <<< "$issue_refs"
-        evidence+="\n"
-    fi
-    
     # List modified files from tasks_meta.json
     local file_list=$(jq -r '.tasks[] | .files[]?' "$TASKS_META_FILE" 2>/dev/null | sort -u | head -10)
     if [[ -n "$file_list" ]]; then

extensions/levelup/scripts/powershell/generate-trace.ps1

@@ -83,7 +83,7 @@ function Extract-ProblemStatement {
 
     # Get all user stories from spec
     $specContent = Get-Content $paths.FEATURE_SPEC -Raw
-    $userStoryMatches = [regex]::Matches($specContent, '(?i)(As a user|User story|As an|As a).*?(?=\n|@issue-tracker|$)')
+    $userStoryMatches = [regex]::Matches($specContent, '(?i)(As a user|User story|As an|As a).*?(?=\n|$)')
     $userStories = $userStoryMatches | ForEach-Object { $_.Value.Trim() } | Select-Object -First 5
 
     # Build problem statement
@@ -157,17 +157,6 @@ function Extract-KeyDecisions {
     }
 
     # 6. Issue tracking
-    $issueRefs = 0
-    foreach ($file in @($paths.FEATURE_SPEC, $paths.IMPL_PLAN, $paths.TASKS)) {
-        if (Test-Path $file) {
-            $content = Get-Content $file -Raw
-            $issueRefs += ([regex]::Matches($content, '@issue-tracker')).Count
-        }
-    }
-    if ($issueRefs -gt 0) {
-        $decisions += "Integrated issue tracking with $issueRefs @issue-tracker references for traceability"
-    }
-    
     # Format as numbered list
     $output = ""
     for ($i = 0; $i -lt $decisions.Count; $i++) {
@@ -229,20 +218,6 @@ function Extract-FinalSolution {
         }
     }
 
-    # Add issue tracker count
-    $issueCount = 0
-    foreach ($file in @($paths.FEATURE_SPEC, $paths.IMPL_PLAN, $paths.TASKS)) {
-        if (Test-Path $file) {
-            $content = Get-Content $file -Raw
-            $issueCount += ([regex]::Matches($content, '@issue-tracker')).Count
-        }
-    }
-    if ($issueCount -gt 0) {
-        $solution += " with $issueCount supporting issue tracker references."
-    } else {
-        $solution += "."
-    }
-    
     return $solution
 }
 
@@ -406,27 +381,6 @@ function Extract-EvidenceLinks {
         }
     }
 
-    # Extract issue references
-    $issueRefs = @()
-    foreach ($file in @($paths.FEATURE_SPEC, $paths.IMPL_PLAN, $paths.TASKS)) {
-        if (Test-Path $file) {
-            $content = Get-Content $file -Raw
-            $matches = [regex]::Matches($content, '@issue-tracker ([A-Z0-9\-#]+)')
-            foreach ($match in $matches) {
-                $issueRefs += $match.Groups[1].Value
-            }
-        }
-    }
-    $issueRefs = $issueRefs | Select-Object -Unique
-    
-    if ($issueRefs.Count -gt 0) {
-        $evidence += "**Issue References**:`n"
-        foreach ($issue in $issueRefs) {
-            $evidence += "- $issue`n"
-        }
-        $evidence += "`n"
-    }
-    
     # List modified files
     $fileList = @()
     foreach ($task in $tasksMetaContent.tasks.PSObject.Properties.Value) {

extensions/levelup/templates/trace-template.md

@@ -30,7 +30,6 @@ Chronological list of significant decisions made during implementation. Includes
 1. Chose React with TypeScript for type-safe component development
 2. Implemented TDD approach with 90%+ code coverage requirement
 3. Applied dual execution loop with 5 SYNC (micro-reviewed) and 3 ASYNC (agent-delegated) tasks
-4. Integrated issue tracking with 6 @issue-tracker references for traceability
 
 ### Final Solution
 
@@ -158,12 +157,6 @@ References to implementation artifacts, commits, issues, and code paths for trac
 - Message: {COMMIT_MESSAGE}
 - Date: {COMMIT_DATE}
 
-**Issue References**:
-
-- {ISSUE_1}
-- {ISSUE_2}
-- ... (all @issue-tracker references from artifacts)
-
 **Code Paths Modified**:
 
 - {FILE_1}