claude-cli-advanced-starter-pack 1.8.3 → 1.8.4

package/templates/commands/create-task-list-for-issue.template.md

@@ -0,0 +1,216 @@
+---
+description: Start working on a GitHub issue by number with full workflow
+type: utility
+complexity: simple
+model: haiku
+argument-hint: <issue-number>
+allowed-tools:
+  - Bash
+  - AskUserQuestion
+  - Task
+---
+
+# /create-task-list-for-issue - Quick Issue Start
+
+**Start working on a GitHub issue by number. Confirms details, then runs full `/create-task-list` workflow.**
+
+---
+
+## USAGE
+
+```bash
+/create-task-list-for-issue 123
+/create-task-list-for-issue #45
+/create-task-list-for-issue 7
+```
+
+---
+
+## EXECUTION
+
+### Step 1: Parse Issue Number
+
+Extract issue number from `$ARGUMENTS`:
+- Strip `#` prefix if present
+- Validate it's a positive integer
+
+```
+If no issue number provided:
+  → Use AskUserQuestion: "Which issue number would you like to work on?"
+```
+
+---
+
+### Step 2: Fetch Issue Details
+
+```bash
+gh issue view [NUMBER] --json number,title,body,createdAt,labels,url
+```
+
+---
+
+### Step 3: Detect Issue Format
+
+Check if the issue body contains BOTH of these indicators of `/github-task` format:
+- `## Acceptance Criteria` OR `## Task Checklist` section
+- `## Suggested Implementation` OR `## Implementation Approach` section
+
+**Set `IS_TASK_READY`** = true if both indicators found, false otherwise.
+
+---
+
+### Step 4: Display Issue Confirmation
+
+**If IS_TASK_READY = true:**
+
+```
+╔═══════════════════════════════════════════════════════════════╗
+║  Issue #[NUMBER]  ✓ Task-Ready                                ║
+╠═══════════════════════════════════════════════════════════════╣
+║                                                               ║
+║  [Issue Title - max 50 chars]                                 ║
+║                                                               ║
+║  Created: [MM/DD/YYYY]                                        ║
+║  Labels: [label1, label2, ...]                                ║
+║  URL: [github url]                                            ║
+║                                                               ║
+║  Format: Has task checklist - will use existing tasks         ║
+║                                                               ║
+║  Tasks found:                                                 ║
+║    • [Task 1 from checklist]                                  ║
+║    • [Task 2 from checklist]                                  ║
+║    • ... ([N] total)                                          ║
+║                                                               ║
+╚═══════════════════════════════════════════════════════════════╝
+```
+
+**If IS_TASK_READY = false:**
+
+```
+╔═══════════════════════════════════════════════════════════════╗
+║  Issue #[NUMBER]  ⚠ Needs Analysis                            ║
+╠═══════════════════════════════════════════════════════════════╣
+║                                                               ║
+║  [Issue Title - max 50 chars]                                 ║
+║                                                               ║
+║  Created: [MM/DD/YYYY]                                        ║
+║  Labels: [label1, label2, ...]                                ║
+║  URL: [github url]                                            ║
+║                                                               ║
+║  Format: No task checklist - will generate via exploration    ║
+║                                                               ║
+║  Description preview:                                         ║
+║    [First 100 chars of issue body...]                         ║
+║                                                               ║
+╚═══════════════════════════════════════════════════════════════╝
+```
+
+---
+
+### Step 5: Confirm and Proceed
+
+```
+header: "Start"
+question: "Start working on this issue?"
+options:
+  - label: "Y - Yes, proceed"
+    description: "Run full /create-task-list workflow"
+  - label: "V - View full details"
+    description: "Show complete issue body first"
+  - label: "N - Cancel"
+    description: "Return without starting"
+```
+
+**If user selects V (View):**
+- Run `gh issue view [NUMBER]` and display full body
+- Then re-ask the confirmation question (Y/N only)
+
+**If user selects N (Cancel):**
+- Exit command
+
+**If user selects Y (Yes):**
+- Proceed to Step 6
+
+---
+
+### Step 6: Run Full /create-task-list Workflow
+
+**If IS_TASK_READY = true:**
+
+Display:
+```
+╔═══════════════════════════════════════════════════════════════╗
+║  📋 Starting Issue #[NUMBER] (Task-Ready)                     ║
+╠═══════════════════════════════════════════════════════════════╣
+║  Using existing task checklist from issue                     ║
+║  Running full /create-task-list workflow for:                 ║
+║    • Codebase exploration & context                           ║
+║    • Testing configuration (Ralph loop, E2E)                  ║
+║    • Workflow setup (branch, board sync)                      ║
+╚═══════════════════════════════════════════════════════════════╝
+```
+
+Run: `/create-task-list for issue #[NUMBER] --use-existing-tasks`
+
+---
+
+**If IS_TASK_READY = false:**
+
+Display:
+```
+╔═══════════════════════════════════════════════════════════════╗
+║  📋 Starting Issue #[NUMBER] (Needs Analysis)                 ║
+╠═══════════════════════════════════════════════════════════════╣
+║  Running full /create-task-list workflow for:                 ║
+║    • Task generation via codebase exploration                 ║
+║    • Testing configuration (Ralph loop, E2E)                  ║
+║    • Workflow setup (branch, board sync)                      ║
+║    • Option to update issue with generated tasks              ║
+╚═══════════════════════════════════════════════════════════════╝
+```
+
+Run: `/create-task-list for issue #[NUMBER]`
+
+After `/create-task-list` completes and generates tasks, ask:
+
+```
+header: "Update"
+question: "Update GitHub issue with generated task list?"
+options:
+  - label: "Y - Yes, update issue"
+    description: "Add task checklist to issue body"
+  - label: "N - No, just implement"
+    description: "Keep issue as-is, start work"
+```
+
+If user selects Y:
+```bash
+# Append task checklist to issue body
+gh issue edit [NUMBER] --body "$(gh issue view [NUMBER] --json body -q .body)
+
+## Task Checklist (Auto-generated)
+
+- [ ] Task 1
+- [ ] Task 2
+..."
+```
+
+---
+
+## ERROR HANDLING
+
+| Error | Action |
+|-------|--------|
+| Issue not found | Display "Issue #[N] not found" and exit |
+| gh not authenticated | Show `gh auth login` instructions |
+| Invalid issue number | Ask user to provide valid number |
+| Network error | Show retry option |
+
+---
+
+## RELATED COMMANDS
+
+- `/menu-issues-list` - Browse all open issues with menu
+- `/create-task-list` - Create task list from any prompt
+- `/github-task-start` - Start working on issue (simpler flow)
+- `/github-update` - Sync with project board

