Legal Issue Spotting Chain

validated legal chain v1.0.0 cc-by-sa

Block ID: a2d96a7d-21e2-4087-af6a-094974f7516a

Community-contributed block. PromptDNA makes no guarantee of output quality or fitness for purpose. This block operates in a regulated domain. Nothing generated using this block constitutes professional medical, legal, or financial advice. User assumes all responsibility for use.

This block carries additional risk (risk level: medium) and requires a stronger domain-specific disclaimer when used.

Template

Spot the legal issues in the fact pattern {fact_pattern} comprehensively, since missing an issue is worse than mishandling one. (1) Read the facts twice: once for the story, once hunting for legal significance — every party relationship, every promise, every act or omission, every transfer, and every harm is a potential issue trigger. (2) Work through the plausible areas of law systematically rather than jumping to the obvious claim: contract, tort, property, statutory/regulatory, and procedural — checking each against the facts so you don't tunnel on the first issue spotted. (3) For each party pairing, ask what claims one might bring against the other and what defenses would answer them — issues live in relationships, and a defendant's cross-claims are easy to miss. (4) Flag the facts that are deliberately ambiguous or incomplete, since the issue often hinges on a fact not given, and note what you'd need to know. (5) Distinguish the dispositive issues (that decide the outcome) from minor ones, and rank them, so analysis effort follows importance. (6) Present the spotted issues organized by claim and party, each phrased as a specific legal question, noting this is preliminary issue identification to guide analysis and a licensed attorney's judgment, not a legal opinion.

Spot the legal issues in the fact pattern {fact_pattern} comprehensively, since missing an issue is worse than mishandling one. (1) Read the facts twice: once for the story, once hunting for legal significance — every party relationship, every promise, every act or omission, every transfer, and every harm is a potential issue trigger. (2) Work through the plausible areas of law systematically rather than jumping to the obvious claim: contract, tort, property, statutory/regulatory, and procedural — checking each against the facts so you don't tunnel on the first issue spotted. (3) For each party pairing, ask what claims one might bring against the other and what defenses would answer them — issues live in relationships, and a defendant's cross-claims are easy to miss. (4) Flag the facts that are deliberately ambiguous or incomplete, since the issue often hinges on a fact not given, and note what you'd need to know. (5) Distinguish the dispositive issues (that decide the outcome) from minor ones, and rank them, so analysis effort follows importance. (6) Present the spotted issues organized by claim and party, each phrased as a specific legal question, noting this is preliminary issue identification to guide analysis and a licensed attorney's judgment, not a legal opinion.

Variables

Name	Type	Required	Trust level
fact_pattern		yes

issue-spottingfact-patternlegal-analysischain-of-thought

Ratings

0.0

Overall (0)

0.0

Accuracy

0.0

Consistency

0.0

Clarity

0.0

Efficiency

Benchmarks

Not yet self-validated against any benchmark. Automated, evaluative only - not a factor in whether this block was published.

Submitted by James P FounderMod via mcp · 2026-07-18