Skip to content

Decide whether AgentV should become a component submodule #24

Description

@smota

Parent epic: #18

Goal

Decide whether to add AgentV as a components/ submodule after docs/templates prove useful.

Initial recommendation

Do not vendor AgentV source in phase 1. Start with toolsets/agentv/ docs/templates only.

If deeper integration becomes necessary, add components/agentv as:

  • reference-only first, or
  • tool-provider only if MetaSkills scripts intentionally call AgentV from submodule.

Acceptance criteria

  • Decision recorded in docs or ADR.
  • If submodule is added, include components/agentv.metaskills.md with mode and rationale.
  • Native assets must not require reference-only component at install/runtime.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestroadmapRoadmap planning and execution

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions