Closes gaps in market-concentration analysis, hot-document identification with mandatory internal-document production, serial-acquisition risk analysis, spoliation assessment, and timing-model review.
Scanned 9/11/2026
Install to Claude Code
npx -y skills add sunyifeisb-art/legalwork --skill draft-response-to-second-request-for-information --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Draft Response To Second Request For Information?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/sunyifeisb-art-draft-response-to-second-request-for-information)More formats (shields.io, HTML) on the badges page.
---
name: draft-response-to-second-request-for-information
task_id: antitrust-competition/draft-response-to-second-request-for-information
description: Closes gaps in market-concentration analysis, hot-document identification with mandatory internal-document production, serial-acquisition risk analysis, spoliation assessment, and timing-model review.
activates_for: [planner, solver, checker]
---
# Skill: Second Request Response Strategy Memorandum
## 1. Subject-matter triage (only if applicable)
- This skill applies to a Second Request response strategy memo in an antitrust merger review.
- Triage the record into the operative workstreams: concentration analysis, document-production strategy, serial-acquisition exposure, timing / outside-date risk, and any spoliation indicators.
- If the source set includes multiple relevant product markets, time periods, or acquisition events, treat each as a separate analytic unit rather than compressing them into a single narrative pass.
## 2. Failure modes the skill is correcting
- Baseline omits the merger-guideline concentration analysis for each relevant market, or treats one market as representative of all markets.
- Baseline states that a market is “highly concentrated” or “unchanged” without tying the conclusion to the governing concentration framework, the pre/post levels, and the delta.
- Baseline fails to identify internal documents that should be produced in response to the Second Request, or treats hot documents as optional framing material instead of mandatory production material.
- Baseline does not distinguish ordinary competitive discussion from board-level strategy, pricing, share, or integration language that may drive agency theory.
- Baseline does not analyze serial-acquisition exposure where the record shows prior acquisitions or roll-up activity in the same market.
- Baseline does not model whether substantial compliance can occur in time to avoid outside-date risk.
- Baseline ignores document-destruction or deletion instructions that may require immediate escalation.
- Baseline relies on third-party market analysis without checking the arithmetic and assumptions against the underlying source data.
- Baseline gives conclusions without a clear recommendation path for counsel, business stakeholders, and document custodians.
## 3. Legal frameworks / domain conventions that apply
- HSR Second Request practice: substantial compliance is the operative compliance milestone, and the waiting period resumes only after substantial compliance under the HSR Act, 15 U.S.C. § 18a, and the implementing rules in 16 C.F.R. Parts 803 and 804.
- Merger concentration analysis should be tied to the applicable merger-guideline framework used in the source materials or generally recognized agency practice; compute the pre-transaction level, post-transaction level, and delta for each relevant market before stating whether a structural presumption is implicated.
- Internal-document production is mandatory in Second Request practice for responsive board materials, strategic planning materials, and communications reflecting competitive, pricing, capacity, customer, or integration strategy; the memo should treat production compliance as a core legal and process issue, not a discretionary one.
- Serial-acquisition analysis should be framed under the agency’s cumulative-effects / roll-up theory where the record shows multiple acquisitions in the same industry or line of commerce.
- Spoliation analysis should be grounded in the duty to preserve reasonably anticipated evidence once litigation or investigation is reasonably foreseeable; deletion, scrubbing, or alteration instructions warrant immediate review and escalation.
- Third-party market analysis must be checked for arithmetic integrity before reliance; correct obvious calculation errors and reconcile any divergence between analyst assumptions and the source record.
- Agency theories commonly to be anticipated include structural concentration, internal-document evidence, cumulative acquisition pattern, and timing pressure from an expiring outside date.
## 4. Analytical scaffolds
1. Enumerate the relevant markets, product lines, or competitive arenas from the source record before analyzing concentration.
- For each market, compute the pre-transaction level, post-transaction level, and change using the source data.
- Compare each result to the applicable concentration framework and state whether the market triggers a structural concern.
- Where a third-party analyst supplied figures, verify the arithmetic and any boundary assumptions before using them.
2. Enumerate the responsive document categories before discussing hot documents.
- Separate board materials, strategic plans, integration materials, pricing or margin discussions, customer-focused materials, and ordinary business communications.
- Identify which documents are likely to be treated as especially probative by the agency and explain why their tone, audience, or timing matters.
- For each hot document, pair identification with a production and narrative strategy that explains context without minimizing the language.
3. Enumerate prior acquisitions or acquisition clusters if the source set shows more than one.
- Analyze whether the pattern suggests a cumulative acquisition strategy in the same market or adjacency.
- Cross-reference the acquisition history against the current transaction’s competitive theory.
- Explain how the pattern may affect agency skepticism even where any single prior deal was not independently challenged.
4. Build the timing model as a sequence, not a single estimate.
- Identify the Second Request issue date, the projected substantial-compliance date, the post-compliance waiting period, and the merger agreement outside date.
- Compare the projected clearance date against the outside date and flag whether timing is compressed, manageable, or likely to require an extension or other deal-protection step.
- If the record lacks a single definitive date, state the assumption set explicitly and run the timing analysis on each available scenario.
5. Screen the record for preservation and spoliation issues.
- Look for instructions to delete, alter, scrub, or “clean up” records after an investigation was foreseeable.
- If such language exists, flag it prominently, recommend immediate factual investigation, and assess disclosure implications.
- Distinguish between ordinary retention housekeeping and conduct that may support a spoliation inference.
6. Test each agency theory against counter-arguments.
- For concentration: challenge market definition, substitutability assumptions, entry, and any data-quality problems.
- For hot documents: separate advocacy language from literal market facts and identify context that may blunt the inference.
- For serial acquisition: distinguish unrelated acquisitions, non-overlapping assets, or different competitive dynamics.
- For timing: identify whether the outside date can be extended, paused, or otherwise managed without undue business harm.
7. Close each issue with a concrete consequence and action path.
- Tie the issue to the regulatory, transactional, operational, or litigation consequence it creates.
- State what counsel or the business must do next to reduce the risk.
## 5. Vertical / structural / temporal relationships (only if applicable)
- Structural relationship: concentration evidence, internal documents, and acquisition history should be read together; a single document may reinforce a structural concern that the market math already suggests.
- Temporal relationship: document dates, acquisition dates, and preservation-trigger dates matter; later language can be more probative of current intent, while post-notice deletion instructions can raise separate preservation issues.
- Process relationship: the response strategy must align with the production workflow, custodian collection plan, and the clearance timeline so that legal positions and document handling are consistent.
- If the source record does not contain multiple periods, acquisitions, or markets, state that explicitly and explain why the single-item treatment is appropriate.
## 6. Output structure conventions
- Open with an executive summary that gives the overall risk posture and the main agency theories to expect.
- Use a market analysis section that lists each relevant market separately and states the concentration result and source basis for each.
- Use a hot-documents section that identifies each significant document or category, describes the problematic language or theme, and states the proposed contextual framing.
- Include a serial-acquisition analysis section only if the record shows prior acquisitions or roll-up behavior.
- Include a timeline / outside-date section that models the compliance path against the merger-agreement deadline.
- Include a spoliation section only if the record contains deletion, scrubbing, alteration, or other preservation-red-flag language.
- End with a Recommended Actions block.
- Each recommendation should begin with an imperative verb.
- Assign the recommendation to the appropriate role, such as counsel, business owner, or custodian lead.
- Include a timing anchor tied to the Second Request process, the outside date, or another source-based milestone.
- Keep the memo usable as a strategy document: precise, source-tethered, and organized by issue rather than by document dump.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!