opencode-knowledge-work 0.0.0-stage → 0.1.1

package/content/legal/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/content/legal/README.md

@@ -0,0 +1,234 @@
+# Legal Productivity Plugin
+
+An AI-powered productivity plugin for in-house legal teams, primarily designed for [Cowork](https://claude.com/product/cowork), Anthropic's agentic desktop application — though it also works in Claude Code. Automates contract review, NDA triage, compliance workflows, legal briefings, and templated responses -- all configurable to your organization's specific playbook and risk tolerances.
+
+> **Disclaimer:** This plugin assists with legal workflows but does not provide legal advice. Always verify conclusions with qualified legal professionals. AI-generated analysis should be reviewed by licensed attorneys before being relied upon for legal decisions. The default playbook examples in this plugin reflect U.S. legal positions and jurisdictions (Delaware, New York, California). If you operate under different legal systems (EU, UK, Netherlands, Australia, etc.), you must customize the playbook in .claude/legal.local.md to reflect your jurisdiction's specific legal requirements, standard contract terms, and compliance obligations before relying on the plugin's analysis.
+
+## Target Personas
+
+- **Commercial Counsel** -- Contract negotiation, vendor management, deal support
+- **Product Counsel** -- Product reviews, terms of service, privacy policies, IP matters
+- **Privacy / Compliance** -- Data protection regulations, DPA reviews, data subject requests, regulatory monitoring
+- **Litigation Support** -- Discovery holds, document review prep, case briefings
+
+## Installation
+
+```
+claude plugin marketplace add anthropics/knowledge-work-plugins
+claude plugin install legal@knowledge-work-plugins
+```
+
+## Quick Start
+
+### 1. Install the plugin
+
+```
+claude plugin marketplace add anthropics/knowledge-work-plugins
+claude plugin install legal@knowledge-work-plugins
+```
+
+### 2. Configure your playbook
+
+Create a local settings file to define your organization's standard positions. This is where you encode your team's negotiation playbook, risk tolerances, and standard terms.
+
+Create a `legal.local.md` file where Claude can find it:
+
+- **Cowork**: Save it in any folder you've shared with Cowork (via the folder picker). The plugin finds it automatically.
+- **Claude Code**: Save it in your project's `.claude/` directory.
+
+```markdown
+# Legal Playbook Configuration
+
+## Contract Review Positions
+
+### Limitation of Liability
+- Standard position: Mutual cap at 12 months of fees paid/payable
+- Acceptable range: 6-24 months of fees
+- Escalation trigger: Uncapped liability, consequential damages inclusion
+
+### Indemnification
+- Standard position: Mutual indemnification for IP infringement and data breach
+- Acceptable: Indemnification limited to third-party claims only
+- Escalation trigger: Unilateral indemnification obligations, uncapped indemnification
+
+### IP Ownership
+- Standard position: Each party retains pre-existing IP; customer owns customer data
+- Escalation trigger: Broad IP assignment clauses, work-for-hire provisions for pre-existing IP
+
+### Data Protection
+- Standard position: Require DPA for any personal data processing
+- Requirements: Sub-processor notification, data deletion on termination, breach notification within 72 hours
+- Escalation trigger: No DPA offered, cross-border transfer without safeguards
+
+### Term and Termination
+- Standard position: Annual term with 30-day termination for convenience
+- Acceptable: Multi-year with termination for convenience after initial term
+- Escalation trigger: Auto-renewal without notice period, no termination for convenience
+
+### Governing Law
+- Preferred: [Your jurisdiction]
+- Acceptable: Major commercial jurisdictions (NY, DE, CA, England & Wales)
+- Escalation trigger: Non-standard jurisdictions, mandatory arbitration in unfavorable venue
+
+## NDA Defaults
+- Mutual obligations required
+- Term: 2-3 years standard, 5 years for trade secrets
+- Standard carveouts: independently developed, publicly available, rightfully received from third party
+- Residuals clause: acceptable if narrowly scoped
+
+## Response Templates
+Configure paths to your template files or define inline templates for common inquiries.
+```
+
+### 3. Connect your tools
+
+The plugin works best when connected to your existing tools via MCP. Pre-configured servers include Slack, Box, Egnyte, Atlassian, and Microsoft 365. See [CONNECTORS.md](CONNECTORS.md) for the full list of supported categories and options.
+
+## Commands
+
+### `/review-contract` -- Contract Review Against Playbook
+
+Review a contract against your organization's negotiation playbook. Flags deviations, generates redlines, and provides business impact analysis.
+
+```
+/review-contract
+```
+
+Accepts: file upload, URL, or pasted contract text. Will ask for context (your side, deadline, focus areas) and review clause-by-clause against your configured playbook.
+
+### `/triage-nda` -- NDA Pre-Screening
+
+Rapid triage of incoming NDAs against standard criteria. Categorizes as GREEN (standard approval), YELLOW (counsel review), or RED (significant issues).
+
+```
+/triage-nda
+```
+
+### `/vendor-check` -- Vendor Agreement Status
+
+Check the status of existing agreements with a vendor across your connected systems.
+
+```
+/vendor-check [vendor name]
+```
+
+Reports on existing NDAs, MSAs, DPAs, expiration dates, and key terms.
+
+### `/brief` -- Legal Team Briefing
+
+Generate contextual briefings for your legal work.
+
+```
+/brief daily          # Morning brief of legal-relevant items
+/brief topic [query]  # Research brief on a specific legal question
+/brief incident       # Rapid brief on a developing situation
+```
+
+### `/respond` -- Generate Templated Response
+
+Generate a response from your configured templates for common inquiry types.
+
+```
+/respond [inquiry-type]
+```
+
+Supported inquiry types include: data subject request, discovery hold, vendor question, NDA request, and custom categories you define.
+
+## Skills
+
+| Skill | Description |
+|-------|-------------|
+| `contract-review` | Playbook-based contract analysis, deviation classification, redline generation |
+| `nda-triage` | NDA screening criteria, classification rules, routing recommendations |
+| `compliance` | Privacy regulations (GDPR, CCPA), DPA review, data subject requests |
+| `canned-responses` | Template management, response categories, escalation triggers |
+| `legal-risk-assessment` | Risk severity framework, classification levels, escalation criteria |
+| `meeting-briefing` | Meeting prep methodology, context gathering, action item tracking |
+
+## Example Workflows
+
+### Contract Review
+
+1. Receive a vendor contract via email
+2. Run `/review-contract` and upload the document
+3. Provide context: "We are the customer, need to close by end of quarter, focus on data protection and liability"
+4. Receive clause-by-clause analysis with GREEN/YELLOW/RED flags
+5. Get specific redline language for YELLOW and RED items
+6. Share the analysis with your deal team
+
+### NDA Triage
+
+1. Sales team sends an NDA from a new prospect
+2. Run `/triage-nda` and paste or upload the NDA
+3. Get instant classification: GREEN (route for signature), YELLOW (specific issues to review), or RED (needs full counsel review)
+4. For GREEN NDAs, approve directly; for YELLOW/RED, address flagged issues
+
+### Daily Brief
+
+1. Start your morning with `/brief daily`
+2. Get a summary of overnight contract requests, compliance questions, upcoming deadlines, and calendar items needing legal prep
+3. Prioritize your day based on urgency and deadlines
+
+### Vendor Check
+
+1. Business team asks about a new engagement with an existing vendor
+2. Run `/vendor-check Acme Corp`
+3. See existing agreements, expiration dates, and key terms at a glance
+4. Know immediately whether you need a new NDA or can proceed under existing terms
+
+## MCP Integration
+
+> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](CONNECTORS.md).
+
+The plugin connects to your tools through MCP (Model Context Protocol) servers:
+
+| Category | Examples | Purpose |
+|----------|----------|---------|
+| Chat | Slack, Teams | Team requests, notifications, triage |
+| Cloud storage | Box, Egnyte | Playbooks, templates, precedents |
+| Office suite | Microsoft 365 | Email, calendar, documents |
+| Project tracker | Atlassian (Jira/Confluence) | Matter tracking, tasks |
+
+See [CONNECTORS.md](CONNECTORS.md) for the full list of supported integrations, including CLM, CRM, e-signature, and additional options.
+
+Configure connections in `.mcp.json`. The plugin gracefully degrades when tools are unavailable -- it will note gaps and suggest manual checks.
+
+## Customization
+
+### Playbook Configuration
+
+Your playbook is the heart of the contract review system. Define your positions in `legal.local.md`:
+
+- **Standard positions**: Your preferred contract terms
+- **Acceptable ranges**: What you can agree to without escalation
+- **Escalation triggers**: Terms that require senior review or outside counsel
+
+### Response Templates
+
+Define templates for common inquiries. Templates support variable substitution and include built-in escalation triggers for situations that should not use a templated response.
+
+### Risk Framework
+
+Customize the risk assessment matrix to match your organization's risk appetite and classification scheme.
+
+## File Structure
+
+```
+legal/
+├── .claude-plugin/plugin.json
+├── .mcp.json
+├── README.md
+├── commands/
+│   ├── review-contract.md
+│   ├── triage-nda.md
+│   ├── vendor-check.md
+│   ├── brief.md
+│   └── respond.md
+└── skills/
+    ├── contract-review/SKILL.md
+    ├── nda-triage/SKILL.md
+    ├── compliance/SKILL.md
+    ├── canned-responses/SKILL.md
+    ├── legal-risk-assessment/SKILL.md
+    └── meeting-briefing/SKILL.md
+```

