Planning & Project Management for Claude Code

> Open a new internal investigation matter — runs intake, generates the sources checklist, and creates the persistent investigation log. Use when a complaint or allegation comes in and the attorney needs to stand up a privileged investigation workspace.

> Draft an audience-specific summary from the privileged investigation memo — HR, leadership, or outside counsel versions. Use when an investigation memo needs to be communicated to an audience that should not see the full privileged work product.

> 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.

> Fast "is this a problem?" answer for the quick Slack question — pattern-matches against your calibration. Use when the user says "is this a problem", "quick question", "can we do X", "do I need legal review for", "sanity check", or pastes a PM's question that needs a same-minute fine / needs a look / hold call.

> Full launch review against your framework and risk calibration. Use when the user says "review this launch", "legal review for [feature]", "can we ship this", "what are the legal issues with [product]", or references a launch tracker ticket or PRD that needs a category-by-category review memo.

> 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.

> Check open leaves for deadline alerts and required decisions. Surfaces only the leaves that require an action and explains why — not a status board. Use weekly, or whenever the attorney needs to know which leaves have upcoming designation, certification, or exhaustion deadlines.

> 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

> Add a new leave to the leave register with the minimum information needed to start tracking deadlines. Use when an employee goes on leave and you want the tracker to watch designation, certification, and exhaustion clocks from day one.

Deep briefing on one matter — current posture, what's changed, next deadline, open questions, and a risk re-assessment check, ready before a GC update or outside counsel call. Use when the user says "brief me on [matter]", "where are we on [matter]", or needs a read on a specific matter.

Close a matter — capture outcome, final exposure, and lessons, then archive it out of the active portfolio without deleting the record. Use when the user wants to close a matter, says "[matter] is done", or needs to record a settlement, dismissal, judgment, withdrawal, or consolidation outcome.

Intake a new matter — uniform questions covering identification, conflicts, source, risk triage, materiality, outside counsel, owners, legal hold, and key dates; writes matter.md and history.md and appends a structured row to _log.yaml. Use when the user says "new matter", "intake this matter", or wants to bring a new matter into the portfolio.

Append a dated event to a matter's history file and refresh the log row — captures new developments, status changes, risk re-assessments, deadline shifts, and settlement authority changes. Use when the user wants to log an update on a matter, note a development, or record a status change against the portfolio.

> Manage matter workspaces — new, list, switch, close, or detach (practice-level). Use when a multi-client practitioner needs to create a matter, switch the active matter, list matters, archive a matter, or detach to practice-level context, or when another skill needs to know which matter it's working in.

> Reference: fast triage of inbound NDAs into GREEN / YELLOW / RED so the team only spends lawyer time on the ones that need it. Built for sales and BD to self-serve before pinging legal. Loaded by /commercial-legal:review when an NDA is detected.

> 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.

Diff a specific regulatory change against the indexed policy library. Use when a reg has changed and you need to know which policies it touches and what the gap is, when the user says "diff this reg against our policies", "which policy does this affect", or "gap analysis", or when reg-feed-watcher hands off a material item.

> Draft an employment policy with state supplements where law differs across the jurisdictional footprint. Use when the user says "draft a [topic] policy", "we need a policy on", "update our [topic] policy", or names a policy gap.

> Keep the privacy policy current with practice. Two modes: weekly sweep of saved PIAs, DPA reviews, and triage results to find policy drift; or direct query for a proposed new practice. Use when the user asks "does our policy cover this", "we want to start doing X — does the policy need updating", "run the policy monitor", "policy sweep", or wants to find where the privacy policy no longer matches what the team actually does.

Produce a proposed marked-up policy redraft that closes a gap found by /regulatory-legal:gaps or /regulatory-legal:policy-diff. A first draft for internal review — not for direct application to approved policy documents. Use when the user says "redraft the policy", "draft the policy fix", "mark up the policy", or when gap-surfacer hands off a gap for drafting.

> Draft a firm AI usage policy from published model policies, adapted to your practice profile — a research-and-synthesis tool whose output is a draft for attorney review and adoption, not a finished policy. Use when user says "draft an AI policy", "we need an AI policy", "build an AI usage policy", "our firm needs a GenAI policy", or similar requests to generate a first-cut internal AI policy.

Roll up the portfolio from _log.yaml — risk distribution, upcoming deadlines, stale matters, materiality totals, stage distribution, and flagged anomalies. Use when the user asks "where do we stand", "how many open matters", or wants a portfolio rollup or status across all active matters.

First-pass privilege log review — make the obvious privilege calls and flag the hard ones for attorney review without making close calls. Use when the user says "review the privilege log", "priv log", "check privilege on these docs", or has a log to QA before production.

> Diff a new AI regulation or guidance against your current governance posture — surfaces gaps, priorities, and a remediation plan with owners and deadlines. Use when an AI regulation moves (or you learn about one you missed), or when user says "new reg just dropped", "does [regulation] affect us", "gap analysis for EU AI Act", "compliance check against [AI law or guidance]", or pastes regulatory text.

> Show contracts with cancel-by deadlines coming up and warn before notice windows close, working from a maintained renewal register. Use when the user asks "what's renewing soon", "what renewals are due", "did we miss a cancellation window", "add this to the renewal tracker", or on a scheduled basis. Receives handoffs from saas-msa-review.

