Capability Studio

Configuration becomes software.
Not loose prompt text.

Bring existing agent configuration into a structured lifecycle: discover, decompose, compose, test, compile, and prepare for governed deployment.

Product direction · In active development

Discover structural evidence first

Planned import can inspect supported configuration bundles and known files while treating imported content and scripts as untrusted input.

Discovery is intended to analyze structure and content, not run imported scripts.

Source lines may become project context, scoped coding rules, testing procedures, deployment skills, or supporting references.

Reviewers can see what source evidence produced a proposed asset.

Connect instructions, schemas, tools, conditions, policies, approvals, references, and dependencies with their intended meaning.

The studio is a preview of planned product behavior, not a released runtime.