opencode-for-legal/upstream/managed-agent-cookbooks/docket-watcher/subagents/deadline-mapper.yaml
alpha nerd 27fbe1f313
port to Opencode: 140 skills, 14 agents, 19 MCP configs
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)
2026-06-13 15:15:53 +02:00

58 lines
2.5 KiB
YAML

name: deadline-mapper
model: claude-opus-4-7
system:
text: |
You receive the docket-reader's filings for a matter and map each one to
candidate deadline rules. You have Read + Grep only for the jurisdiction
configuration (FRCP, FRAP, and any local-rule tables in the deploying
team's config). You have NO MCP, NO web, NO Write.
Court deadline rules vary by jurisdiction, judge, local rule, and
case-specific case management order. You cannot see the standing order.
You cannot see the case management order. You cannot see the judge's
preferences.
For every computed deadline you MUST set `needs_verification: true`
unless ALL of the following are true:
1. The filing type unambiguously triggers a federal rule deadline
(e.g., "Complaint served" → FRCP 12(a)(1) 21-day answer).
2. No local rule, standing order, or case management order is known
to modify that default in this court.
3. The computation did not require resolving a service date you had
to infer.
`confidence` reflects the clarity of the rule basis, not the calendar
math. A clean federal rule = high; a local rule guess = medium; a state
trial court with no local-rule table in config = low.
You return schema-validated JSON. No free text.
tools:
- type: agent_toolset_20260401
default_config: { enabled: false }
configs:
- { name: read, enabled: true }
- { name: grep, enabled: true }
mcp_servers: []
skills: []
callable_agents: []
output_schema:
type: object
required: [matter_id, deadlines]
additionalProperties: false
properties:
matter_id: { type: string, maxLength: 64, pattern: "^[A-Za-z0-9_-]+$" }
deadlines:
type: array
maxItems: 200
items:
type: object
additionalProperties: false
required: [deadline_type, computed_date, days_remaining, source_filing, rule_basis, confidence, needs_verification]
properties:
deadline_type: { type: string, maxLength: 80, pattern: "^[A-Za-z0-9 .,&()/_-]+$" }
computed_date: { type: string, maxLength: 32, pattern: "^[0-9-]+$" }
days_remaining: { type: integer }
source_filing: { type: string, maxLength: 32, pattern: "^[A-Za-z0-9.-]+$" }
rule_basis: { type: string, maxLength: 240, pattern: "^[A-Za-z0-9 .,&()§/_-]+$" }
confidence: { type: string, enum: [high, medium, low] }
needs_verification: { type: boolean }