Competitive Landscape
Provided by Patsnap Eureka.
Produce an evidence-driven competitive landscape report for a technology sector
or track. The deliverable is a structured report with player tiers, route
differentiation matrix, top-player profiles, and white-space opportunities —
conclusion first, evidence second — suitable for strategic planning, market
entry decisions, and R&D direction setting.
Use When
- Sector or technology-track player mapping and competitive tiering
- Route differentiation analysis across multiple companies
- White-space and opportunity identification in a technology domain
- Multi-company comparison anchored to a technology topic
- Domestic-vs-overseas player comparison in a defined technical arena
- "Who are the players in X?" or "What is the competitive landscape for X?"
Do Not Use
- Single company only, no sector scope → route to
company-tech-profile
- Pure technology-route comparison with no player/company object → route to
tech-route-comparison
- The task is a project/proposal review → route to
rd-initiation-review
- Market or commercial analysis without technology depth (pure market sizing,
pricing strategy, go-to-market)
- Legal patent opinion, FTO, or infringement analysis
Tool Routing And Fallback
This skill works across multiple tool environments. Before retrieval, detect
which capabilities are available and select the highest tier that is reachable.
Tier 1 (Recommended): Structured Patent/Paper Retrieval
- Use the host's best structured patent and paper retrieval stack.
- This usually means sector search, assignee/entity filtering, and record-level
deep fetch.
- Evidence grade: S/A (primary structured evidence)
- Required capabilities: sector discovery, entity filtering, route faceting or
structured narrowing, and deep-read of shortlisted records.
- Typical query count per run: 8-15 searches.
Tier 2 (Fallback): Web Research + Companion Lanes
- Use the host's best broad web research tool plus scholarly or finance
companion lanes when available.
- Exa, Tavily, Brave, official filings, and domain-specific research databases
are good examples, not hard requirements.
- Evidence grade: A/B
- Coverage loss vs Tier 1: no structured assignee extraction from patent data,
no IPC/CPC faceting, player discovery depends on web article quality
Tier 3 (Fallback): Generic Web Tools
- Use generic web search and page/PDF reading tools available in the host.
- Evidence grade: B/C
- Coverage loss vs Tier 2: no academic-focused ranking, broader noise
Tier 4 (Minimum): Pure LLM + User Materials
- No external tools required
- Evidence grade: C/U
- Coverage loss vs Tier 3: no current information, no verifiable citations
Routing Rules
- Detect available tools at the start of the workflow.
- Select the highest available tier as the primary retrieval channel.
- When a tier is unavailable, explicitly state the downgrade in the output
and in
method_decisions.md.
- Do not pretend lower-tier results have the same coverage as higher tiers.
- If the tool stack is degraded, lower confidence on player completeness
and white-space claims.
Minimum Working Files
Create or update these files in a writable run folder:
request.md
workplan.md
method_decisions.md
query_log.csv
source_index.csv
claim_ledger.csv
report.md
Recommended subfolders are described in references/workflow.md.
Default Workflow
Step 0: Freeze Scope
Confirm or infer the following before any retrieval:
- sector / track: the technology domain to analyze
- geography: default global unless user specifies a region
- time_window: default last 3 years unless user specifies otherwise
- known_players: any companies the user already has in mind (seed set)
- purpose: what decision this landscape supports (market entry / R&D
direction / investment screening / strategic planning)
- TopN target: default 5-10 players
Scope routing decision tree:
User input shape?
├─ Technology topic + multiple companies → proceed as player-set landscape
├─ Technology topic only, no companies → proceed; discover players from evidence
├─ "Who are the players in X?" → proceed as discovery landscape
├─ Only 1 company, no sector scope → redirect to company-tech-profile
├─ "Compare A with B in topic X" with 2+ companies → proceed as landscape
└─ Pure technology route, no player interest → redirect to tech-route-comparison
Step 1: Build Sector Evidence Baseline
- Run 2-3 broad sector searches with core technology terms.
- Tier 1: structured sector search across patents and papers
- Tier 2: targeted web research across technical reports, official pages, and
research coverage
- Tier 3/4: generic web or user-provided materials for initial candidate list
- Extract candidate player set from patent assignees and paper affiliations
in the search results. Aim for 10-20 candidates before filtering.
- Run 1-2 sector overview searches to capture market context, recent trends,
and players that may not appear in patent/paper data.
- Merge candidates from all sources into a single candidate list with
preliminary activity indicators.
Step 2: Tier Players
For each candidate in the list:
- Run a focused search to get patent and paper activity volume and recency.
- Tier 1: structured entity-filtered search
- Tier 2+: targeted web research across patent indices, official domains, and
research pages
- Classify each player using the tiering decision tree:
Player classification criteria:
├─ Tier 1 — Leader: high patent/paper activity + shipped products or
│ demonstrated capability + sustained recent growth
├─ Tier 2 — Challenger: moderate activity + clear differentiation or
│ strong niche position + growing trajectory
├─ Tier 3 — Follower: low activity or narrow focus, but present in the
│ space with identifiable technology routes
└─ Watchlist: emerging signals (recent filings, new entrants, pivoting
companies) but insufficient evidence for confident tiering
- Select top 5-7 players for deep-dive based on tier and relevance to the
user's decision context.
- If evidence is insufficient to tier confidently, keep the player on the
watchlist and note the evidence gap.
Tiering evidence rule:
- Full-scope counts and route breadth must come from aggregation, not samples
- Final tiers must combine patent evidence with paper and product signals
- Do not assign tiers from one noisy search or one source family alone
Step 3: Deep-Dive Top Players Individually
For EACH top player, analyze independently — never merge conclusions across players:
- Patent route analysis: key IPC clusters, filing trend, representative patents.
- Tier 1: structured per-player search; for large footprints, use optional
host-specific automation if available
- Tier 2+: targeted web research across patent indices, official domains, and
technical publications
- Deep-read 2-3 representative patents per player to extract route-specific
technical detail and differentiation evidence.
- Paper focus: research themes, collaboration network, publication venues.
- Product signals: shipped products, benchmarks, partnerships, market presence.
Per-player sampling defaults (Tier 1 with structured retrieval):
k = 6 for a focused challenger or niche player
k = 8 for a normal Tier 1 / Tier 2 player
k = 10 for highly diversified leaders
Two-level sampling rule (when sampling is used):
- Sector sample first: use it to understand routes, terminology, and
ecosystem structure
- Player sample second: use it to understand each shortlisted player's
real route emphasis
Never substitute one for the other:
- Sector sample ≠ player proof
- Player sample ≠ sector white-space proof
Adjust analysis emphasis by industry type:
Industry type?
├─ Semiconductor → emphasize: process node, EDA/IP, foundry vs fabless split,
│ patent family breadth
├─ Biopharma → emphasize: pipeline stage, target coverage, clinical results,
│ regulatory milestones
├─ AI / Software → emphasize: model benchmarks, open-source presence, API
│ adoption, paper citation impact
├─ New Energy / Materials → emphasize: material routes, production capacity,
│ cost trajectory, supply chain position
└─ General Manufacturing → balanced patent families + standard participation
+ supply chain signals
Step 4: Route Differentiation And White Spaces
- Build a route differentiation matrix: rows = top players, columns = key
technology routes or sub-tracks. Cells indicate strength level
(Strong / Moderate / Emerging / Absent) with brief evidence notes.
Example format:
| Player |
Route A |
Route B |
Route C |
| Company X |
Strong — 50+ patents, shipped product |
Emerging — 3 recent filings |
Absent |
| Company Y |
Moderate — 15 patents, no product yet |
Strong — market leader |
Emerging |
- Identify white spaces — areas that simultaneously satisfy ALL three criteria:
- Sparse coverage: few or no strong players currently active
- Clear technical value: the route addresses a real technical need or
market demand
- Explainable entry path: a realistic way for a new entrant to build
capability in this space
- If a potential white space fails any of the three criteria, do not present
it as an opportunity — note it as an observation instead.
Step 5: Synthesis
Synthesize all evidence into the output skeleton. Separate every claim into:
- Verified fact: directly supported by patent, paper, or official source
- Evidence-backed inference: reasonable conclusion from multiple signals
- Open gap: insufficient evidence, state what is missing
Output Skeleton
1. Lead With Conclusion
1-2 sentences: overall sector competitive dynamics — concentration level,
dominant routes, pace of change.
2. Player Tiers
Tiered list with 1-line evidence summary per player:
| Tier |
Player |
Key Evidence |
| Leader |
Company A |
150+ patents in route X, shipped product Y |
| Challenger |
Company B |
Growing paper output, niche in route Z |
| ... |
... |
... |
3. Route Differentiation Matrix
Markdown table: players (rows) × technology routes (columns).
Cells = strength indicator (Strong / Moderate / Emerging / Absent).
4. Top Player Profiles
2-3 paragraphs per top player covering:
- Primary technology route and focus areas
- Key differentiation from other players
- Trajectory and recent moves
5. White Spaces And Opportunities
2-3 identified white spaces, each with:
- What the gap is
- Why it has technical value
- How an entrant could realistically build capability there
6. Risks And Recommendations
- Sector-level risks (consolidation, regulatory shifts, technology disruption)
- Recommended actions aligned to the user's decision context
Every claim must cite its source type and identifier, e.g., [Patent: CN1234567B],
[Paper: DOI or title], [Web: source name].
Completion Gates
All must pass before delivering the final answer:
Guardrails
- Do not merge multiple companies into a single analytical conclusion.
- Do not assign tiers based on brand recognition alone — require patent, paper,
or product evidence.
- Do not invent white-space opportunities without evidence of sparse coverage.
- For non-evidence dimensions (TCO, regulation, teardown, collaboration networks),
write "evidence pending" rather than fabricating a judgment.
- Do not mix commercial players with academic institutions or upstream IP sources
in one comparison matrix unless the split is explicitly noted.
- Keep charts or visual aids to 1-2 maximum; retain only those that directly
support the analytical conclusion.
- Default TopN should be 5-10 companies; do not inflate the player set beyond
what the evidence supports.
- Do not use representative sampling for FTO, infringement, or exhaustive
legal-risk workflows.
- Do not collapse all players into one shared sampled set; sampling,
interpretation, and synthesis must remain per-player once top players are selected.
- Do not let sector-level sampled patents dominate the narrative of a specific
player unless that player-level evidence has been separately checked.
- Do not force a strong completeness claim when the tool stack is degraded —
prefer explicit uncertainty over false confidence.
- Record why a player was included, excluded, or downgraded.
Optional Host-Specific Automation
Some hosts may provide extra helpers for representative sampling, quantitative
aggregation, or patent-card normalization. These helpers are optional and are
not part of the core open-source contract.
If you use host-specific automation:
- record the helper and its role in
method_decisions.md
- keep the final evidence compatible with
query_log.csv, source_index.csv,
and claim_ledger.csv
- keep sector-level and player-level helper outputs clearly separated
Load These Files Only As Needed
- references/method-benchmark.md
- references/domain-playbooks.md
- references/workflow.md
- references/source-routing.md
- references/deliverables.md
- references/evidence-schema.md
- references/quality-gates.md
- templates/request-template.md
- templates/workplan-template.md
- templates/report-outline.md
1---2copyright: "Copyright © Patsnap. All rights reserved."3name: competitive-landscape4description:5 Technology-sector competitive landscape analysis with player tiering, route6 differentiation, and white-space identification. Use when the user asks for7 player mapping, sector competitor analysis, technology-track player8 comparison, domestic-vs-overseas player comparison, or any multi-player9 competitive assessment in a defined technology domain.10argument-hint: "[topic + optional region/purpose/player set]"11provider: "Patsnap Eureka"12compatibility: "Designed for Claude Code, Codex, and similar agent runtimes that can read/write local files and call whatever search tools are available."13deliverable-default: "Structured Markdown landscape report plus traceable evidence files; docx/pdf export is optional."14fallback-policy: "Prefer structured patent/paper retrieval for arena discovery and per-player evidence; otherwise downgrade through domain-specific sources, Exa, Tavily, Brave, web, and a known-URL reader without blocking the run."15metadata:16 source: https://skillmd.com/skills/patsnap/competitive-landscape17---1819# Competitive Landscape2021Provided by Patsnap Eureka.2223Produce an evidence-driven competitive landscape report for a technology sector24or track. The deliverable is a structured report with player tiers, route25differentiation matrix, top-player profiles, and white-space opportunities —26conclusion first, evidence second — suitable for strategic planning, market27entry decisions, and R&D direction setting.2829## Use When3031- Sector or technology-track player mapping and competitive tiering32- Route differentiation analysis across multiple companies33- White-space and opportunity identification in a technology domain34- Multi-company comparison anchored to a technology topic35- Domestic-vs-overseas player comparison in a defined technical arena36- "Who are the players in X?" or "What is the competitive landscape for X?"3738## Do Not Use3940- Single company only, no sector scope → route to `company-tech-profile`41- Pure technology-route comparison with no player/company object → route to42 `tech-route-comparison`43- The task is a project/proposal review → route to `rd-initiation-review`44- Market or commercial analysis without technology depth (pure market sizing,45 pricing strategy, go-to-market)46- Legal patent opinion, FTO, or infringement analysis4748## Tool Routing And Fallback4950This skill works across multiple tool environments. Before retrieval, detect51which capabilities are available and select the highest tier that is reachable.5253### Tier 1 (Recommended): Structured Patent/Paper Retrieval5455- Use the host's best structured patent and paper retrieval stack.56- This usually means sector search, assignee/entity filtering, and record-level57 deep fetch.58- Evidence grade: S/A (primary structured evidence)59- Required capabilities: sector discovery, entity filtering, route faceting or60 structured narrowing, and deep-read of shortlisted records.61- Typical query count per run: 8-15 searches.6263### Tier 2 (Fallback): Web Research + Companion Lanes6465- Use the host's best broad web research tool plus scholarly or finance66 companion lanes when available.67- Exa, Tavily, Brave, official filings, and domain-specific research databases68 are good examples, not hard requirements.69- Evidence grade: A/B70- Coverage loss vs Tier 1: no structured assignee extraction from patent data,71 no IPC/CPC faceting, player discovery depends on web article quality7273### Tier 3 (Fallback): Generic Web Tools7475- Use generic web search and page/PDF reading tools available in the host.76- Evidence grade: B/C77- Coverage loss vs Tier 2: no academic-focused ranking, broader noise7879### Tier 4 (Minimum): Pure LLM + User Materials8081- No external tools required82- Evidence grade: C/U83- Coverage loss vs Tier 3: no current information, no verifiable citations8485### Routing Rules8687- Detect available tools at the start of the workflow.88- Select the highest available tier as the primary retrieval channel.89- When a tier is unavailable, explicitly state the downgrade in the output90 and in `method_decisions.md`.91- Do not pretend lower-tier results have the same coverage as higher tiers.92- If the tool stack is degraded, lower confidence on player completeness93 and white-space claims.9495## Minimum Working Files9697Create or update these files in a writable run folder:9899- `request.md`100- `workplan.md`101- `method_decisions.md`102- `query_log.csv`103- `source_index.csv`104- `claim_ledger.csv`105- `report.md`106107Recommended subfolders are described in [references/workflow.md](references/workflow.md).108109## Default Workflow110111### Step 0: Freeze Scope112113Confirm or infer the following before any retrieval:114115- **sector / track**: the technology domain to analyze116- **geography**: default global unless user specifies a region117- **time_window**: default last 3 years unless user specifies otherwise118- **known_players**: any companies the user already has in mind (seed set)119- **purpose**: what decision this landscape supports (market entry / R&D120 direction / investment screening / strategic planning)121- **TopN target**: default 5-10 players122123Scope routing decision tree:124125```126User input shape?127├─ Technology topic + multiple companies → proceed as player-set landscape128├─ Technology topic only, no companies → proceed; discover players from evidence129├─ "Who are the players in X?" → proceed as discovery landscape130├─ Only 1 company, no sector scope → redirect to company-tech-profile131├─ "Compare A with B in topic X" with 2+ companies → proceed as landscape132└─ Pure technology route, no player interest → redirect to tech-route-comparison133```134135### Step 1: Build Sector Evidence Baseline1361371. Run 2-3 broad sector searches with core technology terms.138 - Tier 1: structured sector search across patents and papers139 - Tier 2: targeted web research across technical reports, official pages, and140 research coverage141 - Tier 3/4: generic web or user-provided materials for initial candidate list1422. Extract candidate player set from patent assignees and paper affiliations143 in the search results. Aim for 10-20 candidates before filtering.1443. Run 1-2 sector overview searches to capture market context, recent trends,145 and players that may not appear in patent/paper data.1464. Merge candidates from all sources into a single candidate list with147 preliminary activity indicators.148149### Step 2: Tier Players150151For each candidate in the list:1521531. Run a focused search to get patent and paper activity volume and recency.154 - Tier 1: structured entity-filtered search155 - Tier 2+: targeted web research across patent indices, official domains, and156 research pages1572. Classify each player using the tiering decision tree:158159```160Player classification criteria:161├─ Tier 1 — Leader: high patent/paper activity + shipped products or162│ demonstrated capability + sustained recent growth163├─ Tier 2 — Challenger: moderate activity + clear differentiation or164│ strong niche position + growing trajectory165├─ Tier 3 — Follower: low activity or narrow focus, but present in the166│ space with identifiable technology routes167└─ Watchlist: emerging signals (recent filings, new entrants, pivoting168 companies) but insufficient evidence for confident tiering169```1701713. Select top 5-7 players for deep-dive based on tier and relevance to the172 user's decision context.1734. If evidence is insufficient to tier confidently, keep the player on the174 watchlist and note the evidence gap.175176Tiering evidence rule:177178- Full-scope counts and route breadth must come from aggregation, not samples179- Final tiers must combine patent evidence with paper and product signals180- Do not assign tiers from one noisy search or one source family alone181182### Step 3: Deep-Dive Top Players Individually183184For EACH top player, analyze independently — never merge conclusions across players:1851861. **Patent route analysis**: key IPC clusters, filing trend, representative patents.187 - Tier 1: structured per-player search; for large footprints, use optional188 host-specific automation if available189 - Tier 2+: targeted web research across patent indices, official domains, and190 technical publications1912. Deep-read 2-3 representative patents per player to extract route-specific192 technical detail and differentiation evidence.1933. **Paper focus**: research themes, collaboration network, publication venues.1944. **Product signals**: shipped products, benchmarks, partnerships, market presence.195196Per-player sampling defaults (Tier 1 with structured retrieval):197198- `k = 6` for a focused challenger or niche player199- `k = 8` for a normal Tier 1 / Tier 2 player200- `k = 10` for highly diversified leaders201202Two-level sampling rule (when sampling is used):2032041. **Sector sample first**: use it to understand routes, terminology, and205 ecosystem structure2062. **Player sample second**: use it to understand each shortlisted player's207 real route emphasis208209Never substitute one for the other:210211- Sector sample ≠ player proof212- Player sample ≠ sector white-space proof213214Adjust analysis emphasis by industry type:215216```217Industry type?218├─ Semiconductor → emphasize: process node, EDA/IP, foundry vs fabless split,219│ patent family breadth220├─ Biopharma → emphasize: pipeline stage, target coverage, clinical results,221│ regulatory milestones222├─ AI / Software → emphasize: model benchmarks, open-source presence, API223│ adoption, paper citation impact224├─ New Energy / Materials → emphasize: material routes, production capacity,225│ cost trajectory, supply chain position226└─ General Manufacturing → balanced patent families + standard participation227 + supply chain signals228```229230### Step 4: Route Differentiation And White Spaces2312321. Build a route differentiation matrix: rows = top players, columns = key233 technology routes or sub-tracks. Cells indicate strength level234 (Strong / Moderate / Emerging / Absent) with brief evidence notes.235236Example format:237238| Player | Route A | Route B | Route C |239|--------|---------|---------|---------|240| Company X | Strong — 50+ patents, shipped product | Emerging — 3 recent filings | Absent |241| Company Y | Moderate — 15 patents, no product yet | Strong — market leader | Emerging |2422432. Identify white spaces — areas that simultaneously satisfy ALL three criteria:244 - **Sparse coverage**: few or no strong players currently active245 - **Clear technical value**: the route addresses a real technical need or246 market demand247 - **Explainable entry path**: a realistic way for a new entrant to build248 capability in this space2493. If a potential white space fails any of the three criteria, do not present250 it as an opportunity — note it as an observation instead.251252### Step 5: Synthesis253254Synthesize all evidence into the output skeleton. Separate every claim into:255256- **Verified fact**: directly supported by patent, paper, or official source257- **Evidence-backed inference**: reasonable conclusion from multiple signals258- **Open gap**: insufficient evidence, state what is missing259260## Output Skeleton261262### 1. Lead With Conclusion2632641-2 sentences: overall sector competitive dynamics — concentration level,265dominant routes, pace of change.266267### 2. Player Tiers268269Tiered list with 1-line evidence summary per player:270271| Tier | Player | Key Evidence |272|------|--------|-------------|273| Leader | Company A | 150+ patents in route X, shipped product Y |274| Challenger | Company B | Growing paper output, niche in route Z |275| ... | ... | ... |276277### 3. Route Differentiation Matrix278279Markdown table: players (rows) × technology routes (columns).280Cells = strength indicator (Strong / Moderate / Emerging / Absent).281282### 4. Top Player Profiles2832842-3 paragraphs per top player covering:285- Primary technology route and focus areas286- Key differentiation from other players287- Trajectory and recent moves288289### 5. White Spaces And Opportunities2902912-3 identified white spaces, each with:292- What the gap is293- Why it has technical value294- How an entrant could realistically build capability there295296### 6. Risks And Recommendations297298- Sector-level risks (consolidation, regulatory shifts, technology disruption)299- Recommended actions aligned to the user's decision context300301Every claim must cite its source type and identifier, e.g., `[Patent: CN1234567B]`,302`[Paper: DOI or title]`, `[Web: source name]`.303304## Completion Gates305306All must pass before delivering the final answer:307308- [ ] Sector scope and geography confirmed309- [ ] At least 3 sector-wide searches executed with results analyzed310- [ ] Player candidate set built from evidence, not assumed from prior knowledge311- [ ] If sector or player patent scopes are broad, representative sampling was312 executed or explicitly skipped with reason313- [ ] If sampling was used, sector sample supported route discovery rather than314 directly deciding final player tiers315- [ ] If player sampling was used, each player was sampled independently316- [ ] Top players deep-dived individually (not merged across players)317- [ ] Route differentiation matrix present with evidence backing per cell318- [ ] White spaces satisfy all 3 criteria (sparse + valuable + entry path)319- [ ] Every major claim has a traceable source citation320- [ ] Verified fact / evidence-backed inference / open gap clearly separated321- [ ] Output follows the 6-part skeleton322- [ ] No tier assigned without patent, paper, or product evidence basis323- [ ] Tool tier and coverage limitations explicitly stated in the output324- [ ] If evidence is insufficient for a complete landscape, deliver "candidate325 tiers + evidence gaps + next evidence-gathering directions" instead of326 forcing completeness327328## Guardrails329330- Do not merge multiple companies into a single analytical conclusion.331- Do not assign tiers based on brand recognition alone — require patent, paper,332 or product evidence.333- Do not invent white-space opportunities without evidence of sparse coverage.334- For non-evidence dimensions (TCO, regulation, teardown, collaboration networks),335 write "evidence pending" rather than fabricating a judgment.336- Do not mix commercial players with academic institutions or upstream IP sources337 in one comparison matrix unless the split is explicitly noted.338- Keep charts or visual aids to 1-2 maximum; retain only those that directly339 support the analytical conclusion.340- Default TopN should be 5-10 companies; do not inflate the player set beyond341 what the evidence supports.342- Do not use representative sampling for FTO, infringement, or exhaustive343 legal-risk workflows.344- Do not collapse all players into one shared sampled set; sampling,345 interpretation, and synthesis must remain per-player once top players are selected.346- Do not let sector-level sampled patents dominate the narrative of a specific347 player unless that player-level evidence has been separately checked.348- Do not force a strong completeness claim when the tool stack is degraded —349 prefer explicit uncertainty over false confidence.350- Record why a player was included, excluded, or downgraded.351352## Optional Host-Specific Automation353354Some hosts may provide extra helpers for representative sampling, quantitative355aggregation, or patent-card normalization. These helpers are optional and are356not part of the core open-source contract.357358If you use host-specific automation:359360- record the helper and its role in `method_decisions.md`361- keep the final evidence compatible with `query_log.csv`, `source_index.csv`,362 and `claim_ledger.csv`363- keep sector-level and player-level helper outputs clearly separated364365## Load These Files Only As Needed366367- [references/method-benchmark.md](references/method-benchmark.md)368- [references/domain-playbooks.md](references/domain-playbooks.md)369- [references/workflow.md](references/workflow.md)370- [references/source-routing.md](references/source-routing.md)371- [references/deliverables.md](references/deliverables.md)372- [references/evidence-schema.md](references/evidence-schema.md)373- [references/quality-gates.md](references/quality-gates.md)374- [templates/request-template.md](templates/request-template.md)375- [templates/workplan-template.md](templates/workplan-template.md)376- [templates/report-outline.md](templates/report-outline.md)