package/templates/commands/create-task-list.template.md

@@ -27,11 +27,32 @@ allowed-tools:
 ```bash
 /create-task-list fix the login page redirect bug
 /create-task-list add dark mode to the settings panel
+/create-task-list for issue #123                      # Analyze issue, generate tasks
+/create-task-list for issue #123 --use-existing-tasks # Use issue's task checklist
 /create-task-list
 ```
 
 ---
 
+## FLAGS & ARGUMENTS
+
+| Argument | Description |
+|----------|-------------|
+| `for issue #[N]` | Pull context from GitHub issue #N |
+| `--use-existing-tasks` | Skip task generation, use issue's existing `## Task Checklist` |
+
+**When `for issue #[NUMBER]` is specified:**
+1. Fetch issue via `gh issue view [NUMBER] --json number,title,body,labels`
+2. Use issue title + body as the task prompt
+3. Extract labels for context (frontend, backend, P1, etc.)
+
+**When `--use-existing-tasks` is specified:**
+1. Parse existing checklist from `## Task Checklist` or `## Acceptance Criteria`
+2. Skip Step 5 (task generation) - use parsed tasks directly
+3. Still run full workflow: exploration, testing questions, workflow options
+
+---
+
 ## PERSISTENT INSTRUCTIONS
 
 **IMPORTANT**: Reference the persistent testing/deployment rules from `.claude/task-lists/TESTING_RULES.md`.
@@ -142,15 +163,53 @@ These rules govern:
 
 ---
 
-### Step 1: Capture User Prompt
+### Step 1: Capture User Prompt & Parse Flags
 
 ```
 PROMPT: $ARGUMENTS
 
+Parse for special patterns:
+  - "for issue #[NUMBER]" → Set GITHUB_ISSUE_NUMBER, fetch issue
+  - "--use-existing-tasks" → Set USE_EXISTING_TASKS=true
+
 If no arguments provided:
   → Use AskUserQuestion: "What would you like to accomplish today?"
 ```
 
+**If GITHUB_ISSUE_NUMBER is set:**
+
+```bash
+# Fetch full issue details
+gh issue view [NUMBER] --json number,title,body,labels,url
+```
+
+**Store issue data:**
+```json
+{
+  "issue_number": [NUMBER],
+  "issue_title": "[title]",
+  "issue_body": "[body]",
+  "issue_labels": ["label1", "label2"],
+  "issue_url": "[url]"
+}
+```
+
+**Set PROMPT** to: `[Issue Title]: [First 500 chars of body]`
+
+**If USE_EXISTING_TASKS is true:**
+1. Parse `## Task Checklist` or `## Acceptance Criteria` from issue body
+2. Extract checkbox items: `- [ ] Task description`
+3. Store as `EXISTING_TASKS` array
+4. Display:
+   ```
+   ╔═══════════════════════════════════════════════════════════════╗
+   ║  📋 Using Existing Tasks from Issue #[NUMBER]                 ║
+   ╠═══════════════════════════════════════════════════════════════╣
+   ║  Found [N] tasks in issue checklist                           ║
+   ║  Will skip task generation, use these tasks directly          ║
+   ╚═══════════════════════════════════════════════════════════════╝
+   ```
+
 ### Step 2: Context Assessment
 
 Evaluate the prompt for:
@@ -289,18 +348,50 @@ options:
 **Question 2: SKIP** (E2E not configured - skip this question)
 {{/if}}
 
-**Question 3: GitHub Integration**
+---
+
+### Step 4b: MANDATORY Workflow Questions (ALWAYS ASK)
+
+**CRITICAL**: After presenting findings, you MUST ask these 4 questions using AskUserQuestion.
+Users can answer with combinations like: `1, 2` or `1 & 3` or `1,2,4` or `all` or `none`.
+
+**Parse combination answers**: If user responds with numbers (e.g., "1, 2" or "1 & 3 & 4"), enable ALL selected options.
+
 ```
-header: "GitHub"
-question: "Would you like to create a tracked GitHub issue for this task list?"
+header: "Workflow Options"
+question: "Select workflow options (combine with commas: 1,2 or 1 & 3):\n\n1. Create GitHub Issue on remote repo\n2. Add issue to Project Board\n3. Create new branch before implementing\n4. Create new git worktree\n\nWhich options? (e.g., '1,2' or 'all' or 'none')"
 options:
-  - label: "Yes - Create GitHub issue (Recommended)"
-    description: "Creates issue with codebase analysis, adds to project board, auto-updates progress"
-  - label: "No - Local task list only"
-    description: "Just use TodoWrite without GitHub tracking"
-```
+  - label: "1 - GitHub Issue only"
+    description: "Create tracked issue with codebase analysis"
+  - label: "1, 2 - Issue + Project Board (Recommended)"
+    description: "Create issue AND add to project board"
+  - label: "1, 2, 3 - Issue + Board + Branch"
+    description: "Full workflow: issue, board, and new branch"
+  - label: "All (1, 2, 3, 4)"
+    description: "Everything: issue, board, branch, and worktree"
+  - label: "None - Local only"
+    description: "Skip all GitHub integration, just local TodoWrite"
+```
+
+**Parse user's selection** and store flags:
+- `CREATE_GITHUB_ISSUE`: true if "1" selected
+- `ADD_TO_PROJECT_BOARD`: true if "2" selected
+- `CREATE_NEW_BRANCH`: true if "3" selected
+- `CREATE_WORKTREE`: true if "4" selected
+
+**Combination Parsing Rules**:
+| User Input | Parsed Options |
+|------------|----------------|
+| `1` | Issue only |
+| `1, 2` or `1,2` or `1 & 2` | Issue + Board |
+| `1,2,3` or `1, 2, 3` | Issue + Board + Branch |
+| `1 & 2 & 4` | Issue + Board + Worktree |
+| `all` or `1,2,3,4` | All options |
+| `none` or `0` | No GitHub integration |
 
-**Question 4: Confirm Plan** (only if plan needs adjustment)
+---
+
+**Question 4: Confirm Plan**
 ```
 header: "Plan"
 question: "Does this approach look correct, or should I adjust?"
