fix(commands): separate VCS and ticketing abstractions

VCS (GitHub/GitLab/Bitbucket) and ticketing (Jira/Linear/GitHub Issues)
are distinct concepts. Commands now reference the right abstraction:
- Issue/ticket commands use "ticketing tool" from memory
- PR/MR commands use VCS tool from memory

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Author: blafourcade

commands/03_plan/plan.md

@@ -1,7 +1,7 @@
 ---
 name: plan
 description: Generate technical implementation plans from requirements
-argument-hint: requirements (VCS issue URL or raw text)
+argument-hint: requirements (ticket URL or raw text)
 model: opus
 ---
 
@@ -40,9 +40,9 @@ $ARGUMENTS
 
 ### Step 1: Parse Input
 
-1. Detect input type (VCS issue URL vs raw text)
+1. Detect input type (ticket URL vs raw text)
 2. Extract requirements from input:
-   - For VCS issue: fetch and parse issue content
+   - For ticket URL: fetch and parse ticket content
    - For raw text: clean and structure the requirements
 3. Normalize text (handle vocal dictation issues)
 4. Print user journey simplified in ASCII diagram for better understanding and validation

commands/10_maintenance/new_issue.md

@@ -1,6 +1,6 @@
 ---
 name: new_issue
-description: Create issues in the configured VCS/ticketing tool
+description: Create issues in the configured ticketing tool
 argument-hint: "Describe the problem you want to create an issue for"
 model: sonnet
 ---
@@ -9,7 +9,7 @@ model: sonnet
 
 ## Goal
 
-Create an issue based on the problem: `$ARGUMENTS`
+Create a ticket based on the problem: `$ARGUMENTS`
 
 ## Context
 
@@ -27,7 +27,7 @@ Create an issue based on the problem: `$ARGUMENTS`
 
 ## Rules
 
-- From project memory identify the VCS/ticketing tool (GitHub, GitLab, Jira, etc.) and CLI or MCP to use.
+- From project memory identify the ticketing tool (Jira, Linear, GitHub Issues, etc.) and CLI or MCP to use.
 - Use CLI first, MCP as fallback.
 - Be thorough and concise in the issue description, focus on clarity, small sentences.
 - Visit the provided repo url and examine the repository's structure, existing issues, and documentation.

commands/10_maintenance/reproduce.md

@@ -21,7 +21,7 @@ Fix bug systematically using test-driven approach, from issue creation to pull r
 
 ## Steps
 
-1. Create issue in configured VCS/ticketing tool with short descriptive title
+1. Create ticket in configured ticketing tool with short descriptive title
 2. Create fix branch
 3. Reproduce issue and understand root cause
 4. Write failing test demonstrating bug