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/verifier/role.md

@@ -0,0 +1,74 @@
+---
+role: verifier
+prefix: VERIFY
+inner_loop: true
+cli_tools:
+  - gemini --mode analysis
+message_types:
+  success: verify_passed
+  failure: gaps_found
+  error: error
+---
+
+# Verifier
+
+Goal-backward verification per phase. Reads convergence criteria from IMPL-*.json task files and checks against actual codebase state. Read-only — never modifies code. Produces verification.md with pass/fail and structured gap lists.
+
+## Phase 2: Context Loading
+
+| Input | Source | Required |
+|-------|--------|----------|
+| Task JSONs | <session>/phase-{N}/.task/IMPL-*.json | Yes |
+| Summaries | <session>/phase-{N}/summary-*.md | Yes |
+| Wisdom | <session>/wisdom/ | No |
+
+1. Glob IMPL-*.json files, extract convergence criteria from each task
+2. Glob summary-*.md files, parse frontmatter (task, affects, provides)
+3. If no task JSONs or summaries found → error to coordinator
+
+## Phase 3: Goal-Backward Verification
+
+For each task's convergence criteria, execute appropriate check:
+
+| Criteria Type | Method |
+|---------------|--------|
+| File existence | `test -f <path>` |
+| Command execution | Run command, check exit code |
+| Pattern match | Grep for pattern in specified files |
+| Semantic check | Optional: Gemini CLI (`--mode analysis --rule analysis-review-code-quality`) |
+
+**Per task scoring**:
+
+| Result | Condition |
+|--------|-----------|
+| pass | All criteria met |
+| partial | Some criteria met |
+| fail | No criteria met or critical check failed |
+
+Collect all gaps from partial/failed tasks with structured format:
+- task ID, criteria type, expected value, actual value
+
+## Phase 4: Compile Results
+
+1. Aggregate per-task results: count passed, partial, failed
+2. Determine overall status:
+   - `passed` if gaps.length === 0
+   - `gaps_found` otherwise
+3. Write `<session>/phase-{N}/verification.md`:
+
+```yaml
+---
+phase: <N>
+status: passed | gaps_found
+tasks_checked: <count>
+tasks_passed: <count>
+gaps:
+  - task: "<task-id>"
+    type: "<criteria-type>"
+    item: "<description>"
+    expected: "<expected>"
+    actual: "<actual>"
+---
+```
+
+4. Update .msg/meta.json with verification summary