alm-integration (DOORS / Polarion / Jira)

Flagship skill

alm-integration is a major automotive requirements skill. It wraps heterogeneous ALM backends behind consistent Agent-facing APIs.

Overview

Dimension	Coverage
Backends	IBM DOORS Next (production-ready), Polarion, ZenTao, Jira, Feishu Base
Surface	4 tools × 40+ actions
Artifacts	Requirements / architecture / design / tests / safety analyses / changes / defects
Flows	CRUD, linking, ReqIF exports, baselines, change-impact analysis
Highlights	Atomic folder operations, high-throughput Reportable REST pulls

Core tools

Rendering diagram…

Tool	Role	Sample actions
`alm_query`	Reads	`list_items` / `get_item` / `describe_adapter` / `list_folders` / `get_baseline`
`alm_mutate`	Writes	`create_item` / `update_item` / `delete_item` / `create_folder` / `create_baseline`
`alm_link`	Trace links	`create_link` (`satisfies` / `derivedFrom` / `verifies`, …) / `list_links` / `batch_link`
`alm_export`	Exports	`export_reqif` / `export_reportable_rest` / `export_docx`
`alm_bind_credential`	Secrets	`bind_doors` / `bind_jira` / `bind_polarion`

Supported item kinds

Type	Examples
Stakeholder requirement	Voice-of-customer statements
System / software requirements	Engineering specs
Architecture	Modules, interfaces, signals
Design	Detailed design elements
Test case / procedure	Verification assets
Safety analysis	DFA / FMEA / HAZOP
Change request	Engineering change records
Defect	Issue tracking

Link semantics

Link	Direction	ASPICE intuition
`satisfies`	Lower → upper	Child satisfies parent need
`derivedFrom`	Lower → upper	Derived lineage
`refines`	Lower → upper	Refinement
`verifies`	Test → requirement	Verification evidence
`validates`	Test → requirement	Validation evidence
`implements`	Code → design	Implementation binding

Workflows

Workflow 1 — Requirements to ReqIF

alm_query(action="list_items", source="doors", folder_id="SWE.1")
   ↓ requirement list
alm_query(action="get_item", source="doors", item_id=...)
   ↓ detail
alm_export(action="export_reqif", source="doors", folder_id="SWE.1")
   ↓ hand ReqIF to supplier

Workflow 2 — Batch `verifies` links

alm_query(action="list_items", source="doors", type="Test Case")
   ↓ cases
alm_link(action="batch_link",
    links=[{source_id, target_id, type: "verifies"}, ...])

Workflow 3 — Baseline diffing (with graft)

Rendering diagram…

See ASPICE case · scenario 2.

Error codes

Code	Retry?	Handling
`auth_expired`	no	Adapter re-login; escalate if still failing
`not_configured`	no	Backend not registered for `source`
`unsupported_action`	no	Check `describe_adapter` capabilities
`unsupported_item_type`	no	Item type unsupported on adapter

Differentiators

Atomic folder moves

Concurrent DOORS folder mutations can collide. The skill applies optimistic locking + compensating transactions for atomicity.

Reportable REST throughput

Bulk item hydration via Reportable REST is 10–50× faster than naive per-item queries.

ASPICE remediation

Primary repair tool after automotive-process-analyzer finds compliance gaps.

Invocation

/alm-integration Export every SWE.1 requirement to ReqIF

Examples:

"Create a requirement in DOORS"
"Build a test→requirement trace matrix"
"ReqIF package for Tier-1 supplier"
"Change-impact analysis"
"Snapshot baseline vNext"
"Batch satisfies links"

Not for: generic Q&A unrelated to ALM, or ticketing systems outside requirements scope.

alm-integration (DOORS / Polarion / Jira)

On this page