@@ -330,6 +421,25 @@ options:
 
 ### Step 5: Create Task List
 
+**If USE_EXISTING_TASKS is true (from `--use-existing-tasks` flag):**
+
+Skip task generation. Use the tasks parsed from the GitHub issue in Step 1.
+
+```
+╔═══════════════════════════════════════════════════════════════╗
+║  📋 Using Existing Tasks from Issue #[NUMBER]                 ║
+╠═══════════════════════════════════════════════════════════════╣
+║  Skipping task generation - using issue's checklist           ║
+║  Tasks will be wrapped with testing/deployment context        ║
+╚═══════════════════════════════════════════════════════════════╝
+```
+
+**Convert EXISTING_TASKS to TodoWrite format**, wrapping with context tasks (Task 0 for rules, final task for commit).
+
+---
+
+**If USE_EXISTING_TASKS is false (default):**
+
 Use **TaskCreate** to build the task list with Claude's native system.
 
 **Task List Structure** (adapts based on TESTING_CONFIGURED status):
@@ -408,13 +518,81 @@ The user should manually verify changes work before committing.
 
 ---
 
-### Step 6: Create GitHub Issue (If Selected)
+### Step 6: Execute Workflow Options (Based on Step 4b Selection)
+
+Execute the workflow options selected by the user in Step 4b. Process in this order:
+
+---
+
+#### Step 6a: Create New Branch (if CREATE_NEW_BRANCH = true)
+
+**Before any GitHub operations, create the working branch:**
+
+```bash
+# Generate branch name from task description
+# Format: feature/[short-description] or fix/[short-description]
+
+gh api repos/{owner}/{repo} --jq '.default_branch' # Get default branch
+git checkout -b [branch-name]
+git push -u origin [branch-name]
+```
+
+**Display confirmation:**
+```
+╔═══════════════════════════════════════════════════════════════╗
+║  ✅ New Branch Created                                        ║
+╠═══════════════════════════════════════════════════════════════╣
+║  Branch: [branch-name]                                        ║
+║  Based on: [default-branch]                                   ║
+║  Pushed to: origin/[branch-name]                              ║
+╚═══════════════════════════════════════════════════════════════╝
+```
+
+---
+
+#### Step 6b: Create Git Worktree (if CREATE_WORKTREE = true)
+
+**Create isolated worktree for parallel development:**
+
+```bash
+# Create worktree directory
+git worktree add ../[project-name]-[branch-name] [branch-name]
+
+# Display path to worktree
+```
+
+**Display confirmation:**
+```
+╔═══════════════════════════════════════════════════════════════╗
+║  ✅ Git Worktree Created                                      ║
+╠═══════════════════════════════════════════════════════════════╣
+║  Location: ../[project-name]-[branch-name]                    ║
+║  Branch: [branch-name]                                        ║
+║                                                               ║
+║  To work in worktree:                                         ║
+║    cd ../[project-name]-[branch-name]                         ║
+║                                                               ║
+║  To remove when done:                                         ║
+║    git worktree remove ../[project-name]-[branch-name]        ║
+╚═══════════════════════════════════════════════════════════════╝
+```
+
+**Ask user:**
+```
+header: "Worktree"
+question: "Worktree created. Work in worktree or current directory?"
+options:
+  - label: "Continue in current directory"
+    description: "Stay here, worktree is for manual use"
+  - label: "Switch to worktree"
+    description: "I'll restart Claude Code in the worktree directory"
+```
 
