extension-manifest

To generate a handoff manifest for CIRCE and DELFOS, run the extension-manifest skill after the ALDC pipeline completes successfully. It reads from spec files, source files, and metadata, then requires user interaction to select target consumers and provide connection details before outputting the final manifest.

An extension handoff manifest enables systems like CIRCE and DELFOS to consume an extension's published surface without sharing a workspace. You need this manifest at the end of the ALDC pipeline when you want to hand off compiled extension data to downstream consumers like Copilot Studio agents.

No, manifest generation requires the Conductor pipeline to complete successfully before running. The skill reads from spec files, source files, and metadata produced by the pipeline, so a failed build will not provide the valid inputs needed to output the CIRCE and DELFOS manifest sections.

Creating a handoff manifest requires spec files, source files, and metadata from the completed ALDC pipeline. During the process, user interaction is required to select target consumers and provide connection details, which are then structured into headers, CIRCE and DELFOS sections, and a footer.

Manifest generation requires user interaction to select target consumers and provide connection details for CIRCE and DELFOS. This ensures the output manifest correctly routes the extension's published surface to the appropriate downstream systems without workspace sharing.

The main limitation is dependency on successful ALDC pipeline completion; the manifest cannot be generated without valid spec files, source files, and metadata. Additionally, the required user interaction for target selection and connection details prevents fully automated, headless manifest generation.