plan-review
Auto-assembles review panel using deterministic rules, dispatches agents against plan file, collects verdicts.
What this skill does
Phase gate: PLAN checkpoint. MUST get APPROVE from all reviewers before proceeding to Build. ## Inputs - Plan file path (default: most recent non-`.done.md` file in `ai-workspace/plans/`) - `--include <agent>`: Force-add an agent to the panel - `--exclude <agent>`: Remove an agent (except technical-editor, which cannot be excluded) ## Steps 1. **Find the plan file**: ```bash ls -t "$(git rev-parse --show-toplevel)/ai-workspace/plans/"*.md | grep -v '.done.md' | head -1 ``` If no plan file found → error: "No plan file in ai-workspace/plans/. Write a plan first." If plan file is `.done.md` → error: "This plan is already finalized." 2. **Read the plan** and extract: - Files to Modify section - Full body text - Plan scope (count files changed, count body lines) 3. **Assemble the review panel** — invoke `/assemble-panel` with scope = plan file. It returns the panel based on file types and keywords in the plan. Pass `--include`/`--exclude` as overrides. Log which agents were selected and why. Codex/Cursor: read `.claude/skills/assemble-panel/SKILL.md` directly and apply the scope/keyword maps inline. If `/assemble-panel` is unavailable, fall back to `[technical-editor, code-reviewer]` with gate=P2, cap=3. 4. **Dispatch all selected agents IN PARALLEL** using the Agent tool (single message, multiple Agent tool calls). Each agent receives: - The plan file content - Their specific review mandate - Instructions to return: APPROVE / REVISE / DROP with findings tagged P0/P1/P2 5. **Collect verdicts** and synthesize into a summary table: ``` ## Plan Review Summary | Agent | Verdict | P0 | P1 | P2 | Key Finding | |-------|---------|----|----|-----|-------------| ``` 6. **Gate logic and review loop** — invoke `/assemble-panel` for panel governance. It provides the policy algebra (gate=P2, cap=3) and handles RETAIN, EXPAND, CONVERGE, and ESCALATE_RECURRING. Do not duplicate those rules here. After each round: - All APPROVE with no above-gate findings → "Proceed to Build" - Above-gate findings remain → fix, then re-review per assemble-panel's RETAIN + EXPAND rules - Cap reached with unresolved findings → escalate to human If `/assemble-panel` is unavailable, fall back: keep all reviewers with above-gate findings, exit at round 3 or when all clean. ## Panel Bounds - Minimum: technical-editor alone (1 agent, trivial plans) - Typical: technical-editor + code-reviewer + architect-reviewer (3) - Maximum: all agents (rare, large cross-cutting plans)
Related in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.