-If user selected GitHub integration:
+---
 
-#### Step 6a: Preview Issue Before Creation
+#### Step 6c: Create GitHub Issue (if CREATE_GITHUB_ISSUE = true)
 
-**Present issue preview to user** before creating:
+**Present issue preview:**
 
 ```markdown
 ## GitHub Issue Preview
@@ -423,6 +601,7 @@ If user selected GitHub integration:
 **Priority:** P2-Medium (or determined from analysis)
 **Labels:** [Determined from exploration - frontend, backend, feature, bug, etc.]
 **Stack:** [Frontend only | Backend only | Both]
+**Branch:** [branch-name if created, else "will create on first commit"]
 
 **Description Preview:**
 > [First 200 characters of the analysis from Step 3...]
@@ -433,95 +612,109 @@ If user selected GitHub integration:
 - [ ] ...
 ```
 
-**Ask for confirmation using AskUserQuestion:**
-```
-header: "Create GitHub Issue?"
-question: "Ready to create this GitHub issue? Review the preview above."
-options:
-  - label: "Yes - Create Issue"
-    description: "Create the issue and enable auto-progress tracking"
-  - label: "Modify Details"
-    description: "I want to change the title, priority, or labels"
-  - label: "Skip GitHub"
-    description: "Don't create issue, use local TodoWrite only"
-```
+**Create the issue:**
+```bash
+gh issue create \
+  --title "[Task description]" \
+  --body "$(cat <<'EOF'
+## Description
 
-**Handle user response:**
-- **"Yes - Create Issue"**: Proceed to create the issue (Step 6b)
-- **"Modify Details"**: Ask which fields to change, then show preview again
-- **"Skip GitHub"**: Skip to Step 7, note that GitHub tracking is disabled
+[User's original prompt]
 
----
+## Codebase Analysis
 
-#### Step 6b: Create the Issue
+[Include findings from Step 3 exploration agents]
 
-1. **Create comprehensive issue** using `/github-create-task`:
-   ```bash
-   /github-create-task --batch-mode
+## Task Checklist
 
-   Title: [Task description from user prompt]
-   Priority: P2-Medium
-   Labels: [Determined from exploration - frontend, backend, feature, bug, etc.]
-   QA: [Required if P0/P1, else Not Required]
-   Stack: [Frontend only|Backend only|Both]
+[Mirror the TodoWrite tasks as checkboxes]
+- [ ] Task 1: ...
+- [ ] Task 2: ...
 
-   ## Description
+---
+Generated by `/create-task-list`
+EOF
+)" \
+  --label "[labels]"
+```
+
+**Store issue number:**
+```json
+// Write to .claude/task-lists/session-{timestamp}.json
+{
+  "github_issue": {
+    "number": [ISSUE_NUM],
+    "url": "[ISSUE_URL]",
+    "created_at": "[ISO timestamp]"
+  },
+  "branch": "[branch-name]",
+  "worktree": "[worktree-path or null]"
+}
+```
 
-   [User's original prompt]
+---
 
-   ## Codebase Analysis
+#### Step 6d: Add to Project Board (if ADD_TO_PROJECT_BOARD = true)
 
-   [Include findings from Step 3 exploration agents]
+**Add the created issue to the configured project board:**
 
-   ## Task Checklist
+```bash
+# Get project board number from tech-stack.json or .gtaskrc
+# {{versionControl.projectBoard.number}}
 
-   [Mirror the TodoWrite tasks as checkboxes]
-   - [ ] Task 1: ...
-   - [ ] Task 2: ...
-   ```
+gh project item-add [PROJECT_NUMBER] \
+  --owner [OWNER] \
+  --url [ISSUE_URL]
+```
 
