feat(cli): add… | ai-driven-dev/framework

No file or test is named in the issue. Start by locating the skill and plugin packaging definitions, then compare their metadata with Mistral Vibe's required author, version, vibe_version, permissions, and tags fields. Done means the affected skills are valid for Mistral Vibe and the compatibility check confirms the required metadata.

Problem

The AIDD CLI cannot install, update, restore, diagnose, or remove the framework for Mistral Vibe.

The original report attributed the failure to missing skill fields (author, version, vibe_version, permissions, tags). That diagnosis is obsolete. Current Vibe follows the Agent Skills SKILL.md contract: name and description are required; the reported fields are not required skill fields. author and version belong to optional package metadata.

The actual gap is target packaging and lifecycle support in aidd.

Investigation outcome (Vibe 2.25.7, 2026-09-23)

A runtime probe executed Vibe's shipped ClaudePluginAdapter against every current AIDD plugin:

8/8 plugin packages accepted;
51/51 skills imported;
2 aidd-dev agents not imported because Claude agents have no compatibility mapping;
aidd-context SessionStart hook not imported;
2/3 aidd-telemetry hooks imported (PostToolUse, Stop), while SessionStart was not;
no fatal compatibility diagnostic.

So the skills are valid. Installing the existing Claude packages directly would provide partial support, but would silently lose agents and session-start behavior. That is not a sufficient framework support contract.

Vibe now has a native plugin format based on Agent Plugins 1.0:

project discovery: .vibe/plugins/<plugin>/ after the folder is trusted;
user discovery: ~/.vibe/plugins/<plugin>/;
required manifest: plugin.json with $schema: https://agent-plugins.org/schemas/1.0.0/plugin.schema.json and name;
portable components: skills/ and mcp.json;
Vibe extension components: ai.mistral.vibe/agents/ and ai.mistral.vibe/hooks.toml;
plugin skills and agents are namespaced at runtime.

Plugin resolution only runs on Vibe's Unified Harness. Vibe 2.25.6+ bundles that runtime, but 2.25.7 still defaults to the legacy harness unless a rollout selects Unified or the user starts Vibe with --experimental-harness. Support must state and test this prerequisite rather than claim compatibility with the legacy backend.

Decision

Add a first-class vibe target to the AIDD CLI and emit native Agent Plugins 1.0 packages. Do not rely on Vibe's lossy Claude compatibility adapter and do not flatten all skills into .agents/skills/.

Scope: local Vibe CLI and the VS Code extension using the shared Vibe configuration/backend. Vibe Code Web is excluded until Mistral documents or exposes an equivalent repository plugin contract.

Acceptance criteria

vibe is a registered AI tool target with display name Mistral Vibe; CLI parsing, setup selection, recommendation/detection, install/update/sync/doctor/clean, translation, and help use the tool profile rather than tool-name branches.
Project scope materializes each selected plugin under .vibe/plugins/<plugin>/; user scope uses ~/.vibe/plugins/<plugin>/. Update, restore, and removal preserve unrelated user-owned files.
Each built plugin has a valid Agent Plugins 1.0 plugin.json; source name, version, description, author, license, and skills are preserved where representable.
All 51 current skills load with their directory/name invariant intact and remain explicitly invocable in Vibe.
checker and executor are converted to native ai.mistral.vibe/agents/*.toml subagents with their full instructions and deliberate tool/permission mappings.
Supported hook events map explicitly: PreToolUse to pre_tool, PostToolUse to post_tool, and Stop to post_agent. Hook commands receive a payload their scripts understand.
Unsupported SessionStart hooks are never silently dropped: build/install output names the affected plugin and skipped behavior. The ticket does not invent an approximate lifecycle mapping.
Project installation never writes Vibe's trust store. Output and doctor explain that project plugins remain inactive until the user trusts the folder.
Runtime guidance requires Vibe >=2.25.6 and Unified Harness; legacy-harness sessions are explicitly unsupported.
Automated tests cover path resolution and lifecycle behavior on Linux, macOS, and Windows. A package-level probe using current Vibe loads 8 plugins, 51 skills, 2 agents, all mapped hooks, and zero fatal diagnostics without requiring an API key.
CLI and VS Code documentation state the same support matrix; no Vibe Code Web support claim is added.

Out of scope

Vibe skill registry publishing or a marketplace service;
Vibe knowledge, libraries, or managed connectors, because AIDD currently ships none;
emulating SessionStart with a semantically different event;
support for Vibe's legacy harness.

feat(cli): add native Mistral Vibe plugin target

Evaluación

Línea de trabajo

Descripción

Problem

Investigation outcome (Vibe 2.25.7, 2026-09-23)

Decision

Acceptance criteria

Out of scope

Sources

Preparar el entorno

Primeros pasos

Más de ai-driven-dev/framework

Issues similares

feat(cli): add native Mistral Vibe plugin target

¿Algo no está bien?

Evaluación

Línea de trabajo

Descripción

Problem

Investigation outcome (Vibe 2.25.7, 2026-09-23)

Decision

Acceptance criteria

Out of scope

Sources

Preparar el entorno

Primeros pasos

Más de ai-driven-dev/framework

¿Algo no está bien?

¿Algo no está bien?

¿Algo no está bien?

¿Algo no está bien?

¿Algo no está bien?

Issues similares

¿Algo no está bien?

¿Algo no está bien?

¿Algo no está bien?

¿Algo no está bien?

¿Algo no está bien?

Recibe los nuevos issues en tu correo