Loading...
Loading...
Found 31 Skills
Annie Duke's Decision Quality framework applied to a business decision. Spawns a team of specialist agents — Resulting Auditor, Calibrator, Pre-Mortem Analyst, Quit Strategist, Process Architect — who each apply a distinct lens from Duke's framework to evaluate whether a decision is sound regardless of outcome. The lead synthesizes into a stacking analysis: which biases are operating, which process flaws exist, and the honest Duke verdict. Use when the user says "duke this", "is this a good bet", "should I quit", "evaluate this decision", or faces any high-stakes choice under uncertainty and wants rigorous decision-process analysis. Works as a standalone analysis or after /office-hours.
문제를 분석하여 Agent Teams를 자동 구성하고, 4가지 조율 패턴(distribute/monitor/discourse/sequence) 중 최적 패턴으로 협업한다. "/teams {문제 설명}"으로 호출한다.
Fix findings from autonomous-tests. Args: all | critical | high | vulnerability | file:<path> (default: interactive selection). Example: /autonomous-fixes vulnerability
Issue creation workflow for Agent Teams Lite following the issue-first enforcement system. Trigger: When creating a GitHub issue, reporting a bug, or requesting a feature.
[BETA] Execute work plans with external delegate support. Same as ce:work but includes experimental Codex delegation mode for token-conserving code implementation.
FORGE + Agent Teams — Exploits Agent Teams for true parallel execution of FORGE agents. 3 patterns: pipeline (full pipeline with parallel stories), party (multi-agent debate), build (parallel story development). Requires CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1. Usage: /forge-team pipeline "objective" | /forge-team party "topic" | /forge-team build [STORY-IDs]
楽勝で流す。Agent Teamsで完全自走、寝てる間にゴール。Use when user mentions '/breezing', agent teams, team execution, full auto completion, multi-agent workflow, 'チームで完走', 'チームで全部'. Do NOT load for: single tasks, reviews, setup, or /work (direct implementation).