-2. **Store issue number** for progress tracking:
-   ```json
-   // Write to .claude/task-lists/session-{timestamp}.json
-   {
-     "github_issue": {
-       "number": [ISSUE_NUM],
-       "url": "[ISSUE_URL]",
-       "created_at": "[ISO timestamp]"
-     }
-   }
-   ```
+**Display confirmation:**
+```
+╔═══════════════════════════════════════════════════════════════╗
+║  ✅ Added to Project Board                                    ║
+╠═══════════════════════════════════════════════════════════════╣
+║  Issue: #[ISSUE_NUMBER]                                       ║
+║  Board: [PROJECT_NAME] (#[PROJECT_NUMBER])                    ║
+║  Status: [Default column - usually "To Do" or "Backlog"]      ║
+╚═══════════════════════════════════════════════════════════════╝
+```
 
-3. **Install progress hook** (auto-updates GitHub issue when tasks complete):
-   - The hook watches for TodoWrite calls
-   - When a task is marked `completed`, it updates the GitHub issue:
-     - Checks off the corresponding checkbox
-     - Adds a progress comment if significant milestone
-   - See `.claude/hooks/tools/github-progress-hook.js`
+---
 
-#### Step 6c: Post-Creation Confirmation
+#### Step 6e: Summary of Workflow Actions
 
-After the issue is created, **display confirmation and ask how to proceed**:
+**Display summary of all completed workflow actions:**
 
-```markdown
+```
 ╔═══════════════════════════════════════════════════════════════╗
-║  ✅ GitHub Issue Created Successfully                         ║
+║  📋 Workflow Setup Complete                                   ║
 ╠═══════════════════════════════════════════════════════════════╣
-║                                                               ║
-║  Issue: #[ISSUE_NUMBER]                                       ║
-║  URL: https://github.com/[owner]/[repo]/issues/[number]       ║
-║                                                               ║
-║  Auto-progress tracking enabled:                              ║
-║  • Tasks will auto-update issue as they complete              ║
-║  • Checkboxes will be checked off automatically               ║
-║                                                               ║
+{{#if CREATE_NEW_BRANCH}}
+║  ✅ Branch: [branch-name]                                     ║
+{{/if}}
+{{#if CREATE_WORKTREE}}
+║  ✅ Worktree: ../[worktree-path]                              ║
+{{/if}}
+{{#if CREATE_GITHUB_ISSUE}}
+║  ✅ Issue: #[ISSUE_NUMBER] - [title]                          ║
+║     URL: [ISSUE_URL]                                          ║
+{{/if}}
+{{#if ADD_TO_PROJECT_BOARD}}
+║  ✅ Project Board: Added to [PROJECT_NAME]                    ║
+{{/if}}
+{{#unless CREATE_GITHUB_ISSUE}}
+{{#unless CREATE_NEW_BRANCH}}
+{{#unless CREATE_WORKTREE}}
+║  ℹ️  Local task list only (no GitHub integration)             ║
+{{/unless}}
+{{/unless}}
+{{/unless}}
 ╚═══════════════════════════════════════════════════════════════╝
 ```
 
-**Ask user how to proceed using AskUserQuestion:**
+**Ask user how to proceed:**
 ```
-header: "Issue Created"
-question: "GitHub issue #[NUMBER] created. What would you like to do?"
+header: "Workflow Ready"
+question: "Workflow setup complete. What would you like to do?"
 options:
   - label: "Continue to Task Execution"
     description: "Proceed with creating and executing the task list"
@@ -580,7 +773,12 @@ const config = {
    - To enable: run `ccasp test-setup`
 {{/if}}
    - Execution Strategy: [Sequential / Grouped / All at once]
-   - GitHub Issue: [#123 (if created) | Not tracked]
+
+   **Workflow Setup:**
+   - GitHub Issue: [#123 | Not created]
+   - Project Board: [Added to Board #X | Not added]
+   - Branch: [feature/task-name | Using current branch]
+   - Worktree: [../project-branch | Not created]
    ```
 
 #### Step 8b: Final Confirmation Before Execution