Claude pluginClaude Code
- Manifest
.claude-plugin/plugin.json- Workflows
commands/*.md and skills/*/SKILL.md- Distribution
- Claude plugin marketplace
EAINE agent plugins · Candidate validation release
Bring governed AI engineering into the agent workspace.
One portable EAINE assessment workflow, projected for Claude Code, Cursor, and Visual Studio Code. The packages help teams inspect architecture and the complete AI SDLC without turning AI output into approval, certification, or release authority.
Current package line1.0.0-beta.1
- Framework
- EAINE v1.0-RC1 Candidate
- Capability
- Advisory local assessment
- Validation
- Structural checks complete
- Runtime status
- Behavioral validation pending
Three host projections
Native packaging, one governed meaning.
Each projection carries the same seven Skills, eleven workflow commands, knowledge references, assessment templates, evidence boundaries, and Candidate limitations. Host-specific packaging cannot widen the portable EAINE authority boundary.
Agent Plugins 1.0Cursor
- Manifest
plugin.json- Workflows
rules/*.mdc, commands/*.md, and skills/*/SKILL.md- Distribution
- Cursor Marketplace
Agent Plugins 1.0Visual Studio Code
- Manifest
plugin.json- Workflows
com.github.copilot/* and skills/*/SKILL.md- Distribution
- Agent plugin marketplace or Git source
AI SDLC coverage
Every lifecycle stage stays visible.
The lifecycle is iterative. Experiment, emergency, rollback, improvement, and retirement paths do not waive evidence, security, human authority, or release decisions.
- 01Discovery
- 02Requirements Engineering
- 03Architecture and Design
- 04Development
- 05Quality Engineering
- 06Security Validation
- 07Deployment and Release
- 08Operations
- 09Continuous Improvement
Assessment workflows
Architecture, risk, evidence, and decisions remain connected.
- Scope and applicability
- Inherent risk and tailoring
- Nine-stage lifecycle planning and review
- Architecture and authority review
- Requirement-level conformance proposals
- Separate maturity observations
- Evidence-gap review and bounded export
Architecture review covers components, trust zones, identities, interfaces, data and knowledge flows, authority contracts, control planes, failure containment, rollback, recovery, operations, and retirement. It proposes findings; it does not enforce controls.
Validation boundary
A serious beta, not a readiness claim.
The packages are available for governed validation preparation. Installation, behavioral compatibility, decision equivalence, and project outcomes still require target-runtime and independent human evidence.
What is already checked
- Package structure and manifest presence
- Seven portable Skill definitions
- Eleven workflow command projections
- Portable knowledge, templates, and schemas
- Per-file SHA-256 inventories
- Default-deny authority invariants
What remains open
- Behavioral testing in each supported host version
- Skill selection, command routing, and instruction precedence
- Relative-resource resolution and refusal behavior
- Decision-equivalence testing across projections
- Independent assessment and field evidence
- Public distribution and marketplace authorization
Marketplace path
Validate privately, then publish through native stores.
Use a version-pinned private Git marketplace for named validation teams. Submit the same frozen release to public stores only after runtime tests, provenance, support, and distribution approval are complete.
Claude Code
- Validate the frozen package locally in the target runtime.
- Publish it from a version-pinned Git repository or private marketplace.
- Submit the reviewed release through the host's publication channel.
- Link the verified listing and release digest from this page.
Cursor
- Validate the frozen package locally in the target runtime.
- Publish it from a version-pinned Git repository or private marketplace.
- Submit the reviewed release through the host's publication channel.
- Link the verified listing and release digest from this page.
Visual Studio Code
- Validate the frozen package locally in the target runtime.
- Publish it from a version-pinned Git repository or private marketplace.
- Submit the reviewed release through the host's publication channel.
- Link the verified listing and release digest from this page.
EAINE does not claim permanent feature parity between providers. Host requirements and review processes can change; confirm the linked official guidance before each submission.