domain-research
Acquire working expertise in an unfamiliar industry, market, or technical field in hours using a four-step protocol covering core vocabulary, key players, regulatory landscape, and value chain. Use when entering a domain the team does not know, before writing a domain brief for other agents, or when unfamiliar terminology is blocking analysis.
- License 许可
- Apache-2.0
- 最近更新
- 2026-10-27
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- domain-research
- description
- Acquire working expertise in an unfamiliar industry, market, or technical field in hours using a four-step protocol covering core vocabulary, key players, regulatory landscape, and value chain. Use when entering a domain the team does not know, before writing a domain brief for other agents, or when unfamiliar terminology is blocking analysis.
02 资源文件 4
- 参考文档references/competitive-intelligence.md5.2 KB
- 参考文档references/domain-mapping.md5.4 KB
- 参考文档references/source-evaluation.md5.1 KB
- 参考文档templates/domain-brief.md2.3 KB
03 SKILL.md 正文
Domain Research Skill
Use this protocol to acquire domain expertise rapidly when facing unfamiliar industries, markets, or technical fields. Follow the four-step structure below, then synthesize findings into a domain brief for other agents.
The Four-Step Protocol
Step 1: Core Vocabulary, Key Players, and Regulatory Landscape
Build foundational knowledge first:
- Identify core vocabulary. Find 8-12 domain-specific terms that appear repeatedly in authoritative sources. Include at least one term you'd have guessed wrong without research (e.g., "pharming" in agriculture, "basis points" in finance).
- Map key players. Identify 5-10 organizations that define the domain: market leaders, regulators, standard-setters, advocacy groups. Note their role and influence.
- Scan regulatory environment. Find the primary regulator(s) for this domain. Understand what they regulate (products, practices, disclosures) and how recently rules changed.
- Document three recent shifts. What's changed in the last 2-3 years? New regulations, technology adoption, consolidation, market growth?
Step 2: Value Chain Mapping
Understand how money and value flow:
- Identify production layers. Who makes raw inputs? Who processes them? Who distributes? Who consumes?
- Find the money flows. In which layer do margins concentrate? Where is competition intense vs. protected?
- Locate switching costs. What locks customers, suppliers, or partners into relationships? What would make them switch?
- Spot dependencies. Which players depend on others for survival? Where are bottlenecks?
Step 3: Domain-Specific Constraints, Risks, and Failure Modes
Expose what could go wrong:
- Technical constraints. What physical, computational, or chemical limits exist? What's theoretically impossible?
- Regulatory hazards. Where do organizations stumble with compliance? What penalties apply?
- Market risks. Cyclicality? Substitution threats? Disintermediation? Commoditization?
- Operational failure modes. What breaks first under stress? What requires perfect execution?
- Black swan factors. What low-probability, high-impact event would reshape the domain? (Pandemic, regulation, competitor innovation.)
Step 4: Analogies to Known Domains
Build intuition through comparison:
- Find structural parallels. What aspect resembles a domain you understand? (E.g., "cloud infrastructure is like electrical grids—commoditized, always-on, regulated by geography.")
- Identify differences. Where does the analogy break? What's fundamentally different?
- Use analogies carefully. Flag them as intuition-building, not proof.
Step 5: Competitive Landscape (Optional but Recommended)
When the domain involves markets with multiple players, add competitive intelligence:
- Map the competitive set. Direct, adjacent, and substitute competitors — 3-5 per tier.
- Decode positioning and strategy. Value propositions, pricing models, target segments, recent strategic moves.
- Analyze dynamics. Market concentration, switching costs, network effects, convergence vs. divergence.
- Identify whitespace. Underserved segments, overserved segments, structural vulnerabilities, timing opportunities.
See references/competitive-intelligence.md for the full protocol.
This step is optional for purely technical or regulatory domains but recommended for any domain where commercial competition shapes outcomes.
Source Evaluation Criteria
Assess credibility, recency, and relevance:
- Primary vs. secondary. Primary sources (regulatory filings, earnings calls, original research) carry more weight. Secondary sources (news, analysis) are faster but risk distortion.
- Recency. Prefer sources published in the last 1-2 years. Flag older sources as potentially outdated.
- Vendor bias. Discount marketing materials and vendor whitepapers by 50%. They're biased toward selling.
- Regulatory authority. Government bodies and industry standard-setters are highly credible on their domain.
- Triangulation. When three independent sources agree, confidence rises. Conflict signals nuance or bias.
- Author credentials. Does the author work in or study the domain? Or parachute in from unrelated fields?
See references/source-evaluation.md for detailed guidance.
Synthesis: The Domain Brief
Produce a consumable brief for other agents:
- Distill findings into a domain overview (2-3 sentences).
- List core vocabulary with definitions.
- Draw a value chain diagram or text description.
- Name major players and their roles.
- State regulatory constraints.
- List domain-specific risks and failure modes.
- Include structural analogies.
- Rate confidence (high/medium/low) for each claim.
- Cite sources.
Use the template at templates/domain-brief.md.
Anti-Patterns: What Isn't Real Domain Knowledge
Avoid these traps:
- Surface jargon. Using domain terms without understanding what they mean. ("The API leverages blockchain synergies.") Test yourself: can you explain it to a skeptic?
- Outdated assumptions. Treating five-year-old market structures as current. Always check recency.
- Vendor marketing as fact. "Enterprise AI adoption is skyrocketing" may just be a vendor's marketing narrative, not market reality.
- Overgeneralization. Assuming all players in a domain follow the same model. Exceptions often matter most.
- Neglecting regulation. Missing regulatory context is a critical gap. Always ask: "Who regulates this, and what are they watching?"
Reference Files
references/source-evaluation.md— Detailed guidance on assessing sources during researchreferences/domain-mapping.md— Framework for mapping unfamiliar domain structurereferences/competitive-intelligence.md— Competitive set mapping, positioning analysis, market dynamicstemplates/domain-brief.md— Output template for synthesizing findings
Quick Start
- Spend 10 minutes identifying vocabulary and key players (Step 1).
- Spend 15 minutes mapping the value chain (Step 2).
- Spend 10 minutes identifying risks and constraints (Step 3).
- Spend 5 minutes sketching analogies (Step 4).
- (Optional) Spend 15 minutes mapping competitive landscape (Step 5).
- Synthesize into a domain brief using the template.
Total time: ~45 minutes for a working domain model (~60 minutes with competitive landscape).
04 同仓库更多 Skills
twenty-year-land-plan
Apply the Bren discipline of evaluating every land and development decision on a twenty-year horizon, with a comprehensive plan for how the land, the community, and the surrounding public infrastructure evolve together. Deals optimized for a five-year exit are structurally different from deals that compound across generations; insist on knowing which kind you are making. Use when evaluating land, entitlements, master-planned development, or phasing decisions, and when separating five-year exit deals from generational holds.
thematic-gut-check
Apply the Gray discipline of identifying the structural theme behind every real estate deal, testing where that theme sits in its capital-flow lifecycle, and insisting that deals without a named theme — or deals late in a crowded theme — clear a higher bar. A mediocre deal in a strong theme usually beats a clever deal in a weak one. Use when naming the structural thesis behind a deal, judging whether that theme is early or crowded, and setting the bar the deal must clear.
supply-pipeline-gut-check
Apply the Zell discipline of grounding every real estate thesis in the local supply pipeline. Demand counts over adjectives — units under construction, units permitted, units proposed — and convert them into a forward absorption schedule. A deal that ignores the pipeline is a bet on a market you have not actually studied. Use when validating a market thesis, forecasting absorption and rent growth, or counting units under construction, permitted, and proposed.
ruin-scenario-mapping
Apply the Taleb discipline of identifying, for every real estate deal, the specific chain of events that produces ruin — permanent, unrecoverable capital loss — and verifying that no single such chain has non-trivial probability. Deals with any plausible ruin path must be restructured or abandoned. Use when sizing leverage, testing refinancing, covenant, and liquidity risk, or checking whether any single failure chain can permanently wipe out the position.
revenue-cost-architecture
Design a venture's revenue streams, pricing logic, cost structure, and unit economics so the business model has a coherent theory of value capture, not just value creation. Use after the value proposition and customer segment are set and before financial projections, when choosing a pricing model, calculating contribution margin or CAC payback, or checking whether the unit economics hold at scale.
replacement-cost-stress-test
Apply the Buffett discipline of pricing every real estate asset against the cost to rebuild it from scratch. The ratio of purchase price to replacement cost sets a ceiling on long-run downside: below replacement cost, new supply cannot profitably undercut you; at or above it, you are buying a liability disguised as an asset. Use when setting a purchase price, judging downside protection, or testing how exposed an asset is to newly built competing supply.