skill-manifest

Skill: Extension Manifest Generator

Generates a handoff manifest at the end of the ALDC pipeline, enabling CIRCE and/or DELFOS to consume the extension's published surface without sharing a workspace.

Ecosystem context — CIRCE and DELFOS are sibling collections in the ALDC family: CIRCE provides AI agents for Microsoft Copilot Studio; DELFOS provides AI agents for Power BI. The manifest emitted by this skill is the contract those collections consume (through the Business Central MCP server) without sharing a workspace.

Trigger

This skill activates after the Conductor pipeline completes successfully (all sub-agents finalized, all HITL gates passed). The agent MUST NOT generate the manifest until the extension compiles and all tests pass.

The skill reads from:

1. The al-spec.md (or equivalent spec file) for the completed extension
2. The actual .al source files in the project directory
3. The app.json for publisher, version, and extension metadata

The skill outputs a single {extension-name}-manifest.md file in the project root or a designated output/ directory.

Interactive Gate (HITL — Required)

Before generating the manifest, the agent MUST ask the user:

The extension pipeline is complete. I can generate a handoff manifest
for consumption by other frameworks in the ecosystem.

Who will consume this manifest?

  (a) CIRCE — to build a Copilot Studio agent against this extension
  (b) DELFOS — to build a Power BI dashboard against this extension's data
  (c) Both CIRCE and DELFOS

Which option? (a / b / c)

The agent waits for the user's response. No manifest is generated without explicit selection.

If the user selects (c) Both, the agent generates a single unified manifest containing all sections for both targets, clearly labeled.

Additional Interactive Gate — CIRCE Connection Details

When the target includes CIRCE (options a or c), the agent MUST ask:

To generate the CIRCE connection section, I need your BC environment details: