matter-intake

Intakes new legal matters through uniform questions and writes matter.md, history.md, and _log.yaml records.

Updated Jun 17, 2026
One-click install
npx skills add https://github.com/tk1cntt/PhapChe --skill matter-intake-tk1cntt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: matter-intake
Source: https://github.com/tk1cntt/PhapChe/tree/main/docs/claude-for-legal-main/litigation-legal/skills/matter-intake
Command: npx skills add https://github.com/tk1cntt/PhapChe --skill matter-intake-tk1cntt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Bringing a new legal matter into a litigation portfolio often happens ad hoc, producing inconsistent records that cannot be compared or rolled up later. This Skill runs every new matter through the same structured intake so the portfolio stays uniform and auditable. ## Core Features & Use Cases - Uniform Intake Workflow: Walks through identification, conflicts check, source, risk triage, materiality, outside counsel, internal owners, legal hold, key dates, and initial posture. - Conflicts Gate Enforcement: Blocks record creation when conflicts are not-run, offering documented paths to clear, defer, or bypass with a permanent override record. - Structured Output Generation: Creates a narrative matter.md, seeds an append-only history.md, and appends a schema-conformant row to _log.yaml for portfolio rollups. - Use Case: A demand letter arrives from a counterparty. Run the intake to capture the matter details, confirm conflicts status, assign outside counsel, flag the missing legal hold, and commit a consistent log row the status skill can aggregate. ## Quick Start Say "intake this new matter: Acme v. Us 2026" and answer the intake questions to generate the matter record.

Frequently Asked Questions about matter-intake

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I intake a new legal matter into a litigation portfolio?

Invoke the intake with the matter name and answer the uniform questions covering identification, conflicts, source, risk triage, materiality, counsel, owners, legal hold, and key dates. The skill writes matter.md, history.md, and a structured _log.yaml row after your confirmation.

What happens if the conflicts check has not been run?

The intake stops at a gate and will not create any records. You must either run conflicts now, mark it pending with an owner and due date if the practice profile allows parallel intake, or bypass with a documented override rationale that stays visible in every status report.

What files does the matter intake process create?

It creates a narrative matter.md with the full intake, seeds an append-only history.md with the intake as the first entry, and appends a structured row to the shared _log.yaml. The slug is lowercase with hyphens and the year, checked for uniqueness first.

Does the intake skill run the conflicts check itself?

No. It records the conflicts status, method, clearing party, and entities checked, but the actual clearance happens in whatever system or judgment the practice profile declares. It also does not issue legal holds or decide the initial case theory.

How is matter status derived during intake?

Status derives from the source field: pre-suit threats and demand letters map to threatened, while served complaints, subpoenas, and regulator inquiries map to active. Internal reports default to threatened unless a formal process has started.