skill-manifest

To generate an Extension Manifest for ALDC workflows, run the manifest generator after a successful extension build. It consumes al-spec.md, compiled AL objects, and app.json to produce a standardized {extension-name}-manifest.md file.

An ALDC Extension Manifest is a standardized file communicating an extension's surface to downstream frameworks like CIRCE and DELFOS. You need it after the Conductor pipeline completes to ensure consistent metadata distribution and reduce manual handoff errors.

Yes, the manifest generator supports producing separate CIRCE, DELFOS, or combined manifests. You can select the target to generate either a single unified manifest file or distinct manifests depending on your downstream framework requirements.

Before generating the ALDC manifest, the generator validates the presence and references of al-spec.md, compiled AL objects, and app.json. Ensuring these inputs are present finalizes the manifest with proper repository metadata and AL object references.

The ALDC extension manifest file is placed in the project root or an output/ directory after generation. The generator automatically names the file {extension-name}-manifest.md for streamlined handoffs in CI/CD pipelines.

Yes, you can use the manifest generator in CI/CD pipelines for ALDC extensions. Running it after a successful extension build streamlines handoffs by automatically producing a validated manifest with proper spec references and repository metadata.