feat: Add templates for epics, product brief, and requirements documentation

- Introduced a comprehensive template for generating epics and stories in Phase 5, including an index and individual epic files.
- Created a product brief template for Phase 2 to summarize product vision, goals, and target users.
- Developed a requirements PRD template for Phase 3, outlining functional and non-functional requirements, along with traceability matrices.

feat: Implement tech debt roles for assessment, execution, planning, scanning, validation, and analysis

- Added roles for tech debt assessment, executor, planner, scanner, validator, and analyst, each with defined phases and processes for managing technical debt.
- Each role includes structured input requirements, processing strategies, and output formats to ensure consistency and clarity in tech debt management.

.claude/skills/team-issue/roles/planner/role.md

@@ -0,0 +1,81 @@
+---
+role: planner
+prefix: SOLVE
+inner_loop: false
+additional_prefixes: [SOLVE-fix]
+message_types: [solution_ready, multi_solution, error]
+---
+
+# Issue Planner
+
+Design solutions and decompose into implementation tasks. Uses CLI tools for ACE exploration and solution generation. For revision tasks (SOLVE-fix), design alternative approaches addressing reviewer feedback.
+
+## Phase 2: Context Loading
+
+| Input | Source | Required |
+|-------|--------|----------|
+| Issue ID | Task description (GH-\d+ or ISS-\d{8}-\d{6}) | Yes |
+| Explorer context | `<session>/explorations/context-<issueId>.json` | No |
+| Review feedback | Task description (for SOLVE-fix tasks) | No |
+| wisdom meta | <session>/wisdom/.msg/meta.json | No |
+
+1. Extract issue ID from task description via regex: `(?:GH-\d+|ISS-\d{8}-\d{6})`
+2. If no issue ID found -> report error, STOP
+3. Load explorer context report (if available):
+
+```
+Read("<session>/explorations/context-<issueId>.json")
+```
+
+4. Check if this is a revision task (SOLVE-fix-N):
+   - If yes, extract reviewer feedback from task description
+   - Design alternative approach addressing reviewer concerns
+5. Load wisdom files for accumulated codebase knowledge
+
+## Phase 3: Solution Generation via CLI
+
+**CLI invocation**:
+
+```
+Bash("ccw cli -p \"
+PURPOSE: Design solution for issue <issueId> and decompose into implementation tasks; success = solution bound to issue with task breakdown
+
+TASK: • Load issue details from ccw issue status • Analyze explorer context • Design solution approach • Break down into implementation tasks • Generate solution JSON • Bind solution to issue
+
+MODE: analysis
+
+CONTEXT: @**/* | Memory: Issue <issueId> - <issue.title> (Priority: <issue.priority>)
+Explorer findings: <explorerContext.key_findings>
+Relevant files: <explorerContext.relevant_files>
+Complexity: <explorerContext.complexity_assessment>
+
+EXPECTED: Solution JSON with: issue_id, solution_id, approach, tasks (ordered list with descriptions), estimated_files, dependencies
+Write to: <session>/solutions/solution-<issueId>.json
+Then bind: ccw issue bind <issueId> <solution_id>
+
+CONSTRAINTS: Follow existing patterns | Minimal changes | Address reviewer feedback if SOLVE-fix task
+\" --tool gemini --mode analysis", { run_in_background: false })
+```
+
+**Expected CLI output**: Solution file path and binding confirmation
+
+**Parse result**:
+
+```
+Read("<session>/solutions/solution-<issueId>.json")
+```
+
+## Phase 4: Solution Selection & Reporting
+
+**Outcome routing**:
+
+| Condition | Message Type | Action |
+|-----------|-------------|--------|
+| Single solution auto-bound | `solution_ready` | Report to coordinator |
+| Multiple solutions pending | `multi_solution` | Report for user selection |
+| No solution generated | `error` | Report failure to coordinator |
+
+Write solution summary to `<session>/solutions/solution-<issueId>.json`.
+
+Update `<session>/wisdom/.msg/meta.json` under `planner` namespace:
+- Read existing -> merge `{ "planner": { issue_id, solution_id, task_count, is_revision } }` -> write back