alpha nerd
27fbe1f313
Port claude-for-legal plugin collection to Opencode skills format. Changes: - 140 skills ported to opencode-for-legal/skills/ (namespaced naming) - 14 agents converted to Opencode subagent format - 5 managed-agent cookbooks flattened to single agents - 19 MCP servers converted to opencode.json format - 11 practice-profile templates ported (CLAUDE.md → PROFILE.md) - Remote skill catalog (index.json) for Opencode URL discovery - Setup wizard skill for first-time configuration License compliance: - Original source preserved in upstream/ per Apache 2.0 §4(b) - NOTICE.md documents derivative work and upstream attribution - LICENSE copied into port directory - README rewritten with port disclaimer and trademark notice Platform updates: - Removed all Claude Code/Cowork product-specific references - Config paths updated to ~/.config/opencode/opencode-for-legal/ - Command syntax: /plugin:skill → opencode auto-loading - Agent frontmatter converted (tools: → mode: subagent)
51 lines
2.1 KiB
YAML
51 lines
2.1 KiB
YAML
# Docket Watcher — managed-agent cookbook
|
|
#
|
|
# Same agent as the `docket-watcher` agent in the litigation-legal Claude Code
|
|
# plugin. This manifest resolves the canonical system prompt and skills against
|
|
# the plugin on disk so there is one source of truth.
|
|
|
|
name: docket-watcher
|
|
model: claude-opus-4-7
|
|
|
|
system:
|
|
file: ../../litigation-legal/agents/docket-watcher.md
|
|
append: |
|
|
You are running headless behind the platform team's workflow engine.
|
|
Produce files in ./out/; do not assume an interactive session. Prepend the
|
|
work-product header from the deploying team's litigation-legal CLAUDE.md.
|
|
|
|
Your output is a lead, not a legal conclusion. Computed deadlines are
|
|
leads, not calendar entries. Court deadline rules vary by jurisdiction,
|
|
court, judge, and local rule, and are routinely modified by standing
|
|
order or case-specific case management order. Missing a court deadline
|
|
has malpractice consequences. A licensed attorney verifies every computed
|
|
deadline against the court's actual rules and any case-specific orders
|
|
before it is docketed.
|
|
|
|
Filing classifications are heuristic. A filing the agent misclassifies
|
|
can produce a wrong deadline rule. The docketing attorney reads the
|
|
filing. Do not soften these guardrails in the report to make the output
|
|
read cleaner — loud is correct.
|
|
|
|
tools:
|
|
# Orchestrator is scoped to local-only tools; MCP and web_fetch are held by
|
|
# the subagent leaves (see callable_agents).
|
|
- type: agent_toolset_20260401
|
|
default_config: { enabled: false }
|
|
configs:
|
|
- { name: read, enabled: true }
|
|
- { name: grep, enabled: true }
|
|
- { name: glob, enabled: true }
|
|
|
|
mcp_servers:
|
|
- { type: url, name: trellis, url: "${TRELLIS_MCP_URL}" }
|
|
- { type: url, name: courtlistener, url: "${COURTLISTENER_MCP_URL}" }
|
|
- { type: url, name: gdrive, url: "${GDRIVE_MCP_URL}" }
|
|
|
|
skills:
|
|
- { from_plugin: ../../litigation-legal }
|
|
|
|
callable_agents:
|
|
- { manifest: ./subagents/docket-reader.yaml }
|
|
- { manifest: ./subagents/deadline-mapper.yaml }
|
|
- { manifest: ./subagents/tracker-writer.yaml } # only leaf with Write
|