> 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.

> Review and approve (or reject) pending playbook update proposals from the playbook-monitor agent and apply approved changes to the practice profile. Use when the playbook-monitor agent has surfaced proposals, when the user says "review playbook proposals", "what playbook updates are pending", or wants to step through deviation-driven playbook changes.

> End-of-semester case handoff memos — the mirror of /ramp. Produces per-case transition memos and a cohort summary so the departing cohort hands work to the incoming cohort cleanly. Reads deadlines, client-comms, and case history. Use when the professor or departing students need to wrap up the semester, build transition memos, or offboard a graduating/withdrawing student.

> Translates a contract review into a summary the business stakeholder will actually read. Not a legal memo — a two-minute answer to "can I sign this and what do I need to know." Use when user says "summarize for the business", "write this up for [stakeholder]", "explain this to procurement", "non-legal summary", or when a review is done and needs to go to someone outside legal.

> Build or update a long-term bar prep (or exam prep) study plan — phases, subjects weighted by weakness, daily session schedule, adaptive to session history in study-plan.yaml. Use when the user says "build a study plan", "plan my bar prep", "schedule my studying", or "how should I study for [X]".

Triage a subpoena served on the company — classify it, analyze scope/burden/privilege, cross-check the portfolio, and produce an objections framework, compliance plan, and deadline calendar. Use when the user says "we got a subpoena", "served with a subpoena", or shares a subpoena, CID, or third-party document request to evaluate.

> Professor's review queue — student output waits here for professor approval before going to clients or courts. Only active if "formal review queue" supervision style was chosen at setup; otherwise dormant. Use when the professor wants to see what's waiting for review, approve, edit-then-approve, or return an item.

> Termination review — high-risk flag detection, severance + release, and final pay timing by jurisdiction. Jurisdiction-specific rules and release consideration periods are researched per review, not stored. Use when the user says "reviewing a termination", "can we fire this person", "term review", or describes a termination scenario.

> Classify a proposed AI use case against your registry — approved, conditional, or not approved — and produce required conditions and next steps. Flags cross-plugin handoffs to privacy or product counsel. Use when user says "triage this use case", "can we use AI for X", "is this approved", "what do we need to do to use AI for X".

> Reference: review of an inbound vendor agreement against the team playbook in `~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md`. Flags deviations, assesses risk, generates specific redline language, and routes to the right approver. Loaded by /commercial-legal:review when a vendor MSA, services agreement, or similar is detected.

> Classify a proposed worker engagement — employee, IC, temp, or vendor — by running the applicable jurisdiction tests and flagging misclassification gaps between the intended arrangement and what the facts actually support. Prospective use only. Use when someone says "we want to bring on a contractor", "is this a vendor or a temp", "how should we classify this person", or describes a proposed working arrangement.

> Draft a unanimous written consent of the board or a committee in house format, with precedent search from the consents repository. Handles multi-resolution consents, director conflict flags, state-law notice requirements, and signatory tracking, with a built-in scope warning for major one-off actions. Use when user says "written consent", "unanimous consent", "board consent", "consent in lieu", "UWC", or describes an action needing board approval without a meeting.

| PostgreSQL 核心 committer Andres Freund 的思维框架与表达方式。基于 6 个调研维度（著作、对话、表达 DNA、他者视角、决策、时间线） 共 2957 行 / 200 KB 一手资料的深度调研，提炼 6 个核心心智模型、10 条决策启发式和完整的表达 DNA。 用途：作为思维顾问，用 Andres Freund 的视角分析 PG 性能/扩展性/AIO/构建现代化等"测量驱动+地基重写"场景， 与 Tom Lane Skill 形成对比视角（一个偏"标准+历史"，一个偏"现代工程+测量"）。 当用户提到「用 Andres 的视角」「andres 会怎么看」「Andres Freund 模式」「AIO 推动」「Meson 切换」「测量驱动」 「I think / I'm unconvinced」「Greetings, Andres Freund」「PG 性能决策」「地基重写」时使用。 即使用户只是说「帮我用 PG 性能导向 committer 的角度想想」「如果 Andres 会怎么做」 「切换到测量驱动模式」「和 Tom Lane 观点对比」也应触发

| digoal/德哥的思维框架与表达方式。基于本地 digoal/blog 长文、ASK/访谈、 技术课程、公开履历、社区活动页和近年 AI skill 行动记录的调研， 提炼5个核心心智模型、8条决策启发式和表达DNA。 Use when the user explicitly asks for 德哥/digoal perspective, judgment, advice, analysis, or expression style, including requests such as 「用德哥的视角」「digoal会怎么看」「按德哥的思路拆一下」 「德哥会怎么写」「用德哥风格改写」「digoal perspective」 or 「切换到德哥」. Apply it to database practice, technical communication, open-source ecosystems, AI skillization, product opportunities, career learning, and cross-domain judgment.

基于用户提供的企业名、企业简介、公司网站、产品信息、财报或访谈材料，搜索当前公开资料并生成企业画像、未来规划与建议书。Use when the user asks for 企业未来规划、公司战略建议书、企业画像、行业/赛道/场景分析、商业机会挖掘、客户付费痛点、产品原型、MVP、团队组建、变现路径、转型增长方案, and wants a source-backed Chinese Markdown report saved under the current project's markdown directory.