fix: remove required variables from ADR template

.beads/issues.jsonl

@@ -1 +1,8 @@
-{"id":"agentspaces-yjh","title":"Simplify workspace navigation and venv activation after creation","description":"## Context\nAfter running 'agentspaces workspace create', users see a 'Next Steps' section with commands to cd and activate venv. This requires copying/pasting long paths.\n\n## Goal\nProvide a simpler way for users to navigate to workspace and activate venv without manual copying/pasting.\n\n## Current Behavior\nUsers must copy/paste:\n1. cd /Users/ckrough/.agentspaces/agentspaces/sleepy-fermat\n2. source .venv/bin/activate\n\n## Desired Behavior\nSingle command or automated navigation that minimizes user effort.\n\n## Files Involved\n- src/agentspaces/cli/workspace.py - workspace create command\n- src/agentspaces/modules/workspace/service.py - workspace creation logic\n\n## Verification\n1. Create a new workspace\n2. Verify simplified navigation/activation works\n3. uv run pytest tests/ -k workspace","status":"closed","priority":2,"issue_type":"feature","created_at":"2026-01-09T14:52:35.442563-05:00","updated_at":"2026-01-09T15:21:26.303403-05:00","closed_at":"2026-01-09T15:21:26.303403-05:00","close_reason":"Implemented: Combined cd and venv activation into single command, removed workspace remove step, added path quoting for safety","created_by":"ckrough"}
+{"id":"agentspaces-4e2","title":"Research Ghost TTY socket API integration possibilities","description":"## Context\nGhost TTY is a terminal multiplexer with a socket API that could be integrated with agentspaces workspace management.\n\n## Goal\nResearch and document capabilities of Ghost TTY socket API that could enhance agentspaces workflow.\n\n## Research Areas\n1. Tab/pane management - creating, switching, closing\n2. Command execution in specific tabs\n3. Environment variable and directory control\n4. Session state queries\n5. Event notifications/hooks\n6. Integration patterns with CLI tools\n\n## Deliverables\nCreate documentation (ADR or design doc) covering:\n- Available API endpoints/commands\n- Use cases for agentspaces integration\n- Example implementations\n- Limitations or constraints\n- Recommended integration approach\n\n## Verification\nDocument created in docs/design/ or docs/adr/ with research findings","status":"closed","priority":3,"issue_type":"task","created_at":"2026-01-10T08:31:27.858077-05:00","created_by":"ckrough","updated_at":"2026-01-10T08:47:03.677322-05:00","closed_at":"2026-01-10T08:47:03.677322-05:00","close_reason":"Research completed. Findings documented in docs/design/ghostty-integration-research.md. Key finding: Ghostty does not have a stable socket API as of Jan 2026. Recommendation: maintain current CLI-based integration and monitor Ghostty development for future opportunities."}
+{"id":"agentspaces-520","title":"Review CLAUDE.md template YAML frontmatter necessity","description":"## Context\nThe project skeleton includes a CLAUDE.md template in src/agentspaces/templates/skeleton/CLAUDE.md. Some templates use YAML frontmatter, others don't.\n\n## Goal\nDetermine if CLAUDE.md template should have YAML frontmatter or if it should be plain markdown.\n\n## Considerations\n1. Does Claude Code use frontmatter in CLAUDE.md files?\n2. Do other templates use frontmatter consistently?\n3. Does frontmatter add value (metadata, template variables)?\n4. Would removing it simplify template processing?\n\n## Tasks\n1. Review src/agentspaces/templates/skeleton/CLAUDE.md\n2. Check if frontmatter is used/needed by Claude Code\n3. Review other template files for consistency\n4. Review src/agentspaces/infrastructure/frontmatter.py usage\n5. Make decision: keep, remove, or standardize\n\n## Deliverables\n- Update CLAUDE.md template if needed\n- Document decision in commit message\n- Update template processing if frontmatter handling changes\n\n## Verification\n1. Generate new project: agentspaces project create\n2. Verify CLAUDE.md renders correctly\n3. Test template processing: uv run pytest tests/ -k template","status":"open","priority":3,"issue_type":"chore","created_at":"2026-01-10T08:31:28.654398-05:00","created_by":"ckrough","updated_at":"2026-01-10T08:31:28.654398-05:00"}
+{"id":"agentspaces-6de","title":"Add terminal-based UI for workspace management","description":"## Context\nThe agentspaces CLI currently only provides command-line subcommands for workspace operations. Users need to run separate commands to list, navigate to, and remove workspaces.\n\n## Goal\nCreate an interactive terminal UI that allows users to:\n1. Browse workspaces in a scrollable list\n2. Select a workspace to CD into it, activate its venv, and start claude\n3. Remove a single workspace\n4. Select multiple workspaces for bulk removal\n\n## Implementation\nWill use a TUI library (likely textual or prompt_toolkit) to create an interactive interface.\n\n## Verification\nManual testing of the TUI with multiple workspaces","status":"closed","priority":2,"issue_type":"feature","created_at":"2026-01-09T16:59:55.628787-05:00","created_by":"ckrough","updated_at":"2026-01-09T17:32:53.462255-05:00","closed_at":"2026-01-09T17:32:53.462255-05:00","close_reason":"Implemented interactive TUI with workspace browsing, navigation (Ghostty tab + fallback), and single/bulk removal. Includes main checkout protection, confirmation dialogs, and preview panel. All critical code review issues addressed."}
+{"id":"agentspaces-782","title":"TUI: Add Ghost TTY tab creation on workspace Enter","description":"## Context\nThe terminal-based user interface (TUI) in src/agentspaces/cli/workspace.py allows browsing workspaces. Ghost TTY is a terminal multiplexer with socket API support.\n\n## Goal\nEnhance TUI workspace selection to launch Claude Code in a new Ghost TTY tab when user presses Enter on a workspace.\n\n## Implementation\n1. Detect Enter key press on selected workspace in TUI\n2. Integrate with Ghost TTY socket API to create new tab\n3. Navigate to workspace directory (~/.agentspaces/\u003cproject\u003e/\u003cname\u003e/)\n4. Activate virtual environment (.venv/bin/activate)\n5. Execute 'Claude' command to start Claude Code\n\n## Dependencies\n- Existing TUI implementation\n- Ghost TTY socket API integration (see beads-xxx for API research)\n\n## Verification\n1. Run 'agentspaces workspace list' with TUI\n2. Select workspace and press Enter\n3. Verify new Ghost TTY tab opens in workspace directory with venv active\n4. Verify Claude Code starts","status":"in_progress","priority":2,"issue_type":"feature","created_at":"2026-01-10T08:31:27.324933-05:00","created_by":"ckrough","updated_at":"2026-01-10T08:45:35.009808-05:00"}
+{"id":"agentspaces-7hb","title":"TUI: Add multi-workspace deletion with single confirmation","description":"## Context\nThe TUI workspace manager in src/agentspaces/cli/workspace.py currently allows removing workspaces one at a time. PR #34 added the interactive TUI for workspace removal.\n\n## Goal\nEnable users to select multiple workspaces for deletion with a single confirmation prompt.\n\n## Implementation\n1. Add multi-select mode to TUI (e.g., spacebar to toggle selection)\n2. Track selected workspaces in UI state\n3. Show count of selected workspaces\n4. Present single confirmation dialog for batch deletion\n5. Call workspace removal service for each selected workspace\n\n## Dependencies\n- Existing TUI implementation in src/agentspaces/cli/workspace.py\n- WorkspaceService.remove_workspace() in src/agentspaces/modules/workspace/service.py\n\n## Verification\n1. Run 'agentspaces workspace list' with TUI\n2. Select multiple workspaces using selection mechanism\n3. Trigger delete action\n4. Verify single confirmation prompt\n5. Verify all selected workspaces are removed\n6. Run tests: uv run pytest tests/ -k workspace","status":"closed","priority":2,"issue_type":"feature","created_at":"2026-01-10T08:31:27.593593-05:00","created_by":"ckrough","updated_at":"2026-01-10T08:43:24.143323-05:00","closed_at":"2026-01-10T08:43:24.143323-05:00","close_reason":"Feature already implemented in PR #32 (b2134b9). The TUI multi-workspace deletion with single confirmation is working as specified: Space key toggles selection, 'd' key triggers removal, and a single ConfirmRemoveModal shows all selected workspaces. All implementation requirements from task description are complete."}
+{"id":"agentspaces-qfu","title":"Fix ADR template missing variables error","description":"## Context\nWhen running 'agentspaces project create', template rendering fails with error:\n'✗ adr-template: Missing required variables for 'adr-template': adr_number, adr_title'\n\nThe ADR template is located in src/agentspaces/templates/skeleton/docs/adr/ and is processed during project initialization.\n\n## Problem\nThe ADR template file expects variables (adr_number, adr_title) but project creation doesn't provide them. This breaks the project initialization workflow.\n\n## Root Cause Investigation\n1. Check src/agentspaces/infrastructure/design.py template rendering\n2. Review src/agentspaces/cli/project.py initialization flow\n3. Examine ADR template frontmatter requirements\n4. Determine if ADR template should be copied as-is or skipped during init\n\n## Possible Solutions\n1. Skip ADR template during project init (only copy when creating actual ADRs)\n2. Provide default/placeholder values for variables\n3. Remove variable requirements from template\n4. Make template variables optional with defaults\n\n## Verification\n1. Run 'agentspaces project create' in test directory\n2. Verify no template errors\n3. Verify docs/adr/ structure is created correctly\n4. Run existing tests: uv run pytest tests/ -k project","status":"closed","priority":1,"issue_type":"bug","created_at":"2026-01-10T08:31:28.388479-05:00","created_by":"ckrough","updated_at":"2026-01-10T08:48:51.936294-05:00","closed_at":"2026-01-10T08:48:51.936294-05:00","close_reason":"Fixed by removing required variables from ADR template and using plain text placeholders instead. Project creation now works without errors."}
+{"id":"agentspaces-x6a","title":"Design: AI-native workspace integration (Claude Code + Teleport)","description":"## Context\nClaude Code supports web-based AI interactions and task teleportation between terminal and web (https://code.claude.com/docs/en/claude-code-on-the-web#moving-tasks-between-web-and-terminal). Agentspaces manages git worktree workspaces for AI coding agents.\n\n## Goal\nDesign three elegant implementation approaches for deep integration of Claude Code AI features and teleport capability into agentspaces workflow.\n\n## Research Questions\n1. How can workspace creation/switching trigger Claude Code sessions?\n2. How can teleport functionality move work between workspaces?\n3. How can workspace metadata track AI session state?\n4. How can agentspaces CLI expose workspace context to Claude Code?\n5. What hooks or APIs enable bidirectional communication?\n\n## Deliverables\nDesign document in docs/design/ with:\n- Three distinct implementation approaches\n- Pros/cons and complexity analysis for each\n- Recommended approach with rationale\n- Integration architecture diagrams\n- Example user workflows\n\n## References\n- https://code.claude.com/docs/en/claude-code-on-the-web#moving-tasks-between-web-and-terminal\n\n## Verification\nDesign document created and reviewed","status":"open","priority":2,"issue_type":"task","created_at":"2026-01-10T08:31:28.122256-05:00","created_by":"ckrough","updated_at":"2026-01-10T08:31:28.122256-05:00"}
+{"id":"agentspaces-yjh","title":"Simplify workspace navigation and venv activation after creation","description":"## Context\nAfter running 'agentspaces workspace create', users see a 'Next Steps' section with commands to cd and activate venv. This requires copying/pasting long paths.\n\n## Goal\nProvide a simpler way for users to navigate to workspace and activate venv without manual copying/pasting.\n\n## Current Behavior\nUsers must copy/paste:\n1. cd /Users/ckrough/.agentspaces/agentspaces/sleepy-fermat\n2. source .venv/bin/activate\n\n## Desired Behavior\nSingle command or automated navigation that minimizes user effort.\n\n## Files Involved\n- src/agentspaces/cli/workspace.py - workspace create command\n- src/agentspaces/modules/workspace/service.py - workspace creation logic\n\n## Verification\n1. Create a new workspace\n2. Verify simplified navigation/activation works\n3. uv run pytest tests/ -k workspace","status":"closed","priority":2,"issue_type":"feature","created_at":"2026-01-09T14:52:35.442563-05:00","created_by":"ckrough","updated_at":"2026-01-09T15:21:26.303403-05:00","closed_at":"2026-01-09T15:21:26.303403-05:00","close_reason":"Implemented: Combined cd and venv activation into single command, removed workspace remove step, added path quoting for safety"}

src/agentspaces/templates/skeleton/docs/adr/000-template.md

@@ -6,18 +6,14 @@ when_to_use:
   - Recording significant technical decisions
   - Decisions future developers will ask "why?"
 variables:
-  required:
-    - adr_number
-    - adr_title
-  optional:
-    - adr_date
-    - adr_status
+  required: []
+  optional: []
 ---
 
-# {{ adr_number }}. {{ adr_title }}
+# ADR-XXX: Decision Title
 
-Date: {{ adr_date | default("YYYY-MM-DD") }}
-Status: {{ adr_status | default("Proposed") }}
+Date: YYYY-MM-DD
+Status: Proposed
 
 ## Context