claude-autopm 1.18.0 → 1.20.1

package/autopm/.claude/agents/frameworks/tailwindcss-expert.md

@@ -60,8 +60,8 @@ Access Tailwind CSS documentation through context7:
 - Long-term maintainability and scalability are important
 
 **Consider alternatives when:**
-- Need rapid development with pre-built components (→ bootstrap-ui-expert or chakra-ui-expert)
-- Material Design is required (→ mui-react-expert)
+- Need rapid development with pre-built components (→ bootstrap-ui-expert or react-frontend-engineer)
+- Material Design is required (→ react-frontend-engineer)
 - Enterprise data components needed (→ antd-react-expert)
 - Team lacks advanced CSS skills (→ component-based alternatives)
 
@@ -737,5 +737,5 @@ module.exports = {
 ## Integration Points
 
 - Works with: react-frontend-engineer, ux-design-expert, bootstrap-ui-expert
-- Hands off to: playwright-test-engineer for testing
+- Hands off to: frontend-testing-engineer for testing
 - Receives from: design system specifications and UI mockups

package/autopm/.claude/agents/frameworks/ux-design-expert.md

@@ -153,9 +153,9 @@ Access UX design and accessibility documentation:
 
 ### Works With
 - **react-frontend-engineer**: Implementation of designs
-- **mui-react-expert**, **chakra-ui-expert**, **antd-react-expert**: Component styling
-- **tailwindcss-expert**, **bootstrap-ui-expert**: CSS frameworks
-- **playwright-test-engineer**: Usability testing automation
+- **react-ui-expert**: Component styling and design systems
+- **tailwindcss-expert**: Utility-first CSS framework
+- **frontend-testing-engineer**: Usability testing automation
 - **javascript-frontend-engineer**: Interactive features
 
 ### Provides To

package/autopm/.claude/commands/infrastructure/traefik-setup.md

@@ -38,5 +38,5 @@ Parameters: environment=production, ssl=letsencrypt, discovery=docker, features=
 ```
 
 ## Related Agents
-- docker-expert: For container configuration
+- docker-containerization-expert: For container configuration
 - kubernetes-orchestrator: For K8s integration

package/autopm/.claude/commands/playwright/test-scaffold.md

@@ -18,4 +18,4 @@ Creates Playwright test suite with Page Object Model.
 - Adds visual regression setup
 - Creates CI/CD integration scripts
 
-Use the playwright-test-engineer agent to create comprehensive E2E test suite.
+Use the frontend-testing-engineer agent to create comprehensive E2E test suite.

package/autopm/.claude/commands/pm/context.md

@@ -0,0 +1,11 @@
+---
+allowed-tools: Bash
+---
+
+Run `node .claude/scripts/pm/context.js` using the Bash tool and show me the complete output.
+
+- DO NOT truncate.
+- DO NOT collapse.
+- DO NOT abbreviate.
+- Show ALL lines in full.
+- DO NOT print any other comments.

package/autopm/.claude/commands/pm/epic-decompose.md

@@ -50,6 +50,19 @@ Do not bother the user with preflight checks progress ("I'm not going to ...").
    - For each epic, check if status is already "completed"
    - If any epic is completed, warn user: "⚠️ Epic(s) marked as completed. Are you sure you want to decompose again?"
 
+## ⚠️ TDD REMINDER
+
+**CRITICAL: All tasks MUST follow Test-Driven Development (TDD).**
+
+When creating tasks, ensure each task includes:
+- TDD Requirements section (RED-GREEN-REFACTOR cycle)
+- "Tests written FIRST" as first item in Definition of Done
+- References to `.claude/rules/tdd.enforcement.md`
+
+Every generated task file will remind developers to write tests first.
+
+---
+
 ## Instructions
 
 You are decomposing epic(s) into specific, actionable tasks for: **$ARGUMENTS**
@@ -123,6 +136,14 @@ conflicts_with: []  # Tasks that modify same files, e.g., [003, 004]
 ## Description
 Clear, concise description of what needs to be done
 
+## ⚠️ TDD Requirements
+**This project uses Test-Driven Development. You MUST:**
+1. 🔴 RED: Write failing test first
+2. 🟢 GREEN: Write minimal code to make test pass
+3. 🔵 REFACTOR: Clean up code while keeping tests green
+
+See `.claude/rules/tdd.enforcement.md` for complete requirements.
+
 ## Acceptance Criteria
 - [ ] Specific criterion 1
 - [ ] Specific criterion 2
@@ -143,8 +164,10 @@ Clear, concise description of what needs to be done
 - Parallel: true/false (can run in parallel with other tasks)
 
 ## Definition of Done
-- [ ] Code implemented
-- [ ] Tests written and passing
+- [ ] Tests written FIRST (RED phase)
+- [ ] Code implemented (GREEN phase)
+- [ ] Code refactored (REFACTOR phase)
+- [ ] All tests passing
 - [ ] Documentation updated
 - [ ] Code reviewed
 - [ ] Deployed to staging

package/autopm/.claude/commands/pm/epic-oneshot.md

@@ -11,6 +11,19 @@ Decompose epic into tasks and sync to GitHub in one operation.
 /pm:epic-oneshot <feature_name>
 ```
 
+## ⚠️ TDD REMINDER
+
+**CRITICAL: All tasks generated will include TDD requirements.**
+
+This command will create tasks that REQUIRE Test-Driven Development:
+- Each task includes TDD Requirements section
+- Definition of Done starts with "Tests written FIRST"
+- All agents must follow RED-GREEN-REFACTOR cycle
+
+See `.claude/rules/tdd.enforcement.md` for complete requirements.
+
+---
+
 ## Instructions
 
 ### 1. Validate Prerequisites

package/autopm/.claude/commands/pm/epic-start.md

@@ -33,6 +33,25 @@ Launch parallel agents to work on epic tasks using the unified branch strategy.
    ```
    If output is not empty: "❌ You have uncommitted changes. Please commit or stash them before starting an epic"
 
+## ⚠️ TDD REMINDER - READ THIS FIRST
+
+**CRITICAL: This project follows Test-Driven Development (TDD).**
+
+Before ANY coding work begins on this epic, you MUST follow the RED-GREEN-REFACTOR cycle:
+
+1. **RED Phase**: Write failing test that describes the desired behavior
+2. **GREEN Phase**: Write minimum code to make test pass
+3. **REFACTOR Phase**: Clean up code while keeping tests green
+
+**For this epic:**
+- All tasks have TDD requirements section
+- Every agent must start with test creation
+- No implementation without tests first
+
+See `.claude/rules/tdd.enforcement.md` for complete TDD requirements.
+
+---
+
 ## Instructions
 
 ### 1. Create or Enter Branch

package/autopm/.claude/commands/pm/epic-sync-modular.md

@@ -33,7 +33,7 @@ This is handled automatically by our modular scripts, but you can run the check
 
 ```bash
 # Check repository protection (built into all scripts)
-bash autopm/.claude/scripts/lib/github-utils.sh
+bash .claude/scripts/lib/github-utils.sh
 ```
 
 The scripts will automatically:
@@ -47,7 +47,7 @@ Create the main GitHub issue for the epic:
 
 ```bash
 # Create epic issue with proper stats and labels
-epic_number=$(bash autopm/.claude/scripts/pm/epic-sync/create-epic-issue.sh "$ARGUMENTS")
+epic_number=$(bash .claude/scripts/pm/epic-sync/create-epic-issue.sh "$ARGUMENTS")
 
 echo "✅ Epic issue created: #$epic_number"
 ```
@@ -65,7 +65,7 @@ Create GitHub issues for all tasks with automatic parallel processing:
 
 ```bash
 # Create task issues (automatically chooses sequential/parallel)
-task_mapping_file=$(bash autopm/.claude/scripts/pm/epic-sync/create-task-issues.sh "$ARGUMENTS" "$epic_number")
+task_mapping_file=$(bash .claude/scripts/pm/epic-sync/create-task-issues.sh "$ARGUMENTS" "$epic_number")
 
 echo "✅ Task issues created. Mapping: $task_mapping_file"
 ```
@@ -90,7 +90,7 @@ Update all task dependencies and rename files to use GitHub issue numbers:
 
 ```bash
 # Update references and rename files
-bash autopm/.claude/scripts/pm/epic-sync/update-references.sh "$ARGUMENTS" "$task_mapping_file"
+bash .claude/scripts/pm/epic-sync/update-references.sh "$ARGUMENTS" "$task_mapping_file"
 
 echo "✅ Task references updated and files renamed"
 ```
@@ -109,7 +109,7 @@ Update the epic.md file with GitHub information and real task IDs:
 
 ```bash
 # Update epic file with GitHub info and real task IDs
-bash autopm/.claude/scripts/pm/epic-sync/update-epic-file.sh "$ARGUMENTS" "$epic_number"
+bash .claude/scripts/pm/epic-sync/update-epic-file.sh "$ARGUMENTS" "$epic_number"
 
 echo "✅ Epic file updated with GitHub information"
 ```
@@ -151,7 +151,7 @@ echo "🚀 Starting modular epic sync for: $EPIC_NAME"
 
 # Step 1: Create epic issue
 echo "📝 Creating epic issue..."
-epic_number=$(bash autopm/.claude/scripts/pm/epic-sync/create-epic-issue.sh "$EPIC_NAME")
+epic_number=$(bash .claude/scripts/pm/epic-sync/create-epic-issue.sh "$EPIC_NAME")
 
 if [[ -z "$epic_number" ]]; then
     echo "❌ Failed to create epic issue"
@@ -162,7 +162,7 @@ echo "✅ Epic issue created: #$epic_number"
 
 # Step 2: Create task issues
 echo "📋 Creating task issues..."
-task_mapping_file=$(bash autopm/.claude/scripts/pm/epic-sync/create-task-issues.sh "$EPIC_NAME" "$epic_number")
+task_mapping_file=$(bash .claude/scripts/pm/epic-sync/create-task-issues.sh "$EPIC_NAME" "$epic_number")
 
 if [[ ! -f "$task_mapping_file" ]]; then
     echo "❌ Failed to create task issues"
@@ -174,13 +174,13 @@ echo "✅ Created $task_count task issues"
 
 # Step 3: Update references
 echo "🔗 Updating task references..."
-bash autopm/.claude/scripts/pm/epic-sync/update-references.sh "$EPIC_NAME" "$task_mapping_file"
+bash .claude/scripts/pm/epic-sync/update-references.sh "$EPIC_NAME" "$task_mapping_file"
 
 echo "✅ Task references updated"
 
 # Step 4: Update epic file
 echo "📄 Updating epic file..."
-bash autopm/.claude/scripts/pm/epic-sync/update-epic-file.sh "$EPIC_NAME" "$epic_number"
+bash .claude/scripts/pm/epic-sync/update-epic-file.sh "$EPIC_NAME" "$epic_number"
 
 echo "✅ Epic file updated"
 
@@ -303,7 +303,7 @@ Enable debug logging for detailed troubleshooting:
 
 ```bash
 export AUTOPM_LOG_LEVEL=0  # Enable debug logging
-bash autopm/.claude/scripts/pm/epic-sync/create-epic-issue.sh "$EPIC_NAME"
+bash .claude/scripts/pm/epic-sync/create-epic-issue.sh "$EPIC_NAME"
 ```
 
 ## Migration from Legacy Epic Sync

package/autopm/.claude/commands/pm/epic-sync.md

@@ -52,7 +52,7 @@ This is handled automatically by our modular scripts, but you can run the check
 
 ```bash
 # Check repository protection (built into all scripts)
-bash autopm/.claude/scripts/lib/github-utils.sh
+bash .claude/scripts/lib/github-utils.sh
 ```
 
 The scripts will automatically:
@@ -66,7 +66,7 @@ Create the main GitHub issue for the epic:
 
 ```bash
 # Create epic issue with proper stats and labels
-epic_number=$(bash autopm/.claude/scripts/pm/epic-sync/create-epic-issue.sh "$ARGUMENTS")
+epic_number=$(bash .claude/scripts/pm/epic-sync/create-epic-issue.sh "$ARGUMENTS")
 
 echo "✅ Epic issue created: #$epic_number"
 ```
@@ -84,7 +84,7 @@ Create GitHub issues for all tasks with automatic parallel processing:
 
 ```bash
 # Create task issues (automatically chooses sequential/parallel)
-task_mapping_file=$(bash autopm/.claude/scripts/pm/epic-sync/create-task-issues.sh "$ARGUMENTS" "$epic_number")
+task_mapping_file=$(bash .claude/scripts/pm/epic-sync/create-task-issues.sh "$ARGUMENTS" "$epic_number")
 
 echo "✅ Task issues created. Mapping: $task_mapping_file"
 ```
@@ -109,7 +109,7 @@ Update all task dependencies and rename files to use GitHub issue numbers:
 
 ```bash
 # Update references and rename files
-bash autopm/.claude/scripts/pm/epic-sync/update-references.sh "$ARGUMENTS" "$task_mapping_file"
+bash .claude/scripts/pm/epic-sync/update-references.sh "$ARGUMENTS" "$task_mapping_file"
 
 echo "✅ Task references updated and files renamed"
 ```
@@ -128,7 +128,7 @@ Update the epic.md file with GitHub information and real task IDs:
 
 ```bash
 # Update epic file with GitHub info and real task IDs
-bash autopm/.claude/scripts/pm/epic-sync/update-epic-file.sh "$ARGUMENTS" "$epic_number"
+bash .claude/scripts/pm/epic-sync/update-epic-file.sh "$ARGUMENTS" "$epic_number"
 
 echo "✅ Epic file updated with GitHub information"
 ```
@@ -172,7 +172,7 @@ echo "🚀 Starting modular epic sync for: $EPIC_NAME"
 
 # Step 1: Create epic issue
 echo "📝 Creating epic issue..."
-epic_number=$(bash autopm/.claude/scripts/pm/epic-sync/create-epic-issue.sh "$EPIC_NAME")
+epic_number=$(bash .claude/scripts/pm/epic-sync/create-epic-issue.sh "$EPIC_NAME")
 
 if [[ -z "$epic_number" ]]; then
     echo "❌ Failed to create epic issue"
@@ -183,7 +183,7 @@ echo "✅ Epic issue created: #$epic_number"
 
 # Step 2: Create task issues
 echo "📋 Creating task issues..."
-task_mapping_file=$(bash autopm/.claude/scripts/pm/epic-sync/create-task-issues.sh "$EPIC_NAME" "$epic_number")
+task_mapping_file=$(bash .claude/scripts/pm/epic-sync/create-task-issues.sh "$EPIC_NAME" "$epic_number")
 
 if [[ ! -f "$task_mapping_file" ]]; then
     echo "❌ Failed to create task issues"
@@ -195,13 +195,13 @@ echo "✅ Created $task_count task issues"
 
 # Step 3: Update references
 echo "🔗 Updating task references..."
-bash autopm/.claude/scripts/pm/epic-sync/update-references.sh "$EPIC_NAME" "$task_mapping_file"
+bash .claude/scripts/pm/epic-sync/update-references.sh "$EPIC_NAME" "$task_mapping_file"
 
 echo "✅ Task references updated"
 
 # Step 4: Update epic file
 echo "📄 Updating epic file..."
-bash autopm/.claude/scripts/pm/epic-sync/update-epic-file.sh "$EPIC_NAME" "$epic_number"
+bash .claude/scripts/pm/epic-sync/update-epic-file.sh "$EPIC_NAME" "$epic_number"
 
 echo "✅ Epic file updated"
 
@@ -269,7 +269,7 @@ for epic_dir in $epic_dirs; do
 
     # Step 1: Create epic issue
     echo "📝 Creating epic issue..."
-    epic_number=$(bash autopm/.claude/scripts/pm/epic-sync/create-epic-issue.sh "$FEATURE_NAME/$epic_name")
+    epic_number=$(bash .claude/scripts/pm/epic-sync/create-epic-issue.sh "$FEATURE_NAME/$epic_name")
 
     if [[ -z "$epic_number" ]]; then
         echo "⚠️  Failed to create epic issue for $epic_name"
@@ -281,7 +281,7 @@ for epic_dir in $epic_dirs; do
 
     # Step 2: Create task issues for this epic
     echo "📋 Creating task issues..."
-    task_mapping_file=$(bash autopm/.claude/scripts/pm/epic-sync/create-task-issues.sh "$FEATURE_NAME/$epic_name" "$epic_number")
+    task_mapping_file=$(bash .claude/scripts/pm/epic-sync/create-task-issues.sh "$FEATURE_NAME/$epic_name" "$epic_number")
 
     if [[ -f "$task_mapping_file" ]]; then
         task_count=$(wc -l < "$task_mapping_file")
@@ -290,10 +290,10 @@ for epic_dir in $epic_dirs; do
 
         # Step 3: Update references
         echo "🔗 Updating task references..."
-        bash autopm/.claude/scripts/pm/epic-sync/update-references.sh "$FEATURE_NAME/$epic_name" "$task_mapping_file"
+        bash .claude/scripts/pm/epic-sync/update-references.sh "$FEATURE_NAME/$epic_name" "$task_mapping_file"
 
         # Step 4: Update epic file
-        bash autopm/.claude/scripts/pm/epic-sync/update-epic-file.sh "$FEATURE_NAME/$epic_name" "$epic_number"
+        bash .claude/scripts/pm/epic-sync/update-epic-file.sh "$FEATURE_NAME/$epic_name" "$epic_number"
     fi
 done
 
@@ -418,7 +418,7 @@ Enable debug logging for detailed troubleshooting:
 
 ```bash
 export AUTOPM_LOG_LEVEL=0  # Enable debug logging
-bash autopm/.claude/scripts/pm/epic-sync/create-epic-issue.sh "$EPIC_NAME"
+bash .claude/scripts/pm/epic-sync/create-epic-issue.sh "$EPIC_NAME"
 ```
 
 ## Migration from Legacy Epic Sync

package/autopm/.claude/commands/pm/issue-start.md

@@ -33,6 +33,26 @@ Begin work on a GitHub issue with parallel agents based on work stream analysis.
    ` ``
    If no analysis exists and no --analyze flag, stop execution.
 
+## ⚠️ TDD REMINDER - READ THIS FIRST
+
+**CRITICAL: This project follows Test-Driven Development (TDD).**
+
+Before ANY coding work begins, you MUST follow the RED-GREEN-REFACTOR cycle:
+
+1. **RED Phase**: Write failing test that describes the desired behavior
+2. **GREEN Phase**: Write minimum code to make test pass
+3. **REFACTOR Phase**: Clean up code while keeping tests green
+
+**For this issue:**
+- Read the task requirements from the task file
+- Identify what tests are needed BEFORE any implementation
+- All agents must start with test creation
+- No implementation without tests first
+
+See `.claude/rules/tdd.enforcement.md` for complete TDD requirements.
+
+---
+
 ## Instructions
 
 ### 1. Ensure Branch Exists
@@ -103,12 +123,30 @@ Task:
   description: "Issue #$ARGUMENTS Stream {X}"
   subagent_type: "{agent_type}"
   prompt: |
-    **CRITICAL RULE: This project uses 'Docker-first development'.**
+    **🚨 CRITICAL RULE #1: Test-Driven Development (TDD) is MANDATORY**
+
+    You MUST follow the RED-GREEN-REFACTOR cycle:
+    1. **RED**: Write a FAILING test first that describes the desired behavior
+    2. **GREEN**: Write MINIMUM code to make the test pass
+    3. **REFACTOR**: Clean up code while keeping all tests green
+
+    **NO CODE WITHOUT TESTS FIRST.** Zero exceptions.
+    - Every function starts with a test
+    - Every bug fix starts with a test that reproduces it
+    - Every feature starts with failing acceptance tests
+
+    See `.claude/rules/tdd.enforcement.md` for complete requirements.
+
+    ---
+
+    **CRITICAL RULE #2: This project uses 'Docker-first development'.**
     - All commands (dependency installation, tests, running the application) MUST be executed inside a Docker container using `docker compose run --rm <service_name> <command>`.
     - DO NOT run `npm`, `pip`, `pytest`, etc., directly on the host.
     - The source code is mounted as a VOLUME, so file changes will be immediately visible in the container (hot-reloading).
     - Full rules can be found in `.claude/rules/docker-first-development.md`.
 
+    ---
+
     You are working on Issue #$ARGUMENTS in the epic branch.
 
     Branch: epic/{epic_name}
@@ -120,10 +158,12 @@ Task:
     
     Requirements:
     1. Read full task from: .claude/epics/{epic_name}/{task_file}
-    2. Work ONLY in your assigned files
-    3. Commit frequently with format: "Issue #$ARGUMENTS: {specific change}"
-    4. Update progress in: .claude/epics/{epic_name}/updates/$ARGUMENTS/stream-{X}.md
-    5. Follow coordination rules in /rules/agent-coordination.md
+    2. **START WITH TESTS**: Write failing tests BEFORE any implementation
+    3. Work ONLY in your assigned files
+    4. Follow TDD cycle: RED (test fails) → GREEN (minimal code) → REFACTOR (cleanup)
+    5. Commit frequently with format: "Issue #$ARGUMENTS: {specific change}"
+    6. Update progress in: .claude/epics/{epic_name}/updates/$ARGUMENTS/stream-{X}.md
+    7. Follow coordination rules in /rules/agent-coordination.md
     
     If you need to modify files outside your scope:
     - Check if another stream owns them
@@ -156,6 +196,11 @@ Launching {count} parallel agents:
 Progress tracking:
   .claude/epics/{epic_name}/updates/$ARGUMENTS/
 
+⚠️  TDD CHECKLIST - All agents MUST follow:
+  1. ❌ RED: Write failing test
+  2. ❌ GREEN: Make test pass (minimal code)
+  3. ❌ REFACTOR: Clean up code
+
 Monitor with: /pm:epic-status {epic_name}
 Sync updates: /pm:issue-sync $ARGUMENTS
 ` ``

package/autopm/.claude/commands/pm/issue-sync.md

@@ -33,7 +33,7 @@ Run comprehensive validation checks before syncing:
 
 ```bash
 # Run preflight validation
-bash autopm/.claude/scripts/pm/issue-sync/preflight-validation.sh "$ARGUMENTS"
+bash .claude/scripts/pm/issue-sync/preflight-validation.sh "$ARGUMENTS"
 
 if [[ $? -ne 0 ]]; then
     echo "❌ Preflight validation failed"
@@ -41,9 +41,9 @@ if [[ $? -ne 0 ]]; then
 fi
 
 # Extract validated paths from preflight output
-epic_name=$(bash autopm/.claude/scripts/pm/issue-sync/preflight-validation.sh "$ARGUMENTS" | grep "Epic:" | cut -d: -f2- | xargs)
-updates_dir=$(bash autopm/.claude/scripts/pm/issue-sync/preflight-validation.sh "$ARGUMENTS" | grep "Updates Directory:" | cut -d: -f2- | xargs)
-progress_file=$(bash autopm/.claude/scripts/pm/issue-sync/preflight-validation.sh "$ARGUMENTS" | grep "Progress File:" | cut -d: -f2- | xargs)
+epic_name=$(bash .claude/scripts/pm/issue-sync/preflight-validation.sh "$ARGUMENTS" | grep "Epic:" | cut -d: -f2- | xargs)
+updates_dir=$(bash .claude/scripts/pm/issue-sync/preflight-validation.sh "$ARGUMENTS" | grep "Updates Directory:" | cut -d: -f2- | xargs)
+progress_file=$(bash .claude/scripts/pm/issue-sync/preflight-validation.sh "$ARGUMENTS" | grep "Progress File:" | cut -d: -f2- | xargs)
 
 echo "✅ Preflight checks passed"
 ```
@@ -65,7 +65,7 @@ Collect all local development updates:
 last_sync=$(grep '^last_sync:' "$progress_file" | sed 's/^last_sync: *//')
 
 # Gather all updates since last sync
-consolidated_updates=$(bash autopm/.claude/scripts/pm/issue-sync/gather-updates.sh \
+consolidated_updates=$(bash .claude/scripts/pm/issue-sync/gather-updates.sh \
     "$ARGUMENTS" \
     "$updates_dir" \
     "$last_sync")
@@ -95,7 +95,7 @@ if [[ "$completion" == "100" ]]; then
 fi
 
 # Format the comment
-formatted_comment=$(bash autopm/.claude/scripts/pm/issue-sync/format-comment.sh \
+formatted_comment=$(bash .claude/scripts/pm/issue-sync/format-comment.sh \
     "$ARGUMENTS" \
     "$consolidated_updates" \
     "$progress_file" \
@@ -119,7 +119,7 @@ Post the formatted comment to GitHub:
 
 ```bash
 # Post comment to GitHub issue
-comment_url=$(bash autopm/.claude/scripts/pm/issue-sync/post-comment.sh \
+comment_url=$(bash .claude/scripts/pm/issue-sync/post-comment.sh \
     "$ARGUMENTS" \
     "$formatted_comment" \
     "$is_completion")
@@ -146,7 +146,7 @@ Update local metadata after successful sync:
 
 ```bash
 # Update progress.md frontmatter with sync information
-bash autopm/.claude/scripts/pm/issue-sync/update-frontmatter.sh \
+bash .claude/scripts/pm/issue-sync/update-frontmatter.sh \
     "$ARGUMENTS" \
     "$progress_file" \
     "$comment_url" \
@@ -178,13 +178,13 @@ echo "🚀 Starting modular issue sync for: #$ISSUE_NUMBER"
 
 # Step 1: Preflight validation
 echo "🔍 Running preflight validation..."
-if ! bash autopm/.claude/scripts/pm/issue-sync/preflight-validation.sh "$ISSUE_NUMBER"; then
+if ! bash .claude/scripts/pm/issue-sync/preflight-validation.sh "$ISSUE_NUMBER"; then
     echo "❌ Preflight validation failed"
     exit 1
 fi
 
 # Extract paths from a single preflight run
-preflight_output=$(bash autopm/.claude/scripts/pm/issue-sync/preflight-validation.sh "$ISSUE_NUMBER")
+preflight_output=$(bash .claude/scripts/pm/issue-sync/preflight-validation.sh "$ISSUE_NUMBER")
 epic_name=$(echo "$preflight_output" | grep "Epic:" | cut -d: -f2- | xargs)
 updates_dir=$(echo "$preflight_output" | grep "Updates Directory:" | cut -d: -f2- | xargs)
 progress_file=$(echo "$preflight_output" | grep "Progress File:" | cut -d: -f2- | xargs)
@@ -196,7 +196,7 @@ echo "  Updates: $updates_dir"
 # Step 2: Gather updates
 echo "📝 Gathering local updates..."
 last_sync=$(grep '^last_sync:' "$progress_file" 2>/dev/null | sed 's/^last_sync: *//' || echo "")
-consolidated_updates=$(bash autopm/.claude/scripts/pm/issue-sync/gather-updates.sh \
+consolidated_updates=$(bash .claude/scripts/pm/issue-sync/gather-updates.sh \
     "$ISSUE_NUMBER" \
     "$updates_dir" \
     "$last_sync")
@@ -217,7 +217,7 @@ if [[ "$completion" == "100" ]]; then
     echo "  Task is complete - formatting completion comment"
 fi
 
-formatted_comment=$(bash autopm/.claude/scripts/pm/issue-sync/format-comment.sh \
+formatted_comment=$(bash .claude/scripts/pm/issue-sync/format-comment.sh \
     "$ISSUE_NUMBER" \
     "$consolidated_updates" \
     "$progress_file" \
@@ -232,7 +232,7 @@ echo "✅ Comment formatted"
 
 # Step 4: Post to GitHub
 echo "☁️ Posting to GitHub..."
-comment_url=$(bash autopm/.claude/scripts/pm/issue-sync/post-comment.sh \
+comment_url=$(bash .claude/scripts/pm/issue-sync/post-comment.sh \
     "$ISSUE_NUMBER" \
     "$formatted_comment" \
     "$is_completion")
@@ -247,7 +247,7 @@ echo "✅ Comment posted successfully"
 
 # Step 5: Update frontmatter
 echo "📝 Updating local metadata..."
-bash autopm/.claude/scripts/pm/issue-sync/update-frontmatter.sh \
+bash .claude/scripts/pm/issue-sync/update-frontmatter.sh \
     "$ISSUE_NUMBER" \
     "$progress_file" \
     "$comment_url" \
@@ -376,7 +376,7 @@ Enable debug logging for detailed troubleshooting:
 
 ```bash
 export AUTOPM_LOG_LEVEL=0  # Enable debug logging
-bash autopm/.claude/scripts/pm/issue-sync/preflight-validation.sh "$ISSUE_NUMBER"
+bash .claude/scripts/pm/issue-sync/preflight-validation.sh "$ISSUE_NUMBER"
 ```
 
 ## Migration from Legacy Issue Sync

package/autopm/.claude/commands/pm/what-next.md

@@ -0,0 +1,11 @@
+---
+allowed-tools: Bash
+---
+
+Run `node .claude/scripts/pm/what-next.js` using the Bash tool and show me the complete output.
+
+- DO NOT truncate.
+- DO NOT collapse.
+- DO NOT abbreviate.
+- Show ALL lines in full.
+- DO NOT print any other comments.

package/autopm/.claude/commands/ui/bootstrap-scaffold.md

@@ -8,7 +8,7 @@ Create a complete Bootstrap-based UI structure with responsive components and th
 ```
 
 ## Purpose
-Use the bootstrap-ui-expert agent to create a complete Bootstrap application scaffold with modern components, responsive design, and customizable themes.
+Use the react-ui-expert agent (with framework=bootstrap) to create a complete Bootstrap application scaffold with modern components, responsive design, and customizable themes.
 
 ## Parameters
 - `theme`: Theme variant (light, dark, corporate, minimal)
@@ -18,7 +18,7 @@ Use the bootstrap-ui-expert agent to create a complete Bootstrap application sca
 
 ## Agent Usage
 ```
-Use the bootstrap-ui-expert agent to create a complete Bootstrap application scaffold.
+Use the react-ui-expert agent with framework=bootstrap to create a complete Bootstrap application scaffold.
 ```
 
 ## Expected Outcome
@@ -32,10 +32,11 @@ Use the bootstrap-ui-expert agent to create a complete Bootstrap application sca
 ## Example Usage
 ```
 Task: Create Bootstrap dashboard with sidebar navigation, responsive cards grid, and contact forms
-Agent: bootstrap-ui-expert
-Parameters: theme=corporate, components=navbar,sidebar,cards,forms,modals, responsive=all, features=dark-mode,validation
+Agent: react-ui-expert
+Parameters: framework=bootstrap, theme=corporate, components=navbar,sidebar,cards,forms,modals, responsive=all, features=dark-mode,validation
 ```
 
 ## Related Agents
 - tailwindcss-expert: For utility-first alternative
-- react-frontend-engineer: For React + Bootstrap integration
+- react-frontend-engineer: For React + Bootstrap integration
+- react-ui-expert: Main agent for UI component architecture

package/autopm/.claude/commands/ui/tailwind-system.md

@@ -37,5 +37,5 @@ Parameters: theme=modern, utilities=custom-spacing,gradients,animations, compone
 ```
 
 ## Related Agents
-- bootstrap-ui-expert: For component-based alternative
+- react-ui-expert: For component-based alternative
 - react-frontend-engineer: For React + Tailwind integration

package/autopm/.claude/examples/mcp/playwright-mcp.md

@@ -74,7 +74,7 @@ autopm mcp sync
 ### Integration with Agents
 
 Used extensively with:
-- `e2e-test-engineer` - For E2E test creation
+- `frontend-testing-engineer` - For E2E test creation
 - `react-frontend-engineer` - For UI testing
 - `ux-design-expert` - For visual regression
 
@@ -309,4 +309,4 @@ npx playwright show-trace trace.zip
 
 - [Playwright Documentation](https://playwright.dev)
 - [MCP Browser Control](https://modelcontextprotocol.org/browser)
-- [E2E Test Engineer Agent](../agents/frameworks/e2e-test-engineer.md)
+- [E2E Test Engineer Agent](../agents/frameworks/frontend-testing-engineer.md)

package/autopm/.claude/examples/mcp-servers.example.json

@@ -37,7 +37,7 @@
     },
     "react-docs": {
       "type": "shared",
-      "agents": ["react-frontend-engineer", "playwright-test-engineer"],
+      "agents": ["react-frontend-engineer", "frontend-testing-engineer"],
       "sources": ["context7"],
       "filters": ["react", "nextjs", "typescript", "tailwind", "vite"],
       "maxSize": "75MB",
@@ -64,7 +64,7 @@
     },
     "testing-context": {
       "type": "shared",
-      "agents": ["playwright-test-engineer", "test-runner"],
+      "agents": ["frontend-testing-engineer", "test-runner"],
       "sources": ["context7", "playwright-mcp"],
       "filters": ["playwright", "testing", "e2e"],
       "maxSize": "50MB",