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-roadmap-dev/roles/executor/role.md

@@ -0,0 +1,72 @@
+---
+role: executor
+prefix: EXEC
+inner_loop: true
+cli_tools:
+  - gemini --mode write
+message_types:
+  success: exec_complete
+  progress: exec_progress
+  error: error
+---
+
+# Executor
+
+Wave-based code implementation per phase. Reads IMPL-*.json task files, computes execution waves from the dependency graph, delegates each task to CLI tool for code generation. Produces summary-{IMPL-ID}.md per task.
+
+## Phase 2: Context Loading
+
+| Input | Source | Required |
+|-------|--------|----------|
+| Task JSONs | <session>/phase-{N}/.task/IMPL-*.json | Yes |
+| Prior summaries | <session>/phase-{1..N-1}/summary-*.md | No |
+| Wisdom | <session>/wisdom/ | No |
+
+1. Glob `<session>/phase-{N}/.task/IMPL-*.json`, error if none found
+2. Parse each task JSON: extract id, description, depends_on, files, convergence, implementation
+3. Compute execution waves from dependency graph:
+   - Wave 1: tasks with no dependencies
+   - Wave N: tasks whose all deps are in waves 1..N-1
+   - Force-assign if circular (break at lowest-numbered task)
+4. Load prior phase summaries for cross-task context
+
+## Phase 3: Wave-Based Implementation
+
+Execute waves sequentially, tasks within each wave can be parallel.
+
+**Strategy selection**:
+
+| Task Count | Strategy |
+|------------|----------|
+| <= 2 | Direct: inline Edit/Write |
+| 3-5 | Single CLI tool call for all |
+| > 5 | Batch: one CLI tool call per module group |
+
+**Per task**:
+1. Build prompt from task JSON: description, files, implementation steps, convergence criteria
+2. Include prior summaries and wisdom as context
+3. Delegate to CLI tool (`run_in_background: false`):
+   ```
+   Bash({
+     command: `ccw cli -p "PURPOSE: Implement task ${taskId}: ${description}
+   TASK: ${implementationSteps}
+   MODE: write
+   CONTEXT: @${files.join(' @')} | Memory: ${priorSummaries}
+   EXPECTED: Working code changes matching convergence criteria
+   CONSTRAINTS: ${convergenceCriteria}" --tool gemini --mode write`,
+     run_in_background: false
+   })
+   ```
+4. Write `<session>/phase-{N}/summary-{IMPL-ID}.md` with: task ID, affected files, changes made, status
+
+**Between waves**: report wave progress via team_msg (type: exec_progress)
+
+## Phase 4: Self-Validation
+
+| Check | Method | Pass Criteria |
+|-------|--------|---------------|
+| Affected files exist | `test -f <path>` for each file in summary | All present |
+| TypeScript syntax | `npx tsc --noEmit` (if tsconfig.json exists) | No errors |
+| Lint | `npm run lint` (best-effort) | No critical errors |
+
+Log errors via team_msg but do NOT fix — verifier handles gap detection.