Generalize workflow commands for multiple documentation and ticketing systems

Summary

The current workflow commands (execute-ticket.md, create-implementation-plan.md, etc.) are tightly coupled to Confluence and Jira. These should be generalized to support multiple documentation and ticketing systems with a local-first methodology.

Current State

Hard-coded Assumptions

• Documentation: Confluence only
• Ticketing: Jira only
• Workflow: Cloud-first (fetch from remote, update remote)

Affected Files

• .claude/commands/execute-ticket.md
• .claude/commands/create-implementation-plan.md
• .claude/commands/create-epic-plan.md
• .claude/commands/complete-epic.md
• .claude/commands/complete-sprint.md

Proposed Changes

1. Support Multiple Documentation Systems

2. Support Multiple Ticketing Systems

3. Local-First Sync Methodology

Proposed Workflow:

Local State (Source of Truth)
    ↓
Work locally on markdown files
    ↓
On push to [Branch] → Sync to cloud systems
    ↓
Cloud systems updated atomically

Benefits:

• Works offline
• Version controlled
• No vendor lock-in
• Faster iteration
• Git as audit trail

4. Integration with GITHUB_ISSUE_TREE.md

Reference: research/GITHUB_ISSUE_TREE.md

• Use local issue tree as planning artifact
• Sync to GitHub Issues on push
• Maintain bidirectional links

Implementation Approach

Option A: Adapter Pattern

Create adapters for each system:

commands/
├── execute-ticket.md (generic)
└── adapters/
    ├── jira-adapter.md
    ├── github-adapter.md
    └── local-adapter.md

Option B: Configuration-Based

Add system configuration to CLAUDE.md:

## Project Configuration
- Documentation: github-wiki | confluence | notion | local
- Ticketing: github-issues | jira | linear | local
- Sync Strategy: local-first | cloud-first

Option C: Auto-Detection

Detect based on project context:

• Has .jira config? → Jira
• Has GitHub remote? → GitHub Issues
• Has Notion integration? → Notion
• Default → Local markdown

Acceptance Criteria

• Commands work without Confluence/Jira
• Local-first workflow documented
• At least 2 documentation systems supported
• At least 2 ticketing systems supported
• Sync-on-push methodology defined
• GITHUB_ISSUE_TREE.md integration specified