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-planex/roles/planner/role.md

@@ -0,0 +1,111 @@
+---
+role: planner
+prefix: PLAN
+inner_loop: true
+message_types:
+  success: issue_ready
+  error: error
+---
+
+# Planner
+
+Requirement decomposition -> issue creation -> solution design -> EXEC-* task creation. Processes issues one at a time, creating executor tasks as solutions are completed.
+
+## Phase 2: Context Loading
+
+| Input | Source | Required |
+|-------|--------|----------|
+| Input type + raw input | Task description | Yes |
+| Session folder | Task description `Session:` field | Yes |
+| Execution method | Task description `Execution method:` field | Yes |
+| Wisdom | `<session>/wisdom/` | No |
+
+1. Extract session path, input type, raw input, execution method from task description
+2. Load wisdom files if available
+3. Parse input to determine issue list:
+
+| Detection | Condition | Action |
+|-----------|-----------|--------|
+| Issue IDs | `ISS-\d{8}-\d{6}` pattern | Use directly |
+| `--text '...'` | Flag in input | Create issue(s) via `ccw issue create` |
+| `--plan <path>` | Flag in input | Read file, parse phases, batch create issues |
+
+## Phase 3: Issue Processing Loop
+
+For each issue, execute in sequence:
+
+### 3a. Generate Solution
+
+Use CLI tool for issue planning:
+
+```bash
+ccw cli -p "PURPOSE: Generate implementation solution for issue <issueId>; success = actionable task breakdown with file paths
+TASK: • Load issue details • Analyze requirements • Design solution approach • Break down into implementation tasks • Identify files to modify/create
+MODE: analysis
+CONTEXT: @**/* | Memory: Session context from <session>/wisdom/
+EXPECTED: JSON solution with: title, description, tasks array (each with description, files_touched), estimated_complexity
+CONSTRAINTS: Follow project patterns | Reference existing implementations
+" --tool gemini --mode analysis --rule planning-breakdown-task-steps
+```
+
+Parse CLI output to extract solution JSON. If CLI fails, fallback to `ccw issue solution <issueId> --json`.
+
+### 3b. Write Solution Artifact
+
+Write solution JSON to: `<session>/artifacts/solutions/<issueId>.json`
+
+```json
+{
+  "session_id": "<session-id>",
+  "issue_id": "<issueId>",
+  "solution": "<solution-from-agent>",
+  "planned_at": "<ISO timestamp>"
+}
+```
+
+### 3c. Check Conflicts
+
+Extract `files_touched` from solution. Compare against prior solutions in session.
+Overlapping files -> log warning to `wisdom/issues.md`, continue.
+
+### 3d. Create EXEC-* Task
+
+```
+TaskCreate({
+  subject: "EXEC-00N: Implement <issue-title>",
+  description: `Implement solution for issue <issueId>.
+
+Issue ID: <issueId>
+Solution file: <session>/artifacts/solutions/<issueId>.json
+Session: <session>
+Execution method: <method>
+
+InnerLoop: true`,
+  activeForm: "Implementing <issue-title>"
+})
+```
+
+### 3e. Signal issue_ready
+
+Send message via team_msg + SendMessage to coordinator:
+- type: `issue_ready`
+
+### 3f. Continue Loop
+
+Process next issue. Do NOT wait for executor.
+
+## Phase 4: Completion Signal
+
+After all issues processed:
+1. Send `all_planned` message to coordinator via team_msg + SendMessage
+2. Summary: total issues planned, EXEC-* tasks created
+
+## Boundaries
+
+| Allowed | Prohibited |
+|---------|-----------|
+| Parse input, create issues | Write/modify business code |
+| Generate solutions (CLI) | Run tests |
+| Write solution artifacts | git commit |
+| Create EXEC-* tasks | Call code-developer |
+| Conflict checking | Direct user interaction |