ascendc-operator-dev

The workflow orchestrates end-to-end AscendC operator development by sequentially coordinating design, testcase generation, code generation, compilation, documentation, and evaluation across seven mandated phases.

The process for generating testcases and interface documentation uses mandated sub-skills within the development workflow to automatically generate and aggregate design docs, test cases, and interface documentation for full traceability.

No, the workflow enforces gate checks before progression across its seven phases, meaning you cannot skip phases even if you only need code generation without precision and performance evaluation.

To start the end-to-end operator development workflow, you need to provide the operator name and a brief description, which kicks off the sequential coordination from project initialization through to performance evaluation.

Unlike manually coding operators and writing documentation separately, this approach mandates invoking designated sub-skills for each phase and automatically aggregates generated documents and reports to ensure traceability.