**Review Type:** Live Design Review (45 minutes)

> Produced using the `running-effective-meetings` skill pack.

**Problem:** The current weekly product review devolves into status updates, consistently runs over 60 minutes, and fails to produce clear decisions or unblock teams.

**Company:** Seed-stage B2B SaaS (API monitoring tool)

Set aligned OKRs/goals: objectives, key results, guardrails, review cadence.

Plan product launch/release: rollout/rollback plan, comms, monitoring, post-launch review. See also: launch-marketing (marketing side).

- **Focal decision/problem:** Engineering on-call page volume has tripled over 6 months (5 to 15 pages/week per team), causing burnout, declining code review rigor, and suspected rising incident rates

**Presenting problem:** On-call page volume has tripled over 6 months (5 to 15 pages/week per team), causing burnout, degraded code review quality, and a suspected increase in production incidents ---

> Produced using the `writing-job-descriptions` skill pack.

**Company:** [Stealth AI Startup] -- AI-Powered Contract Review for Legal Teams

>-

You are the night shift. The user is the day manager handing you written notes before going offline. Your job is to execute plan-driven work autonomously, batch by batch, with testing, review, and doc

Professional-grade contract review skill that adds comment-based issue annotations without changing original text. Enforces a four-layer review (entity verification, basic, business, legal), writes structured comments (issue type, risk reason, revision suggestion) with risk level encoded via reviewer name, and generates a contract summary, consolidated opinion, and Mermaid business flowchart (with rendered image). Output language must follow the contract’s language.

>

>

Delegate CJK/Chinese content tasks to Gemini CLI. Use this skill for writing Chinese reports, Threads posts (美洲更新), comments, translations, and any task requiring native-quality Traditional Chinese output. Gemini handles the content generation while Claude plans, reviews, and integrates.

Build, preview, and update the VitePress documentation site in docs-site/

Google Gemini API integration for building AI-powered applications. Use when working with Google's Gemini API, Python SDK (google-genai), TypeScript SDK (@google/genai), multimodal inputs (image, video, audio, PDF), thinking/reasoning features, streaming responses, structured outputs with JSON schemas, multi-turn chat, system instructions, image generation (Nano Banana), video generation (Veo), music generation (Lyria), embeddings, document/PDF processing, or any Gemini API integration task. Triggers on mentions of Gemini, Gemini 3, Gemini 2.5, Google AI, Nano Banana, Veo, Lyria, google-genai, or @google/genai SDK usage.

Review actual code implementations (Python, JavaScript, TypeScript, React) for correctness, maintainability, security hygiene, and adherence to project patterns. Use when reviewing pull requests to ensure code quality, proper error handling, adequate test coverage mapped to acceptance criteria, and alignment with architecture boundaries and review standards.

Use when reviewing Danish copy for anglicisms, technical jargon, defensive tone, vague formulations, English words, and overly formal language. Scans uncommitted files by default or specific files with --file flag.

Review Odoo code for correctness, security, performance, and Odoo 18 standards. Use when reviewing Odoo modules, diffs, or pull requests; produce a scored report with weighted criteria.

Review all codebase documentation files under `.claude/` and per-crate `CLAUDE.md` files, and fix any that have drifted from the actual code. This is a documentation-only task -- do not modify any source code.

>

Active orchestrator for multi-agent flight execution. Drives the full leg cycle (design, implement, review, commit) using three separate Claude instances.

Review a single file or all files in a folder for data inconsistencies, reference errors, typos, and unclear terminology using parallel sub-agents

Develop zgrok tunnel service following project conventions, issue specs, and Rust best practices. Use when implementing features, fixing bugs, or reviewing code in this repository.

Orchestrate the full PRD lifecycle: catchup → plan-tasks → work → review → rework loop → blind review → doubt review → done.

Git workflow and commit conventions. Use when committing code, creating branches, or making pull requests.

REST API design patterns including resource naming, status codes, pagination, filtering, error responses, versioning, and rate limiting for production APIs.

