Structures verification of public claims about AI-driven memory shortages, high-bandwidth memory (HBM) demand, and trillion-dollar memory-chip valuations into an evidence checklist for finance, procurement, and platform teams. The workflow separates analyst price-target moves, year-to-date equity rallies, and vendor statements about agentic-AI workloads from independently observable supply signals (long-term agreements, stated capacity constraints, peer pricing power). It cites CNBC reporting that Micron crossed a $1 trillion market cap on May 26, 2026 after UBS raised its price target from $535 to $1,625, and that SK Hynix joined the trillion-dollar club on May 27, 2026 with shares up roughly 250% year to date amid AI chip demand lifting South Korea's Kospi—without endorsing any single stock call.
Use cases
- Board asks whether GPU-centric AI budgets should be revised for memory bottlenecks cited in trade media
- Procurement teams evaluate datacenter build plans when DRAM/HBM lead times or pricing shift
- Investor relations drafts need sourced context on memory-chip rallies versus hyperscaler capex narratives
- Risk committees compare Korean and U.S. memory suppliers after simultaneous trillion-dollar milestones
- Engineering leads sanity-check vendor claims that agentic workloads redefine CPU+memory demand mix
Key features
- Extract dated claims (market-cap milestones, price-target revisions, YTD percentage moves, shortage language) and tie each to a named outlet and URL.
- Classify evidence as exchange filings, sell-side research summaries in media, executive quotes, or macro/industry statistics.
- Map claimed demand drivers (agentic AI, HBM stacks, long-term agreements) to workloads your org actually runs.
- List counter-risks called out in coverage (memory-cycle bust history, pricing reversals, geopolitical supply shocks).
- Document dependency on specific suppliers or geographies (South Korea, U.S. fab networks, China demand).
- Publish a memo with verified facts, open questions, and retest triggers (earnings, supply-chain disclosures, benchmark releases).
When to Use This Skill
- After major memory-stock headlines before changing cloud spend or hardware roadmaps
- When negotiating long-term GPU+memory bundles with vendors citing industry shortages
- Before citing trillion-dollar market-cap figures in customer-facing strategy documents
Expected Output
Memory-supply due-diligence memo separating verified media-reported facts from speculative extrapolation, with explicit open questions.
Frequently Asked Questions
- Does this recommend buying Micron or SK Hynix?
- No—it structures evidence review around CNBC reporting; investment decisions stay outside this skill.
- Is a memory shortage guaranteed because CNBC said so?
- No—record the claim, identify the primary sources CNBC cites, and note what your own usage data shows.
- How does this relate to chip roadmap due diligence?
- Roadmap skills focus on process-node equivalence claims; this skill focuses on DRAM/HBM supply, pricing, and equity narratives tied to AI workloads.
Related
Related
3 Indexed items
Advanced chip roadmap claims due diligence review
Turns public semiconductor announcements into a verification checklist when vendors claim novel scaling laws, stacked logic architectures, or nanometer-class equivalence without independent benchmarks. Teams separate marketing nomenclature from manufacturing readiness by demanding yield, thermal, packaging, and third-party validation evidence—patterns highlighted when CNBC reported Huawei's LogicFolding and τ Scaling Law claims alongside analyst skepticism about true 1.4nm-class process breakthroughs without EUV access. The skill also maps export-control context (ASML EUV restrictions) and competitive implications for GPU vendors operating in constrained geographies.
Brainstorming before build
Explores goals, constraints, risks, and design options before committing to a specific implementation path. This technique is most valuable when facing product or UX decisions where the wrong choice is expensive to reverse—new features with uncertain user value, architectural pivots, or cross-functional dependencies where each team has a different mental model of the problem.
Prompt engineering
Crafts prompts with explicit task framing, role definition, output constraints, citation requirements, and few-shot examples so model responses are consistent, grounded in evidence, and actionable for downstream tasks. Prompt engineering reduces the variability and hallucination risk that comes from under-specified prompts.