warpdotdev/council

모델이 다양한 하위 에이전트 위원회를 구성하여 동일한 문제를 여러 관점에서 조사하고, 결과를 비교한 후 최종 권장 사항을 도출합니다. 사용자가 위원회, 제2의 의견, 여러 에이전트/모델을 통한 질문 평가, 병렬 조사, 레드팀/블루팀 비교, 또는 경쟁 기술 접근 방식 간의 결정 도움을 요청할 때 이 스킬을 사용하세요.

council란 무엇인가요?

이 스킬은 다양한 AI 모델을 기반으로 한 하위 에이전트 위원회를 구성하여 동일한 문제를 여러 관점에서 분석하고, 결과를 종합하여 최종 권장 사항을 제시합니다. 사용자가 위원회, 제2의 의견, 여러 에이전트/모델 평가, 병렬 조사, 레드팀/블루팀 비교, 또는 기술적 접근 방식 선택에 도움이 필요할 때 유용합니다. 이 스킬은 Claude Code, Cursor, Codex 등 다양한 AI 에이전트 플랫폼에서 사용 가능하며, 설정된 환경 변수를 통해 모델 구성을 유연하게 조정할 수 있습니다. 워크플로우는 각 관점의 전문가 역할을 가진 여러 하위 에이전트가 독립적으로 문제를 조사하고, 그 결과를 비교 분석하여 하나의 통합된 최종 권고안을 생성함으로써, 단일 모델의 편향을 줄이고 더 포괄적인 통찰력을 제공합니다.

지원 대상~Claude Code~Codex CLI~Cursor

Part ofAgent Workflows

npx skills add https://github.com/warpdotdev/common-skills/tree/main/skills/council

Installed? Explore more 생산성 & 협업 skills: steipete/gemini, steipete/gh-issues, steipete/skill-creator · View all 6 →

원본 보기→모든 스킬 둘러보기

즐겨 사용하는 AI에게 물어보기

이 에이전트 스킬이 미리 로드된 새 채팅을 엽니다.

ChatGPT Claude Gemini Grok Perplexity DeepSeek

문서

council은(는) 무엇을 하나요?

Individual skills in this repo

This repo contains 16 individual skills — each has its own dedicated page.

warpdotdev/brandalf

Guides creation, revision, and review of Warp- or Oz-branded assets. Use when working on launch pages, docs, HTML/CSS components, UI mockups, prompts, social assets, copy, presentations, or any other branded deliverable that should look and sound unmistakably Warp or Oz.

warpdotdev/check-impl-against-spec

Compare a pull request's implementation against spec context in spec_context.md and feed any material mismatches into review.json. Use during PR review when approved or repository spec context is available.

warpdotdev/create-pr

Create a pull request in the warp repository for the current branch. Use when the user mentions opening a PR, creating a pull request, submitting changes for review, or preparing code for merge.

warpdotdev/diagnose-ci-failures

Diagnose CI failures for a PR using the GitHub CLI, extract error logs, and generate a plan to fix them. Use when the user asks to check CI status, pull CI issues, triage test failures, or investigate PR build failures.

warpdotdev/fix-errors

Fix compilation errors, linting issues, and test failures in the warp Rust codebase. Covers presubmit checks, WASM-specific errors, and running specific tests. Use when the user hits build errors, clippy or fmt failures, test failures, or needs to run or interpret presubmit before a PR.

warpdotdev/implement-specs

Implement an approved feature from PRODUCT.md and TECH.md, keeping specs and code aligned in the same PR as implementation evolves. Use after the product and tech specs are approved and the next step is building the feature.

warpdotdev/pr-walkthrough

Generate a static interactive D3 walkthrough of a pull request. Use when the user wants a zoomable PR map, graph/canvas PR orientation, or alternate visualization of PR system components, data flow, code dependencies, and user actions.

warpdotdev/reproduce-bug-report

Launch Oz cloud agents with computer use to reproduce UI-focused bug reports, capture visual evidence, and report reproduction findings. Use when investigating a specific interactive or visual bug from an issue, ticket, support report, or prompt.

warpdotdev/resolve-merge-conflicts

Resolve Git merge conflicts by extracting only unresolved paths, conflict hunks, and compact diffs instead of loading whole files into context. Use when a merge, rebase, cherry-pick, or stash pop stops on conflicts, when `git status` shows unmerged paths, or when files contain conflict markers.

warpdotdev/respond-to-pr-comments-in-blocklist

Walk users through PR review comments, fetching and displaying them first when needed, collect per-comment response decisions, apply requested fixes, and preview GitHub replies and resolutions before posting. Use when responding to PR review comments on the current branch.

warpdotdev/review-pr

Review a pull request diff and write structured feedback to review.json for the workflow to publish. Use when reviewing a checked-out PR from local artifacts like pr_diff.txt and pr_description.txt and producing machine-readable review output instead of posting directly to GitHub.

warpdotdev/spec-driven-implementation

Drive a spec-first workflow for substantial features by writing PRODUCT.md before implementation, writing TECH.md when warranted, and keeping both specs updated as implementation evolves. Use when starting a significant feature, planning agent-driven implementation, or when the user wants product and tech specs checked into source control.

warpdotdev/update-skill

Create or update skills by generating, editing, or refining SKILL.md files in this repository. Use when authoring new skills or revising the structure, frontmatter, or guidance for existing ones.

warpdotdev/validate-changes-match-specs

Validate that a branch or pull request implementation matches introduced product, technical, security, and related specs. Use when reviewing or finishing a spec-driven change and resolving mismatches between checked-in specs and implementation.

warpdotdev/write-product-spec

Write a PRODUCT.md spec for a significant user-facing feature in Warp, focused on detailed behavior and validation. Use when the user asks for a product spec, desired behavior doc, or PRD, wants to define feature behavior before implementation, or when the feature is substantial or behaviorally ambiguous enough that a written spec would improve implementation or review.

warpdotdev/write-tech-spec

Write a TECH.md spec for a significant Warp feature after researching the current codebase and implementation constraints. Use when the user asks for a technical spec, implementation plan, or architecture doc tied to a product spec.