CSlawyer1985/legal-skillhub / skills/appellee-response-brief
appellee-response-brief
VerifiedDrafts appellee response briefs for federal and state appellate courts, exploiting standards of review and record evidence to defend trial court decisions. Trigger when the user needs to respond to an appellant's opening brief or defend a favorable lower court ruling on appeal.
Appellee's Response Brief
Defends the trial court's decision by exploiting deference standards, grounding every argument in the record, and systematically dismantling appellant's challenges.
Quick Start
Gather before drafting:
- Appellant's opening brief — every issue raised, claimed standards of review, key arguments
- Lower court decision — opinion, order, or judgment under review
- Trial record — transcripts, exhibits, supporting documents
- Appellate rules — FRAP 28/32 or state equivalent; local rules, word limits, deadlines
Deference Standards
The appellee's core advantage is deference. Always argue for the most deferential applicable standard.
| Standard | Applies To | Appellee Advantage |
|---|---|---|
| Abuse of discretion | Evidentiary rulings, case management | Affirm unless irrational |
| Clearly erroneous | Factual findings (bench trial) | Affirm if any evidence supports |
| De novo | Pure legal questions | Argue alternative grounds |
| Plain error | Unpreserved issues | Appellant bears heavy burden |
Core Workflow
1. Counter-Statement of the Case
- Present record facts supporting affirmance with extensive citations (transcript pages, exhibit numbers)
- Correct appellant's factual omissions and mischaracterizations
- Emphasize procedural posture triggering deference
2. Argue Each Issue
For every issue the appellant raises, apply this sequence:
- Preservation — raised below? If not, argue waiver/forfeiture
- Standard of review — frame to maximize deference
- Record support — cite specific evidence backing the lower court
- Distinguish cases — factual differences, procedural posture, jurisdiction
- Alternative grounds — argue affirmance on grounds the lower court didn't reach
- Harmless error — even if error occurred, show it didn't affect the outcome
Lead with your strongest ground for affirmance. Address issues in your best narrative order, not necessarily appellant's.
3. Assemble Brief
- Front matter: cover page (correct color per FRAP 32 [VERIFY]), TOC with argumentative headings, Table of Authorities with pin cites, jurisdictional statement (if required), Statement of Issues reframed for affirmance
- Argument: structured per Step 2
- Conclusion: concise request for affirmance; no new arguments
- Certificates: Certificate of Compliance (word count, typeface), Certificate of Service
Pitfalls and Checks
- Don't chase every minor point — focus on arguments that could actually reverse
- Address preservation/waiver issues early when applicable
- The record is your strongest tool — cite it relentlessly
- Raise alternative grounds for affirmance even if the lower court didn't rely on them
- Verify all citations or mark
[VERIFY] - Maintain a professional, measured tone — project confidence in the judgment below
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |