Decision Memo
Document a legal decision for "$ARGUMENTS". Record the decision question, alternatives considered, rationale, accepted risks, and conditions for future review.
See also /project-management-decision-log for recording a project, technical or process decision rather than a legal one with its accepted risk.
Note: AI-generated legal content does not constitute legal advice. Consult a qualified attorney for decisions with significant legal exposure.
Arguments. $ARGUMENTS may contain the project name and optional flags. Take the first token as <project> and treat --skip-checks as a flag; never include flags in file paths. All paths below use <project>. If --skip-checks is present, skip the prerequisite check and, before writing any artifact, append one line to .singularskills/log.jsonl: {"ts":"<ISO timestamp>","skill":"legal-decision-memo","workflow":"legal","phase":null,"project":"<project>","event":"skipped","artifact":"<artifact file>","note":"<reason or \"none given\">"}.
Prerequisites
None — this is a utility skill.
Process
State the decision question clearly:
- Frame the question as a specific, answerable decision (e.g., "Should we include an arbitration clause or allow litigation?" not "What should we do about disputes?")
- Scope the decision to a single, well-defined choice
Document context and constraints:
- Business context driving the need for a decision
- Legal constraints (regulatory requirements, contractual obligations, precedent)
- Timeline and urgency factors
- Budget or resource constraints that limit options
List alternatives considered:
- Document a minimum of 2-3 alternatives
- For each alternative, provide:
- Description — what this option entails
- Pros — benefits and advantages
- Cons — drawbacks and risks
- Legal risk level — Low/Medium/High
- Cost/effort estimate — relative cost or effort to implement
Record the final decision and rationale:
- State the chosen option clearly
- Explain why this option was selected over the others
- Reference specific pros that were decisive
- Acknowledge specific cons that were accepted as trade-offs
Document accepted risk:
- What could go wrong with this decision
- Likelihood of negative outcomes (Low/Medium/High)
- Potential impact if negative outcomes materialize
- Any mitigating factors or safeguards in place
Record decision metadata:
- Who made or approved the decision
- Date of the decision
- Stakeholders consulted
- Any dissenting opinions or concerns raised
Define review and revisit conditions:
- Specific triggers that would require reconsideration (e.g., regulatory change, threshold breach, contract renewal)
- Scheduled review date if applicable
- Metrics or indicators to monitor
Tag with relevant legal area:
- Contracts, Privacy, Intellectual Property, Employment, Compliance, Corporate, Litigation, Regulatory, or other applicable area
Write the artifact by appending to .singularskills/legal/<project>/decision-log.md:
If the file does not exist, create it starting with # Legal Decision Log — <project>
Append a new decision entry with a horizontal rule separator (---) between entries
Each entry includes:
- Decision ID — sequential number (e.g., DEC-001)
- Date — date of the decision
- Decision Question — the question being decided
- Context and Constraints — factors driving the decision
- Alternatives Considered — each alternative with pros, cons, and risk level
- Decision — the chosen option
- Rationale — why this option was selected
- Accepted Risk — risks acknowledged with likelihood and impact
- Decision Maker(s) — who made or approved the decision
- Legal Area — tagged category
- Review Conditions — triggers for reconsideration
Output
The decision memo appended to .singularskills/legal/<project>/decision-log.md. Present a summary to the user highlighting:
- The decision question and chosen option
- Key rationale points
- Primary risks accepted and their mitigation
- When the decision should be revisited
1---2name: legal-decision-memo3description: Document a legal decision in the project's decision log — the question, alternatives with pros, cons and legal risk, the chosen option and rationale, accepted risk, approvers and revisit triggers. Use when the user has made a legal call and wants a record of why and what risk they accepted. Not for weighing a team or management decision; see /leadership-decision.4metadata:5 source: https://skillmd.com/skills/bromso/legal-decision-memo6 argument-hint: "[project] [--skip-checks]"7---89# Decision Memo1011Document a legal decision for "$ARGUMENTS". Record the decision question, alternatives considered, rationale, accepted risks, and conditions for future review.1213See also `/project-management-decision-log` for recording a project, technical or process decision rather than a legal one with its accepted risk.1415> **Note:** AI-generated legal content does not constitute legal advice. Consult a qualified attorney for decisions with significant legal exposure.1617**Arguments.** `$ARGUMENTS` may contain the project name and optional flags. Take the first token as `<project>` and treat `--skip-checks` as a flag; never include flags in file paths. All paths below use `<project>`. If `--skip-checks` is present, skip the prerequisite check and, **before writing any artifact**, append one line to `.singularskills/log.jsonl`: `{"ts":"<ISO timestamp>","skill":"legal-decision-memo","workflow":"legal","phase":null,"project":"<project>","event":"skipped","artifact":"<artifact file>","note":"<reason or \"none given\">"}`.1819## Prerequisites2021None — this is a utility skill.2223## Process24251. **State the decision question clearly:**26 - Frame the question as a specific, answerable decision (e.g., "Should we include an arbitration clause or allow litigation?" not "What should we do about disputes?")27 - Scope the decision to a single, well-defined choice28292. **Document context and constraints:**30 - Business context driving the need for a decision31 - Legal constraints (regulatory requirements, contractual obligations, precedent)32 - Timeline and urgency factors33 - Budget or resource constraints that limit options34353. **List alternatives considered:**36 - Document a minimum of 2-3 alternatives37 - For each alternative, provide:38 - **Description** — what this option entails39 - **Pros** — benefits and advantages40 - **Cons** — drawbacks and risks41 - **Legal risk level** — Low/Medium/High42 - **Cost/effort estimate** — relative cost or effort to implement43444. **Record the final decision and rationale:**45 - State the chosen option clearly46 - Explain why this option was selected over the others47 - Reference specific pros that were decisive48 - Acknowledge specific cons that were accepted as trade-offs49505. **Document accepted risk:**51 - What could go wrong with this decision52 - Likelihood of negative outcomes (Low/Medium/High)53 - Potential impact if negative outcomes materialize54 - Any mitigating factors or safeguards in place55566. **Record decision metadata:**57 - Who made or approved the decision58 - Date of the decision59 - Stakeholders consulted60 - Any dissenting opinions or concerns raised61627. **Define review and revisit conditions:**63 - Specific triggers that would require reconsideration (e.g., regulatory change, threshold breach, contract renewal)64 - Scheduled review date if applicable65 - Metrics or indicators to monitor66678. **Tag with relevant legal area:**68 - Contracts, Privacy, Intellectual Property, Employment, Compliance, Corporate, Litigation, Regulatory, or other applicable area69709. **Write the artifact** by appending to `.singularskills/legal/<project>/decision-log.md`:71 - If the file does not exist, create it starting with `# Legal Decision Log — <project>`7273 - Append a new decision entry with a horizontal rule separator (`---`) between entries74 - Each entry includes:75 - **Decision ID** — sequential number (e.g., DEC-001)76 - **Date** — date of the decision77 - **Decision Question** — the question being decided78 - **Context and Constraints** — factors driving the decision79 - **Alternatives Considered** — each alternative with pros, cons, and risk level80 - **Decision** — the chosen option81 - **Rationale** — why this option was selected82 - **Accepted Risk** — risks acknowledged with likelihood and impact83 - **Decision Maker(s)** — who made or approved the decision84 - **Legal Area** — tagged category85 - **Review Conditions** — triggers for reconsideration8687## Output8889The decision memo appended to `.singularskills/legal/<project>/decision-log.md`. Present a summary to the user highlighting:90- The decision question and chosen option91- Key rationale points92- Primary risks accepted and their mitigation93- When the decision should be revisited