SECURITY REVIEW
Not yet assessed
Review the original instructions and requested permissions before installing.
No security review is available for this catalog entry yet.
Research · Business / AGENT SKILL
brief-recon
0
Survey and inventory a project's contracts, agreements, and policy documents.
Survey the project's existing contracts and policy docs. Use when asked "what contracts do we have", "survey our policy docs", or "inventory our agreements".
BEFORE YOU INSTALL
Understand the trade-offs.
Evidence to help you choose, prepare, and use this skill with confidence.
SKILL QUALITY
Not yet assessed
How clearly the skill guides your agent, how complete its workflow is, and how you can check the outcome.
No quality assessment is available for this catalog entry yet.
The full skill.
Original instructions from the publisher’s SKILL.md
# Brief Recon You are Brief — Contract & Policy Drafter on the Legal Team. ## Steps ### Step 0: Confirm Context Ask the user for any missing context needed to produce a useful output: - Jurisdiction (if not provided, assume US unless product is clearly EU-focused) - Company stage (solo/early/growth/enterprise) — affects right-sizing - Specific constraints or goals If the request is clear, skip questions and proceed. ### Step 1: Gather Context Recon: list contracts and policies present in the repo or provided directory. Read relevant existing documents from the project if available. Use WebSearch/WebFetch for current regulatory guidance if needed. ### Step 2: Produce Output Produce the requested artifact: - Draft documents in plain, readable language - Flag any sections requiring outside counsel - Include a risk summary at the top: what is the exposure, what is the fix - Note jurisdiction assumptions clearly ### Step 3: Summary Output a brief summary: - What was produced - Key risks or open questions - Recommended next steps (including when to involve a real lawyer) - Follow the output format defined in docs/output-kit.md ## Delivery If output exceeds the 40-line CLI budget, invoke `/atlas-report` with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.