Skip to content

Phase 4: Add CLI composition flows (corvus agent build/run/new) #481

@yacosta738

Description

@yacosta738

Parent epic: DALLAY-249
Source of truth: tmp/PRD-Capability-Based-Architecture-for-Composable-AI-Agents.md

Phase 4: Add CLI composition flows (corvus agent build/run/new)

Objective

Expose manifest-driven agent composition through first-class CLI commands.

Scope

  • add corvus agent build --manifest ...
  • add corvus agent run --manifest ...
  • add corvus agent new --template ... --name ...
  • connect CLI flows to manifest validation and AgentComposer
  • provide useful operator-facing errors for invalid manifests or missing capabilities

Acceptance Criteria

  • users can validate, build, and run an agent from a manifest through the CLI
  • template-based scaffolding works for initial agent creation
  • CLI output is clear enough to diagnose missing capability or platform issues
  • targeted command-level tests cover the main flows where practical

Notes

This phase turns the architecture into a usable developer workflow.

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions