weekly-summary

slug	weekly-summary
name	Weekly Summary
description	Compose the company-level weekly digest — what was drafted, what is pending attorney review, what is blocked.
version	0.1.0
metadata	{"sources":[{"mode":"port-original","author":"ClaudeCoder","added_in":"0.1.0"}]}

Weekly Summary

Port-original skill. Hand-authored for Legal & Contracts. Owned by the CEO role.

When to fire

Once per week (recommended cadence: Friday afternoon or Monday morning), or on-demand from a partner / GC / founder request.

Inputs

• All work items closed, blocked, or escalated since the last summary.
• The current backlog (open items, ordered by priority).
• Any attorney sign-offs received and any items still pending attorney review.

Outputs

A short markdown digest, written as a comment / note on a designated weekly summary item:

# Week of <YYYY-MM-DD>

## Drafted and signed off
- <agent>: <one-line description> — signed off by <attorney> (<link>)

## Pending attorney review
- <work item> — drafted by <agent>, awaiting <attorney> review (<link>)

## In flight
- <agent>: <work item> (<status, ETA>)

## Blocked
- <work item> — <what's blocking, who needs to act>

## Escalated
- <work item> — <decision needed from attorney>

## Next week
- <priority items, in order>

How to compose

1. Walk the week's work, oldest to newest. Group by team, then by agent.
2. For "Drafted and signed off": include the deliverable in one line — what it was, which attorney signed off. No process narration.
3. For "Pending attorney review": name the attorney and how long it has been waiting. Flag anything past 48h.
4. For "In flight": include status and ETA. If ETA slipped, say so explicitly with the cause.
5. For "Blocked": name the blocker and the unblocking action. If a human owns the unblock, list them by name.
6. For "Escalated": include the decision needed and the recommendation made. Link to the underlying analysis rather than restating it.
7. For "Next week": the top 3-5 items by priority. If there's a deadline (closing, board meeting, regulatory filing), name it.

Style

• Short. One screen. Cut paragraphs that don't add information.
• Concrete. "NDA for Acme delivered to Sarah for sign-off" beats "Contracts team active on Acme."
• Honest about misses. "MSA for vendor X two days late, blocked on counterparty paper" — do not paper over.
• No agent self-praise. The summary is for the partner / GC / founder, not for agent vanity.

Boundaries

• Never include client identifiers, deal codenames, or confidential matter details without checking the requester's access level.

• Numbers in the summary (deal sizes, valuations, settlement amounts) must be sourced — link to the underlying artifact, not the agent's recollection.

• Do not editorialize on case outcomes, regulatory risk, or client strategy. That's the attorney's job.

• The summary is internal. Never share with parties outside the firm without attorney sign-off.

• UPL line. This skill is designed against the unauthorized-practice-of-law line. Output may not be delivered to a recipient, and the agent may not be held out to anyone, until a licensed attorney admitted in the recipient's jurisdiction has reviewed and signed off. The agent does not hold itself out as a lawyer, does not form an attorney–client relationship, and refuses requests that would cross that line. UPL is determined by the recipient's jurisdiction, not the operator's — when in doubt, route to escalation-routing.