Lessons 2 and 3 taught Method A, extracting knowledge from expert heads through structured interviews. Lesson 4 taught Method B, extracting knowledge from documents through the three-pass framework. This lesson teaches how to choose between them, how to combine them when both apply, and how to resolve conflicts when expert judgement and documented standards give different answers.
The default rule is simple: use Method A when the knowledge lives primarily in people, Method B when it lives primarily in documents, and both when it lives in both. In practice, the interesting question is not which method to use but how to handle the relationship between them when both apply: which, for most professional domains, is the case.
Professional domains differ in where their critical knowledge lives. The mapping is not arbitrary: it follows from the nature of the expertise in each domain.
Domain
Primary Method
Why
Extraction Sequence
Finance
A (expert heads)
The documented methodology is the scaffolding; the expert's calibration of when it applies cleanly and when it does not is the substance
Start with Method A interview; verify key instructions against documented standards in a targeted Pass One
Sales
A (expert heads)
Qualification criteria and playbooks are explicit; the instinct for deal timing, relationship dynamics, and when to walk away is tacit
Start with Method A interview; cross-reference against documented qualification frameworks
HR
B (documents)
The knowledge is genuinely in the handbooks, policy archives, and compliance guides; expert judgement resolves contradictions and fills gaps
Run full three-pass extraction first; conduct focused interview around the contradiction map and gap list
Operations
B (documents)
Standard operating procedures, process documentation, and quality standards are the primary knowledge source
Run full three-pass extraction first; interview operators to surface the undocumented workarounds and exception handling
Legal
A + B (both)
Substantial expert knowledge component (the lawyer's risk instinct) and substantial documented standards component (jurisdiction's contract law)
Run both methods; reconcile with the principle below
Healthcare
A + B (both)
Clinical judgement is tacit; clinical protocols are documented; both carry professional weight
Run both methods; reconcile with the principle below
Architecture
A + B (both)
Spatial reasoning and coordination judgement are tacit; BIM execution plans and building codes are documented
Run both methods; reconcile with the principle below
For Method A-primary domains (finance, sales), start with the interview. The resulting SKILL.md draft is the foundation. Then run a targeted Pass One against any relevant documented standards; not the full three-pass extraction, but a verification sweep to ensure the SKILL.md does not instruct the agent to do something that contradicts a documented standard the expert may have forgotten or taken for granted.
For Method B-primary domains (HR, operations), start with the document extraction. Run the full three-pass framework. Then conduct a focused interview; not the full five-question sequence, but a targeted session organised around the contradiction map and the gap list from Passes Two and Three. The expert's value in B-primary domains is in resolving ambiguities that the documents create, not in providing the foundational knowledge.
Legal, healthcare, and architecture are the domains where the A+B combination is most important and the reconciliation step most demanding. These domains have both a substantial expert knowledge component: the lawyer's risk instinct, the clinician's clinical judgement, the architect's spatial reasoning: and a substantial documented standards component: the jurisdiction's contract law, the clinical protocol, the BIM execution plan and building codes.
The SKILL.md for these domains needs to encode both. And when they conflict; when the expert's instinct says one thing and the written standard says another: the SKILL.md needs an explicit instruction about which takes precedence and under what conditions.
Run both methods fully. Start with whichever is primary for the specific task within the domain (a litigation risk assessment is A-primary even in a domain that is overall A+B; a regulatory compliance check is B-primary). Then run the second method. The reconciliation step comes after both methods have produced their output.
When expert judgement and documented standards conflict, the reconciliation principle determines which takes precedence:
Documented standards take precedence over expert judgement for matters of regulatory compliance and professional liability. The lawyer's jurisdiction constraints are set by the documented law, not by her personal interpretation of what the law should be. The clinician's prescribing authority is bounded by the clinical protocol, not by her sense of what would be best for this patient in this moment. The architect's structural calculations must comply with the building code, not with his spatial intuition.
Expert judgement takes precedence over documented standards for operational decisions within the scope of the professional's competence. Within the jurisdiction constraints, the lawyer's judgement about which clause patterns represent genuine risk for this client in this context is the operative expertise. Within the protocol boundaries, the clinician's assessment of how aggressively to treat is the professional judgement the SKILL.md should encode. Within the building code, the architect's decisions about material selection, spatial organisation, and aesthetic integration are the design expertise that no document captures.
Put concretely: the documented standard sets the boundaries. The expert judgement operates within them. Both need to be in the SKILL.md, and neither should be allowed to swallow the other.
Credit analyst example of reconciliation: The bank's credit policy (documented standard) specifies a minimum DSCR of 1.25x for all term lending. The senior analyst's judgement (expert knowledge) is that in certain sectors during specific economic conditions, a DSCR of 1.15x with strong covenant protections can be acceptable. The reconciliation: the SKILL.md encodes the 1.25x minimum as a hard constraint (documented standard takes precedence for regulatory compliance). It also encodes the analyst's sector-specific assessment framework as operational guidance that applies within the constraint: the agent can flag that a 1.20x DSCR with strong covenants may be worth committee review, but it cannot recommend approval below the documented minimum.
The domain-method mapping is a starting point, not a rigid classification. Specific organisations within a domain may differ based on how mature their documentation is, how much of the institutional knowledge has been codified, and how much remains in expert heads.
When assessing your own domain, ask three questions:
If you took the most experienced person in the role and replaced them with a competent new hire who had access to every document in the organisation, what would the new hire struggle with? The answer points to the tacit knowledge that Method A surfaces.
If you took the same experienced person and removed all the documented policies, standards, and procedures, what would they need to reconstruct from memory? The answer points to the explicit knowledge that Method B captures.
If the answers to both questions are substantial, your domain requires both methods: and the reconciliation principle determines how to handle the areas where they overlap.
Use these prompts in Anthropic Cowork or your preferred AI assistant to practise method selection and combination.
What you're learning: Domain classification is a practical skill, not an academic exercise. The three diagnostic questions reveal where your domain's critical knowledge lives (in people, documents, or both) and the classification directly determines your extraction strategy. Getting this right at the start saves significant rework later.
What you're learning: The reconciliation principle is not a simple hierarchy: it depends on whether the decision falls under regulatory compliance (documented standards win) or operational judgement within professional competence (expert knowledge wins). Practising the distinction across different domains builds the judgement needed to write reconciliation instructions in your own SKILL.md.
What you're learning: Planning the extraction sequence before beginning it prevents the most common error in multi-method extraction: running both methods without a clear plan for how their outputs relate. The one-page plan gives you a roadmap that anticipates the reconciliation decisions before you encounter them, which makes the actual extraction more focused and efficient.
The default rule for method selection is simple: Method A when knowledge lives in people, Method B when it lives in documents, both when it lives in both. The interesting question is not which method to use but how to handle the reconciliation when both apply; when expert judgement and documented standards give different answers for the same decision.
📋Quick Reference
Access condensed key takeaways and quick reference notes for efficient review.
Free forever. No credit card required.