nexus-gateway: Skill for Claude Code

Multi-Role Review Prompt Guide

---

Overview

This guide contains review prompts for 9 specialist roles, designed for a full-system audit of the AI Gateway (Admin Dashboard, client, API, architecture, security, compliance, etc.).

Findings from every role must be remediated through the standard implementation workflow:

Architecture → Requirements → SDD → OpenAPI Spec → Code → Unit Tests → Verification

---

Common review standards

The three items below are mandatory defaults for every role prompt and are embedded in each role's execution flow.

---

1. Enable extended thinking

Use extended thinking to reason through all findings before responding.

Before producing any finding, Claude must internally reason through:

• The root cause and impact chain of the issue
• Cross-module and cross-role ripple effects
• Edge cases and underlying assumptions
• Feasibility and side effects of the proposed fix

---

2. Severity-ordered output

Every finding must be classified and ordered by the levels below:

Level	Marker	Definition
Critical	🚨	Systemic risk affecting core function or security; fix immediately
High	🔴	Important missing function or severe UX issue; fix in the current iteration
Medium	🟡	Incomplete function or sub-optimal UX; fix in an upcoming iteration
Low	🟢	Optimization; add to the backlog for opportunistic pickup

Output order: Critical → High → Medium → Low.

---

3. JIRA-ready ticket format

Every finding must be rendered in the format below:

───────────────────────────────────────────
JIRA TICKET
───────────────────────────────────────────
Title        : [role-prefix]-[number] short problem title
Type         : Gap / Issue / Improvement
Severity     : Critical / High / Medium / Low
Role         : the review role that surfaced the issue

Description  :
  [Clearly describe current behavior, trigger conditions, and context]

Impact       :
  [Describe the impact on users, business, and the system]

Fix Plan     :
  1. Architecture — [architecture-level response]
  2. Requirements — [additions needed in the requirements doc]
  3. SDD          — [updates needed in the software design doc]
  4. OpenAPI      — [API spec changes]
  5. Code         — [implementation guidance and gotchas]
  6. Unit Tests   — [test cases that must be covered]
  7. Verification — [acceptance criteria and verification methods]

Acceptance Criteria :
  - [ ] Condition 1
  - [ ] Condition 2
  - [ ] Condition 3

Estimated Effort : [X] Story Points  |  about [X] person-days
───────────────────────────────────────────