What problem does it solve? Ascend C operator development workflows produce many intermediate deliverables (requirement docs, test plans, acceptance reports, operator docs, logs) that must follow consistent formats tied to workflow stage numbers. This Skill centralizes those templates so each deliverable starts from the correct format baseline instead of being improvised. ## Core Features & Use Cases - Stage-Numbered Template Index: Maps each deliverable to its workflow stage number (1.1 requirement analysis, 2.1 test plan, 2.2 dev plan, 3.4 joint-debug report, CP3/CP4/CP5 acceptance reports, 6.1 operator doc, 7.1/7.2 reports) with placeholder fields like {算子名称} to fill in. - Cross-Stage Templates: Provides shared templates for development logs (LOG) and issue records (Issue) used throughout the whole workflow. - Snapshot Refresh Rules: Defines which deliverables must be refreshed when operator code, precision criteria, or bottleneck analysis changes, keeping documents synchronized with implementation. - Use Case: When asked to produce a functional acceptance report for a BatchMatmulMaxSum operator, load the CP3 template first and fill its precision criteria tables and verdict sections. ## Quick Start Load the matching template from references/ before writing any requirement, test plan, acceptance report, or operator document deliverable.
