Skip to content

Make required skills and tool integrations usable in native channels #56

Description

@iamnbutler

Native channels load root AGENTS/CLAUDE instructions and discover repository skills/rules. #27 adds composer selection; it does not provide user-level/plugin skills, linked resources, custom-agent execution, or tools required by a skill. External-harness hosting (#9) also cannot assume that its ambient integrations transfer.

Acceptance

  • Inventory the concrete skills and integrations used for Ace work, including lane/review workflows, React Doctor, and documentation research.
  • Resolve the intended instructions and linked resources relative to the correct lane/source, and invoke their required commands/tools.
  • Make unavailable capabilities explicit instead of advertising an unusable skill or silently changing its behavior.
  • Support the selected custom-agent and instruction-discovery semantics, with source/precedence visible and preserved across continuation.
  • Demonstrate a real selected skill and a cited primary-document research workflow, with results retained in Ace.

A supported shell route can satisfy a workflow. Do not turn this into blanket compatibility with every installed plugin or MCP server. Browser tooling has its own issue; #26 owns non-image input.

Related: #9, #27. This is broader integration work, not a blanket dogfooding MVP gate. Review evidence.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions