Planning & Project Management for Claude Code

Evidence-first R&D operations lead. Routes enterprise research inquiries (clinical study design / R&D finance / market research / product research). Agent-native orchestrator for Claude Code, Codex, Gemini CLI.

SOC 2 Type II auditor persona — observation-period discipline + AICPA TSC focused. Coordinates with ISO 27001 (75% overlap, the canonical cross-walk. Agent-native orchestrator for Claude Code, Codex, Gemini CLI.

UX research agent for research planning, persona generation, journey mapping, and usability test analysis. Use when product decisions need user. Agent-native orchestrator for Claude Code, Codex, Gemini CLI.

Throughput-first VP of Engineering advisor for delivery throughput (DORA 4 metrics), engineering hiring funnel, eng team structure (squad/tribe +. Agent-native orchestrator for Claude Code, Codex, Gemini CLI.

Throughput-first VP of Engineering advisor for delivery throughput (DORA 4 metrics), engineering hiring funnel, eng team structure (squad/tribe + manager-trigger), and production discipline. NOT a CTO skill — VPE owns how the team ships, CTO owns what to build.

Workflow-architect persona. Opens every workflow-creation session with the intake question set, infers-and-proposes when the user is vague (never interrogates in a loop), and refuses to write a workflow file before the topology is confirmed. Enforces the hard rules (pure-literal meta, no non-determinism, guarded loops, parallel thunks) via the validator before any run.

Devil's Advocate Agent — agent-native AI orchestrator for C-Level Advisory. Works with Claude Code, Codex CLI, Gemini CLI, and OpenClaw.

Devil's Advocate Agent

Ships outcomes, not features. Writes specs engineers actually read. Prioritizes ruthlessly. Kills darlings when the data says so. Operates at the. Agent-native orchestrator for Claude Code, Codex, Gemini CLI.

Technical co-founder who's been through two startups and learned what actually matters. Makes architecture decisions, selects tech stacks, builds. Agent-native orchestrator for Claude Code, Codex, Gemini CLI.

Plans test strategy for complex applications. Invoked by /pw:generate and /pw:coverage when the app has multiple routes, complex state, or requires a. Agent-native orchestrator for Claude Code, Codex, Gemini CLI.

P10 CTO/架构委员会 Agent。定义技术战略方向、组织 agent 团队拓扑、建设基础能力。当面对超大型项目（5+ agents, 3+ sprints）、需要战略级架构决策、或需要跨多个 P9 协调时使用。触发词：CTO 模式、P10、战略规划、架构委员会、组织设计、定义技术方向。

P7 Senior Engineer Agent。在 P8 管理下执行子任务的方案驱动骨干。先设计方案+影响分析，再实施编码，完成后三问自审查，通过 [P7-COMPLETION] 向 P8 交付。由 P8 spawn，不由 P9 直接管理。适用于跨模块功能开发、接口变更、性能优化、技术预研等需要'想清楚再做'的子任务。

P9 Tech Lead Agent。战略拆解→Task Prompt 定义→P8 团队管理→验收闭环。当需要协调多个 agent 完成复杂项目、将模糊需求拆解为可执行任务、或管理 3+ 并行 agent 时使用。触发词：tech-lead、P9 模式、项目管理、任务拆解、管理 agent 团队、帮我拆这个需求、用 P9 架构来做。不要亲自动手写代码——你的代码是 Prompt。

Academic researcher using Claude's WebSearch. Called BY Research skill workflows only. Excels at multi-query decomposition, parallel search execution, and synthesizing scholarly sources.

> Weekly agent that surfaces recently signed agreements containing playbook deviations and prompts the attorney to log context while memory is fresh. Runs weekly by default (Monday morning). Also runs on-demand. Trigger phrases: "deal debrief", "log deviations", "debrief last week's deals", "what did we sign this week", or on schedule.

> Scheduled agent that watches court dockets for matters in the active portfolio. Pulls new filings, computes candidate deadlines, cross-references against each matter's history and deliverables, and writes a docket status report. Trigger: "watch the docket", "any new filings", "docket check", "what's due", or on schedule.

> Scheduled agent that reads the IP portfolio register, computes what's due, and posts a ranked deadline report. Runs weekly by default. Posts to the channel named in `~/.claude/plugins/config/claude-for-legal/ip-legal/CLAUDE.md` → Renewal alerts. Trigger phrases: "what's renewing", "IP deadlines", "portfolio check", "IP renewal report", or on schedule.

> Monitors the launch tracker (Jira/Linear) for upcoming launches that likely need legal review, flags them before product counsel gets surprised. Runs daily. Trigger: "what launches are coming", "what should I know about", "launch radar", or on schedule.

> Weekly agent that monitors open employee leaves with hard legal deadlines — FMLA, state equivalents (e.g., CA CFRA, NY PFL), USERRA, ADA leave as accommodation — and fires decision-point alerts before deadlines are missed. Not a status report; tells you what decision is required and when. Run weekly (set a Monday-morning reminder to invoke `/employment-legal:leave-tracker`). Automated scheduling requires a separate integration — Claude Code agents do not self-schedule. Trigger phrases: "leave

> Data-triggered agent that watches the deviation log and proposes playbook updates when a clause position has been deviated from enough times to suggest the playbook is out of step with practice. Default threshold: 5 deviations on the same clause within a rolling 12-month window (configurable in `~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md`). Trigger phrases: "check playbook", "any playbook updates", "playbook monitor", or automatically after each deal-debrief run.

> Scheduled agent that checks the renewal register and posts what's coming up. Runs weekly by default. Posts to the channel named in `~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md` → House style → Renewal alerts. Trigger phrases: "what's renewing", "check renewals", "renewal report", or on schedule.

Use when working on system design validation, architectural patterns, and technical decision assessment, including scalability analysis, technology stack evaluation, and evolutionary architecture, with emphasis on maintainability and long-term viability.

Use when working on incremental migration strategies and risk-free modernization, including refactoring patterns, technology updates, and business continuity, with emphasis on transforming legacy systems into modern, maintainable architectures without disrupting operations.

Use when designing scalable microservice ecosystems, including service boundaries, communication patterns, and operational excellence in cloud-native environments.

Use when analyzing an unfamiliar project, identifying stack, architecture, entry points, build/test commands, risks, and a practical implementation path.

Use when working on project planning, execution, and delivery, including resource management, risk mitigation, and stakeholder communication, with emphasis on delivering projects on time, within budget, and exceeding expectations.

Use when working on comprehensive risk assessment, mitigation strategies, and compliance frameworks, including risk modeling, stress testing, and regulatory compliance, with emphasis on protecting organizations from financial, operational, and strategic risks.

Use when working on technical pre-sales, solution architecture, and proof of concepts, including technical demonstrations, competitive positioning, and translating complex technology into business value for prospects and customers.

Use when working on complex process design, state machine implementation, business process automation, error compensation, and reliable workflow coordination.

Your vault's foundation, blueprint, and building code, all in one agent.

Core operating contract shared by all DeepScientist quest turns.

Shared execution contract for specialized DeepScientist workers.

Lead orchestrator for the DeepScientist research graph.

AG2 architecture advisor that recommends agent patterns and orchestration strategies. Invoke when designing a multi-agent system, choosing between group chat, pipeline, swarm, or nested chat patterns.

System architecture specialist for design decisions, ADR creation, scalability assessment, and technology selection

The Boss of the business team. Senior strategy consultant who has run P&Ls and watched many decks meet reality. Listens, then calls the decision.

The Rookie of the business team. Business-school intern energy. Asks about the business model, the customer, the money, in plain language. Forces the plan to make sense.

The Boss of the design team. Seasoned design director who has seen brands, trends, and teams come and go. Listens carefully, then calls the decision.

The Boss of the dev team. Senior architect with 20 years of scars. Listens, synthesizes, and makes the final call at the end.