brieflisted

# Brief Management Briefs are persistent work state for local SEO engagements. One brief per location. Brand rollup for multi-location work. Scheduled task outputs extend the brief over time, building a compounding history of every scan, audit, report, and finding for each business. --- ## Structure ``` briefs/ {brand}/ _brand.brief.md ← config + rollup across all locations reports/ ← brand-level rollup reports {location}/ location.brief.md ← always current, always lean reports/ ← weekly, monthly, QBR reports scans/ ← geogrid scans, citation audits, page audits drafts/ ← GBP posts, review responses awaiting approval alerts/ ← monitoring alerts ``` --- ## First Run Detection **This is the most important section.** When a user mentions a specific business and no brief exists, do not proceed with their request yet. Run setup first, then circle back to what they asked for. ### Detection Before doing any work for a specific business, check for an existing brief: - Claude Code: look for `briefs/{brand-slug}/{location-slug}/location.brief.md` - Claude Project: check Project knowledge base for a brief file for this business - If found: go to **Resuming from a Brief** - If not found: go to **First Run Setup** ### First Run Setup Tell the user: > "I don't have a brief for [Business Name] yet. Let me grab a few details so I can track everythin