Owns the full FastAPI stack for web-cv-converter — routes, services, Pydantic schemas, Supabase migrations, Auth0 configuration. Performs OWASP self-review before every handoff.

Workflow полного health check проекта. Architecture → Security → Quality → Report → (Fix). Use before major release or onboarding.

Design a task document for a feature or bug fix through deep research and multi-round design review, and run task lifecycle workflows. Use when planning implementation work in this repository, running pre-edit `task implement` planning from a task worktree, running post-implementation `task checklist` review, resolving task docs, or purging completed task worktrees. Enforce background-doc research, codebase impact analysis, explicit first-principles/long-term/original-fit proposal lenses with tradeoffs, two formal review rounds with user feedback, strict RFC escalation for oversized scope, explicit user approval before writing docs/tasks files, and explicit developer approval before implementation edits.

Code Quality Audit

Translate or review Typst documentation TOML in this repository using the local helper, canonical repo rules, and git-based patch review.

Use when producing a read-only CoordExp audit of code, configs, specs, artifacts, docs, progress notes, or OpenSpec changes for correctness, reproducibility, pipeline, and eval-validity risks.

Use when the user needs to design, implement, audit, or govern Storybook stories for frontend components, design systems, page states, interaction tests, accessibility checks, visual baselines, or component-driven UI workflows.

Codex entry skill for request-traceable implementation planning. Use when a request needs one or more executable plan artifacts under `./plans` after resolving blocking product policy, UX, contract, schema, validation, state, permission, and any upstream UI-direction ambiguity handled by `brainstorm` or `design-discovery`, with a controller-facing `plan.md` written in plain Korean that keeps the user's request items visible, groups work by concrete boundaries, exposes public contracts before execution order, and links per-phase technical detail files for later `plan-review` and `plan-materialize`, plus registry-backed review wiki core/pattern guidance.

Coordinates planning, implementation, review, de-sloppification, and documentation for PythonExerciseGeneratorAndDistributor changes against ACTION_PLAN.md.

Review public APIs, traits, structs, and module boundaries against the guiding

Run safety-first repository audits for OpenClaw Bakery with evidence-based findings and low-risk remediation. Use when the user asks to audit, clean up, review operational health, or align docs/config/paths without risky architectural rewrites.

Validates story implementations through testing, code review, and quality gate assessment. Uses testing skill for execution, checks standards compliance, and creates quality gate decisions (PASS/CONCERNS/FAIL/WAIVED).

Swift coding conventions and best practices for modern Swift development. Use when writing, reviewing, or refactoring Swift code to ensure consistency with naming conventions, access control, async/await patterns, and SwiftUI/framework best practices.

Review ADRs to check they follow testing principles and parent PDR constraints. Use when reviewing ADRs or architecture decisions.

Evaluates green bonds, sustainability-linked bonds, and social bonds with KPI selection, step-up mechanics, and framework assessment. Use when structuring ESG-linked debt, analyzing sustainability frameworks, or evaluating green bond eligibility.

Analyzes code comments for accuracy, completeness, and long-term maintainability. Detects comment rot and misleading documentation. Use after adding or modifying code comments.

Use when the user wants to convert Markdown to DOCX, make a Microsoft Word version of a Markdown file, style Word output with a reference template, fix DOCX callouts, or customize the bundled Word template for notes, reports, and review docs.

Comprehensive TLA+ specification review with checklist and automated validation

Review all prototypes at once for cross-prototype consistency, coverage gaps, ADR follow-through, and scope discipline. Use for a full audit of all prototypes.

>-

Draft, review, and update Software Design Descriptions using an IEEE 1016-2009-inspired structure with explicit architecture/views/elements formalization and output structure validation. Use this whenever a user asks to write an SDD, assess SDD quality/completeness, align design docs to IEEE 1016 concepts, map PRD requirements to design, produce architecture/interface/data design sections, generate remediation-oriented gap reports, perform SDD review-only gap analysis, check whether an SDD has drifted from the codebase, or update an SDD after architecture changes.