Methodology inspired by publicly taught medtech pipeline frameworks; all text is an original paraphrase.
Defaults
| Parameter |
Default Value |
Rationale |
| asset_scope |
all disclosed devices |
Full-pipeline enumeration first |
| stage_lens |
feasibility + pivotal |
Design-iteration stages, not drug-phase labels |
| reimbursement_aware |
true |
Value framed against coverage paths, not raw approval |
| post_market_scan |
true |
Obligations and surveillance state surfaced |
| value_frame |
risk-adjusted |
Modeled value = unadjusted peak x POS, both shown |
Preflight
Run canonical pre-flight per contracts/preflight.md. Include the X-Agentii-Trace header on every tool call per contracts/x-agentii-trace-header.md — carry the _run_id from your first tool result and name yourself (and your parent, if you were spawned). Confirm ticker resolution via search_companies before asset queries.
Triggers
- "Analyze [ticker]'s device pipeline."
- "What is in [ticker]'s feasibility and pivotal portfolio?"
- "Where is each of [ticker]'s devices in its design cycle?"
- "Which of [ticker]'s programs are approaching submission?"
- "What RWE studies support [ticker]'s devices?"
- "What post-market obligations does [ticker] carry?"
- "Risk-adjust [ticker]'s device pipeline."
- "What is the next catalyst for each of [ticker]'s devices?"
- "How does [ticker]'s device pipeline compare to peers?"
- "Which device classifications (PMA/De Novo/510(k)) map to [ticker]'s pipeline?"
- "Map [ticker]'s devices by clinical stage and indication."
- "What does [ticker]'s pipeline say about its reimbursement path?"
Production Grounding
- Device stage ladder: feasibility (first-in-human, small N) → pivotal (registrational) → submission (PMA / De Novo / 510(k)) → post-market. Devices iterate through design versions; design freezes and iteration cycles are the pipeline milestones, not drug-style phases.
- Pivotal design varies by classification: PMA demands the highest evidence bar, De Novo novel classification, 510(k) equivalence — the pipeline's value path depends on the expected track.
- RWE studies (registries, claims analyses) increasingly support coverage and label expansion; treat them as pipeline assets with their own timelines.
- Post-market obligations (surveillance studies, MDR reporting) shape long-term liability and the re-approval path.
- Reimbursement-aware framing: pipeline value assumes a coverage path; an asset without one is discounted.
- Grounding detail lives in
references/knowledge-frameworks.md.
Data Source Priority
get_company_devices / search_universe_devices — asset inventory from the med universe.
search_clinical_trials / get_clinical_trial — study stage, design type, status, enrollment.
get_device_decision — decision history and upcoming decisions per device.
- Knowledge layer:
search_knowledge_entries for framework grounding.
Methodology
Retrieval Scope
structured_only
Retrieval Strategy
- Pull asset inventory (
get_company_devices), cross-check the universe (search_universe_devices).
- Enrich per asset with study records (
search_clinical_trials) — stage, design type, status-diff.
- Pull decision history and upcoming dates (
get_device_decision).
- Flag post-market obligations and RWE study presence per asset.
- Size each asset (peak x POS); ground in knowledge entries.
Temporal Scope
See frontmatter temporal_scope block. Device development and post-market windows span years; history may reach back 8-12 quarters.
Tool Allowlist
See frontmatter allowed_tools.
Protocol
- Asset enumeration
- Stage and design-cycle mapping
- Decision-track alignment
- Post-market and RWE overlay
- Risk-adjusted synthesis
Modes
- Phase scan (default): all devices by stage with next catalyst and expected track.
- Design cycle: design-iteration state, freezes, and submission readiness.
- Post-market: obligations, surveillance state, and RWE support.
Tool Fallbacks
| Failure |
Fallback |
| get_company_devices empty |
search_universe_devices by company or indication; annotate coverage_gap |
| No trial rows |
Mark stage undisclosed; do not guess pivotal vs feasibility |
| No decision history |
Flag the submission track unknown; state both possibilities |
| Knowledge tools empty |
Proceed with structured data only |
Output File
{ticker}/{YYYY-MM-DD_HHMM}_pipeline-devices_{affix}.md
Output Structure
- Executive Summary — pipeline stance in 2-3 sentences
- Asset Table — stage, design type, expected track, next catalyst
- Design-Cycle Read — iteration state, freezes, submission readiness
- Post-Market & RWE — obligations, surveillance, registries
- Risk-Adjusted Sizing — peak x POS with reimbursement framing
- Coverage Gaps — missing records, undisclosed stage, degraded modes
Error Handling
| Error |
Fallback |
| Stage unknown |
Mark "undisclosed"; do not guess |
| Classification ambiguous |
State the evidence-bar difference across tracks |
| No catalysts found |
Say so explicitly; note the pipeline may be early-stage |
Memory Load
See contracts/memory-load.md.
Snapshot
See contracts/snapshot-synthesis.md.
Final Summary (TUI)
Include ### Key Citations block with 0-10 clickable /v/ URLs.
References
contracts/citation-and-memory.md
contracts/output-frontmatter-schema.md
contracts/memory-load.md
contracts/snapshot-synthesis.md
contracts/preflight.md
references/knowledge-frameworks.md
1---2name: pipeline-devices3description: "Device pipeline analysis: feasibility and pivotal study stages, design-iteration cycles, RWE studies, and post-market obligations, with reimbursement-aware value framing and decision-track awareness across the med universe."4sectors: [med.medicines_biotech, med.medical_devices]5multi_ticker_semantics: single_target6temporal_scope:7 default_quarters: 88 max_quarters: 209 description: "Long-horizon pipeline window default 8 quarters; up to 20 for multi-year device development and post-market programs."10allowed_tools:11 - get_company_devices12 - search_universe_devices13 - search_clinical_trials14 - get_clinical_trial15 - get_device_decision16 - search_companies17 - get_company_profile18 - search_knowledge_entries19retrieval_scope: structured_only20min_tool_diversity: 321parameter_free: false22metadata:23 source: https://skillmd.com/skills/agentii-ai/pipeline-devices24---2526> Methodology inspired by publicly taught medtech pipeline frameworks; all text is an original paraphrase.2728## Defaults2930| Parameter | Default Value | Rationale |31|-----------|---------------|-----------|32| asset_scope | all disclosed devices | Full-pipeline enumeration first |33| stage_lens | feasibility + pivotal | Design-iteration stages, not drug-phase labels |34| reimbursement_aware | true | Value framed against coverage paths, not raw approval |35| post_market_scan | true | Obligations and surveillance state surfaced |36| value_frame | risk-adjusted | Modeled value = unadjusted peak x POS, both shown |3738## Preflight3940Run canonical pre-flight per `contracts/preflight.md`. Include the `X-Agentii-Trace` header on every tool call per `contracts/x-agentii-trace-header.md` — carry the `_run_id` from your first tool result and name yourself (and your parent, if you were spawned). Confirm ticker resolution via `search_companies` before asset queries.4142## Triggers4344- "Analyze [ticker]'s device pipeline."45- "What is in [ticker]'s feasibility and pivotal portfolio?"46- "Where is each of [ticker]'s devices in its design cycle?"47- "Which of [ticker]'s programs are approaching submission?"48- "What RWE studies support [ticker]'s devices?"49- "What post-market obligations does [ticker] carry?"50- "Risk-adjust [ticker]'s device pipeline."51- "What is the next catalyst for each of [ticker]'s devices?"52- "How does [ticker]'s device pipeline compare to peers?"53- "Which device classifications (PMA/De Novo/510(k)) map to [ticker]'s pipeline?"54- "Map [ticker]'s devices by clinical stage and indication."55- "What does [ticker]'s pipeline say about its reimbursement path?"5657## Production Grounding5859- Device stage ladder: feasibility (first-in-human, small N) → pivotal (registrational) → submission (PMA / De Novo / 510(k)) → post-market. Devices iterate through design versions; design freezes and iteration cycles are the pipeline milestones, not drug-style phases.60- Pivotal design varies by classification: PMA demands the highest evidence bar, De Novo novel classification, 510(k) equivalence — the pipeline's value path depends on the expected track.61- RWE studies (registries, claims analyses) increasingly support coverage and label expansion; treat them as pipeline assets with their own timelines.62- Post-market obligations (surveillance studies, MDR reporting) shape long-term liability and the re-approval path.63- Reimbursement-aware framing: pipeline value assumes a coverage path; an asset without one is discounted.64- Grounding detail lives in `references/knowledge-frameworks.md`.6566## Data Source Priority67681. `get_company_devices` / `search_universe_devices` — asset inventory from the med universe.692. `search_clinical_trials` / `get_clinical_trial` — study stage, design type, status, enrollment.703. `get_device_decision` — decision history and upcoming decisions per device.714. Knowledge layer: `search_knowledge_entries` for framework grounding.7273## Methodology7475### Retrieval Scope76structured_only7778### Retrieval Strategy791. Pull asset inventory (`get_company_devices`), cross-check the universe (`search_universe_devices`).802. Enrich per asset with study records (`search_clinical_trials`) — stage, design type, status-diff.813. Pull decision history and upcoming dates (`get_device_decision`).824. Flag post-market obligations and RWE study presence per asset.835. Size each asset (peak x POS); ground in knowledge entries.8485### Temporal Scope86See frontmatter temporal_scope block. Device development and post-market windows span years; history may reach back 8-12 quarters.8788### Tool Allowlist89See frontmatter allowed_tools.9091### Protocol921. Asset enumeration932. Stage and design-cycle mapping943. Decision-track alignment954. Post-market and RWE overlay965. Risk-adjusted synthesis9798## Modes99100- **Phase scan** (default): all devices by stage with next catalyst and expected track.101- **Design cycle**: design-iteration state, freezes, and submission readiness.102- **Post-market**: obligations, surveillance state, and RWE support.103104## Tool Fallbacks105106| Failure | Fallback |107|---------|----------|108| get_company_devices empty | `search_universe_devices` by company or indication; annotate coverage_gap |109| No trial rows | Mark stage undisclosed; do not guess pivotal vs feasibility |110| No decision history | Flag the submission track unknown; state both possibilities |111| Knowledge tools empty | Proceed with structured data only |112113## Output File114115`{ticker}/{YYYY-MM-DD_HHMM}_pipeline-devices_{affix}.md`116117## Output Structure1181191. **Executive Summary** — pipeline stance in 2-3 sentences1202. **Asset Table** — stage, design type, expected track, next catalyst1213. **Design-Cycle Read** — iteration state, freezes, submission readiness1224. **Post-Market & RWE** — obligations, surveillance, registries1235. **Risk-Adjusted Sizing** — peak x POS with reimbursement framing1246. **Coverage Gaps** — missing records, undisclosed stage, degraded modes125126## Error Handling127128| Error | Fallback |129|-------|----------|130| Stage unknown | Mark "undisclosed"; do not guess |131| Classification ambiguous | State the evidence-bar difference across tracks |132| No catalysts found | Say so explicitly; note the pipeline may be early-stage |133134## Memory Load135136See `contracts/memory-load.md`.137138## Snapshot139140See `contracts/snapshot-synthesis.md`.141142## Final Summary (TUI)143144Include ### Key Citations block with 0-10 clickable /v/ URLs.145146## References147148- `contracts/citation-and-memory.md`149- `contracts/output-frontmatter-schema.md`150- `contracts/memory-load.md`151- `contracts/snapshot-synthesis.md`152- `contracts/preflight.md`153- `references/knowledge-frameworks.md`