القائمة
WHEN: Implementation or a plan is done and you want a structured second pass from another model or reviewer before merge — same repo, no new automation required.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | second-opinion-review |
| description | WHEN: Implementation or a plan is done and you want a structured second pass from another model or reviewer before merge — same repo, no new automation required. |
| type | flexible |
| requires | ["forge-trust-code"] |
| version | 1.0.0 |
| preamble-tier | 3 |
| triggers | ["second opinion","another model review","dual review"] |
| allowed-tools | ["Bash","Read"] |
Use this after your primary implementation pass and after you would normally invoke forge-trust-code. It does not replace spec review; it adds an explicit independent reasoning pass so obvious gaps are not missed because one session anchored on the same assumptions.
| Skill | Mandatory? | When to invoke | Output |
|---|---|---|---|
forge-trust-code | YES | After implementation, before eval — reviewer reads actual diff | Spec compliance verdict (PASS/FAIL) |
second-opinion-review | No (recommended for high-stakes) | After forge-trust-code passes, when a second perspective is valuable | Independent reasoning pass — confirms or flags concerns |
review-readiness | YES | Immediately before PR creation | All gates passed checklist (eval GREEN, tests passing, no open TODOs) |
When to use this skill (second-opinion-review): When forge-trust-code has passed but the change is high-risk (security-sensitive, cross-service contract, performance-critical). A second reviewer reads the same diff independently, without seeing the first reviewer's conclusions.
| Rationalization | Why it fails |
|---|---|
| "I'll just ask the same model again" | Same context window, same biases. A second pass only helps if the prompt or reviewer changes materially. |
| "Second opinion = slower, skip it" | Cheaper than a revert. Scope it: one file, one risk area, or one contract slice. |
| "I'll merge and fix if reviewers complain" | Post-merge fixes cost more than a 10-minute focused second read on hot paths. |
prd-locked.md) plus any shared-dev-spec excerpt that matters.forge-brain-persist (what was missed, what you fixed).After the checklist, apply this decision table — do not leave it to judgment call alone:
| Condition | Action |
|---|---|
| All checklist items Pass | Proceed to merge. |
| Any Gap in auth, authz, or contract alignment | Block merge. Open a NEEDS_COORDINATION item per forge-glossary and resolve before merge. |
| Any Gap in non-critical paths (logging, copy, non-auth error messages) | Log with forge-brain-persist (what was missed, follow-up task id). Proceed with the tracked item. |
| ≥ 2 Gaps of any kind | Block merge regardless of individual severity — multiple small gaps compound at runtime. |
conductor-orchestrate still owns phase order. This skill is an optional adjunct before merge when stakes or ambiguity are high.
conductor-orchestrate: Orchestrates the pipeline phases; second-opinion-review is an optional adjunct invoked before merge when stakes or ambiguity are high.spec-reviewer: First-pass code review; second-opinion-review provides an independent perspective after spec-reviewer has passed.code-quality-reviewer: Code quality audit; second-opinion-review can serve as a final check when code-quality-reviewer surfaced concerns.forge-eval-gate: Eval gate before merge; second-opinion-review is a peer review safeguard complementary to eval.WHEN: You need to detect performance regressions before merge — TTFB, response time, bundle size. Run as part of forge-eval-gate or standalone before raising a PR.
WHEN: A decision is being superseded, deprecated, or has aged out. Archive it without deletion — marks as warm→cold→archived with full audit trail.
WHEN: You are writing a new decision, superseding an old one, or querying relationships across decisions. Create semantic edges between decisions and link concepts across products/projects/time.
WHEN: You are about to make a decision and need to check if prior art or past learnings exist. Recall decisions, patterns, and gotchas from the brain before proceeding.
WHEN: You need to trace the full provenance of a specific decision — who made it, when, why, and what alternatives were considered. Shows why, when, by whom, evidence, alternatives, outcome.
WHEN: You need to record a decision, lock a spec, log an eval run, or document learnings in the brain.