lp-do-briefing
Produce an understanding-only system briefing — how something works now, traced end-to-end with evidence pointers. No planning artifacts or tasks. Use when you need current-behavior understanding without committing to a plan.
npx skills add majiayu000/claude-skill-registry --skill lp-do-briefing --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Briefing Orchestrator `/lp-do-briefing` produces concise system briefings: current behavior explained end-to-end with evidence, no planning tasks. Use this skill when: - You want to understand a system before deciding whether to change it. - A stakeholder needs a factual snapshot of current behavior. - You need evidence pointers before writing a spec or planning a change. Use `/lp-do-fact-find` instead when you intend to plan or build a change. ## Global Invariants ### Operating mode **BRIEFING ONLY** ### Allowed actions - Read/search files and docs. - Run non-destructive commands (`rg`, targeted lint/typecheck) for evidence. - Inspect targeted git history. ### Prohibited actions - Code changes, refactors, or production data writes. - Destructive shell/git commands. - Planning/build execution — this skill ends at a briefing note. ### Evidence and quality rules - Non-trivial claims require file/line pointers. - Unknowns must include a concrete verification path. - Omit empty sections or collapse to one-line `Not investigated: <reason>`. ## Required Inputs - Topic or system area to understand. - At least one location anchor (path guess, route, endpoint, error/log, or user flow). If
- Global Invariants
- Operating mode
- Allowed actions
- Prohibited actions
- Evidence and quality rules
- Required Inputs
- Phase 0: Queue Check Gate
- Phase 1: Topic Selection
- Fast path (argument provided)
- Discovery path (no argument)
- Phase 2: Sufficiency Gate
- Phase 3: Investigate
- Phase 4: Persist Artifact
- Completion Message
What does the lp-do-briefing skill do?
Produce an understanding-only system briefing — how something works now, traced end-to-end with evidence pointers. No planning artifacts or tasks. Use when you need current-behavior understanding without committing to a plan.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill lp-do-briefing --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.