Coding Assistants

Reqvire integrates with coding assistants by exposing the engineering knowledge graph as structured, AI-ready context. Assistants can work from ontology, capability, requirement, refinement, verification, and implementation evidence instead of scattered prose.

Integration Options

Claude Code plugin

Marketplace plugin with Reqvire slash commands and systems-engineering skills for model analysis, requirement authoring, verification work, impact analysis, and task generation.

Codex skill package

Installable Reqvire skills for Codex workflows, including semantic engineering and ontology authoring guidance.

MCP server

Standard Streamable HTTP tool interface for MCP-capable clients. Read/report tools are available by default; mutation tools require explicit enablement.

Claude Code Plugin

Add the Reqvire marketplace, install the plugin, then restart Claude Code.

/plugin marketplace add https://github.com/reqvire-org/reqvire
/plugin install reqvire@reqvire-org

Skills: syseng and ontology-authoring.
Commands include analyze-model, add-requirement, add-verification, add-capability, analyze-coverage, analyze-impact, collect, lint-model, consolidate, generate-tasks, rename-element, mv, mv-file, and rm.
Plugin content comes from claude-plugins/skills/syseng and claude-plugins/skills/ontology-authoring.

Codex Skills

Reqvire includes Codex skill packages in the repository. The installer copies them to $CODEX_HOME/skills and replaces any older Reqvire skill copies.

./scripts/install-codex-skill.sh

# Installed skill directories
$CODEX_HOME/skills/reqvire-syseng
$CODEX_HOME/skills/reqvire-ontology-authoring

MCP Server

Start Reqvire as an MCP Streamable HTTP server when an assistant should discover tools dynamically.

reqvire mcp
reqvire mcp --with-size-estimates
reqvire mcp --enable-mutations

Convenience no-install form:

npx -y @reqvire-org/reqvire@latest --workspace /path/to/repository mcp

Use reqvire.ontologies when an assistant needs ontology and SHACL context. Pass full: true when it also needs generated model context triples for elements, relations, attachments, concept references, ontology declarations, and shape references.

Recommended Workflow

1Capability first: understand or define the operational ability being changed.

2Ontology context: inspect or attach semantic vocabulary that gives the capability meaning.

3Requirements: define implementable obligations that specify the capability.

4Refinements: add specifications, constraints, behaviors, states, or I/O contracts.

5Semantic contracts: add reusable SHACL shape profiles under the ontology plane and link them with constrainedBy/constrain and use/usedBy.

6Verifications: ensure capabilities or leaf requirements are verified.

7Implementation links: connect code, tests, proofs, and evidence with satisfiedBy.

8Validation: run validate, lint, coverage, traces, and change impact before review.

Useful Prompts

Show unverified leaf requirements and propose verifications.
Explain the capability, ontology context, requirements, and verification evidence for this change.
Analyze change impact against main and summarize invalidated verifications.
Create implementation tasks for the impacted requirements with traceability.
Refactor this requirement to extract technical detail into specification elements.

Use Cases

Engineering graph exploration

Coverage and traceability analysis

Change impact assessment

Capability planning

Implementation task generation

Ontology-driven context collection

Requirement refactoring

Verification hardening