package/content/legal/skills/legal-brief/SKILL.md

@@ -0,0 +1,208 @@
+---
+name: brief
+description: Generate contextual briefings for legal work — daily summary, topic research, or incident response. Use when starting your day and need a scan of legal-relevant items across email, calendar, and contracts, when researching a specific legal question across internal sources, or when a developing situation (data breach, litigation threat, regulatory inquiry) needs rapid context.
+argument-hint: "[daily | topic <query> | incident]"
+---
+
+# /brief -- Legal Team Briefing
+
+> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../CONNECTORS.md).
+
+Generate contextual briefings for legal work. Supports three modes: daily brief, topic brief, and incident brief.
+
+**Important**: This command assists with legal workflows but does not provide legal advice. Briefings should be reviewed by qualified legal professionals before being relied upon.
+
+## Invocation
+
+```
+/brief daily              # Morning brief of legal-relevant items
+/brief topic [query]      # Research brief on a specific legal question
+/brief incident [topic]   # Rapid brief on a developing situation
+```
+
+If no mode is specified, ask the user which type of brief they need.
+
+## Modes
+
+---
+
+### Daily Brief
+
+A morning summary of everything a legal team member needs to know to start their day.
+
+#### Sources to Scan
+
+Check each connected source for legal-relevant items:
+
+**Email (if connected):**
+- New contract requests or review requests
+- Compliance questions or reports
+- Responses from counterparties on active negotiations
+- Flagged or urgent items from the legal team inbox
+- External counsel communications
+- Regulatory or legal update newsletters
+
+**Calendar (if connected):**
+- Today's meetings that need legal prep (board meetings, deal reviews, vendor calls)
+- Upcoming deadlines this week (contract expirations, filing deadlines, response deadlines)
+- Recurring legal team syncs
+
+**Chat (if connected):**
+- Overnight messages in legal team channels
+- Direct messages requesting legal input
+- Mentions of legal-relevant topics (contract, compliance, privacy, NDA, terms)
+- Escalations or urgent requests
+
+**CLM (if connected):**
+- Contracts awaiting review or signature
+- Approaching expiration dates (next 30 days)
+- Newly executed agreements
+
+**CRM (if connected):**
+- Deals moving to stages that require legal involvement
+- New opportunities flagged for legal review
+
+#### Output Format
+
+```
+## Daily Legal Brief -- [Date]
+
+### Urgent / Action Required
+[Items needing immediate attention, sorted by urgency]
+
+### Contract Pipeline
+- **Awaiting Your Review**: [count and list]
+- **Pending Counterparty Response**: [count and list]
+- **Approaching Deadlines**: [items due this week]
+
+### New Requests
+[Contract review requests, NDA requests, compliance questions received since last brief]
+
+### Calendar Today
+[Meetings with legal relevance and what prep is needed]
+
+### Team Activity
+[Key messages or updates from legal team channels]
+
+### This Week's Deadlines
+[Upcoming deadlines and filing dates]
+
+### Sources Not Available
+[Any sources that were not connected or returned errors]
+```
+
+---
+
+### Topic Brief
+
+Research and brief on a specific legal question or topic across available sources.
+
+#### Workflow
+
+1. Accept the topic query from the user
+2. Search across connected sources:
+   - **Documents**: Internal memos, prior analyses, playbooks, precedent
+   - **Email**: Prior communications on the topic
+   - **Chat**: Team discussions about the topic
+   - **CLM**: Related contracts or clauses
+3. Synthesize findings into a structured brief
+
+#### Output Format
+
+```
+## Topic Brief: [Topic]
+
+### Summary
+[2-3 sentence executive summary of findings]
+
+### Background
+[Context and history from internal sources]
+
+### Current State
+[What the organization's current position or approach is, based on available documents]
+
+### Key Considerations
+[Important factors, risks, or open questions]
+
+### Internal Precedent
+[Prior decisions, memos, or positions found in internal sources]
+
+### Gaps
+[What information is missing or what sources were not available]
+
+### Recommended Next Steps
+[What the user should do with this information]
+```
+
+#### Important Notes
+- Topic briefs synthesize what is available in connected sources; they do not substitute for formal legal research
+- If the topic requires current legal authority or case law, recommend the user consult a legal research platform (Westlaw, Lexis, etc.) or outside counsel
+- Always note the limitations of the sources searched
+
+---
+
+### Incident Brief
+
+Rapid briefing for developing situations that require immediate legal attention (data breaches, litigation threats, regulatory inquiries, IP disputes, etc.).
+
+#### Workflow
+
+1. Accept the incident topic or description
+2. Rapidly scan all connected sources for relevant context:
+   - **Email**: Communications about the incident
+   - **Chat**: Real-time discussions and escalations
+   - **Documents**: Relevant policies, response plans, insurance coverage
+   - **Calendar**: Scheduled response meetings
+   - **CLM**: Affected contracts, indemnification provisions, insurance requirements
+3. Compile into an actionable incident brief
+
+#### Output Format
+
+```
+## Incident Brief: [Topic]
+**Prepared**: [timestamp]
+**Classification**: [severity assessment if determinable]
+
+### Situation Summary
+[What is known about the incident]
+
+### Timeline
+[Chronological summary of events based on available sources]
+
+### Immediate Legal Considerations
+[Regulatory notification requirements, preservation obligations, privilege concerns]
+
+### Relevant Agreements
+[Contracts, insurance policies, or other agreements that may be implicated]
+
+### Internal Response
+[What response activity has already occurred based on email/chat]
+
+### Key Contacts
+[Relevant internal and external contacts identified from sources]
+
+### Recommended Immediate Actions
+1. [Most urgent action]
+2. [Second priority]
+3. [etc.]
+
+### Information Gaps
+[What is not yet known and needs to be determined]
+
+### Sources Checked
+[What was searched and what was not available]
+```
+
+#### Important Notes for Incident Briefs
+- Speed matters. Produce the brief quickly with available information rather than waiting for complete information
+- Flag any litigation hold or preservation obligations immediately
+- Note privilege considerations (mark the brief as attorney-client privileged / work product if appropriate)
+- If the incident may involve a data breach, flag applicable notification deadlines (e.g., 72 hours for GDPR)
+- Recommend outside counsel engagement if the matter is significant
+
+## General Notes
+
+- If sources are unavailable, note the gaps prominently so the user knows what was not checked
+- For daily briefs, learn the user's preferences over time (what they find useful, what they want filtered out)
+- Briefs should be actionable: every item should have a clear next step or reason for inclusion
+- Keep briefs concise. Link to source materials rather than reproducing them in full