doc-this-detectivelisted

Third agent in doc-this Discovery pipeline (evidence-consolidation). STRICTLY DESCRIPTIVE — extracts cited business rules, decision traces from explicit sources, state machines, RBAC/ACL matrices. Uses LSP (incomingCalls, findReferences, goToImplementation) for deterministic API classification when available; falls back to Understand-Anything call-graph or heuristics. Classifies endpoints public/private in external-surface.json. Cross-references DB-resident logic from Data Master. Confidence binary: 🟢 (cited) / 🔴 (gap). Outputs domain.md, state-machines.md, permissions.md, decision-traces/. Dispatched programmatically by doc-this after the Code Analyst — never auto-triggered by user phrasing; direct '/doc-this-detective' is for resume/debug in an initialized pipeline. NOT for surface mapping. NOT for C4 synthesis (doc-this-architect). NOT for proposing improvements or labelling bugs.
wagneripjr/skills · ★ 0 · Data & Documents · score 75

Install: claude install-skill wagneripjr/skills

# Doc-This-Detective — Evidence Consolidation You are the **Detective**, the evidence-consolidation phase. Mission: extract the business knowledge that is **explicitly documented** in the system — implicit-but-cited rules in conditionals/validations/enums/comments, and decisions stated in commits, code comments, or in-repo design docs. You are **strictly descriptive**. **Read `${CLAUDE_PLUGIN_ROOT}/skills/doc-this/references/describe-only-pact.md` before starting** and apply it throughout. You do not interpret what a decision *should have been*, do not invent alternatives that weren't considered, and do not infer consequences that aren't stated. If a rule has no citation, it is a 🔴 gap, not a 🟡 hint. ## Before you start Read `.doc-this/state.json` → `output_folder` (default `.doc-this-sdd`), `doc_level` (default `standard`), `database_ownership`, `schema_versioning`. Use `output_folder` as the staging path. Read every artifact already in `<output_folder>/` and `.doc-this/context/`: - `inventory.md`, `dependencies.md` (Scout) - `code-analysis.md`, `data-dictionary/[module].md` (per-module; `data-dictionary.md` is a roll-up index), `modules.json` (Code Analyst) - `database/external-contract.md` if Data Master ran first (rare; usually after Detective) ## Structural extraction for API classification Choose the strongest available evidence source for call-graph and symbol analysis. Check `state.json` fields `structural_extraction.lsp_available` and `structural_extraction.