aitranslate

name: aitranslate description: AI Bilingual Translation skills — glossary init, translate deliverable, parity check, extend glossary, and more. Apply when the engagement scope includes ai bilingual translation work or the consultant references translate, translation, bilingual.

AITRANSLATE — AI Bilingual Translation

Capability overview

Code: AITRANSLATE Full name: AI Bilingual Translation Description: AI bilingual deliverables — domain glossary enforcement, AR/EN parity checks, terminology consistency.

Skills index

Skill 1: Glossary Init

Command: /cps-aitranslate:glossary-init

Purpose

Initialize domain glossary from existing deliverables; seed AR/EN pairs.

Inputs required

client:
  name: "Client Name"
  industry: "Industry"
context:
  scope: "in-scope description"
  constraints: ["constraint 1", "constraint 2"]
references:
  - "Prior deliverable / document name"
  - "External benchmark / source"

Methodology

1. Frame. Translate client request into a structured problem statement and hypotheses.
2. Gather. Pull data from engagement brain, client documents, and external sources.
3. Analyze. Apply the Glossary Init method using domain frameworks (see Frameworks section of the agent).
4. Synthesize. Produce primary deliverable with recommendations, evidence, and risks.
5. Validate. Run /cps:verify-quality and pass through Glossary coverage ≥90% (glossary-coverage hook enforces).

Output shape

A CPS-branded Glossary Init deliverable in 05_Deliverables_Final/. Pyramid-Principle structured, sourced, and reviewed.

Quality checklist

• Glossary coverage ≥90% (glossary-coverage hook enforces)
• Every translated deliverable has an EN side and AR side with matching structure
• New terms proposed for human approval before adding to glossary

Skill 2: Translate Deliverable

Command: /cps-aitranslate:translate

Purpose

Translate a deliverable to/from Arabic with glossary enforcement.

Inputs required

client:
  name: "Client Name"
  industry: "Industry"
context:
  scope: "in-scope description"
  constraints: ["constraint 1", "constraint 2"]
references:
  - "Prior deliverable / document name"
  - "External benchmark / source"

Methodology

1. Frame. Translate client request into a structured problem statement and hypotheses.
2. Gather. Pull data from engagement brain, client documents, and external sources.
3. Analyze. Apply the Translate Deliverable method using domain frameworks (see Frameworks section of the agent).
4. Synthesize. Produce primary deliverable with recommendations, evidence, and risks.
5. Validate. Run /cps:verify-quality and pass through Glossary coverage ≥90% (glossary-coverage hook enforces).

Output shape

A CPS-branded Translate Deliverable deliverable in 05_Deliverables_Final/. Pyramid-Principle structured, sourced, and reviewed.

Quality checklist

• Glossary coverage ≥90% (glossary-coverage hook enforces)
• Every translated deliverable has an EN side and AR side with matching structure
• New terms proposed for human approval before adding to glossary

Skill 3: Parity Check

Command: /cps-aitranslate:parity-check

Purpose

Verify AR/EN versions of a deliverable match on structure and key terms.

Inputs required

client:
  name: "Client Name"
  industry: "Industry"
context:
  scope: "in-scope description"
  constraints: ["constraint 1", "constraint 2"]
references:
  - "Prior deliverable / document name"
  - "External benchmark / source"

Methodology

1. Frame. Translate client request into a structured problem statement and hypotheses.
2. Gather. Pull data from engagement brain, client documents, and external sources.
3. Analyze. Apply the Parity Check method using domain frameworks (see Frameworks section of the agent).
4. Synthesize. Produce primary deliverable with recommendations, evidence, and risks.
5. Validate. Run /cps:verify-quality and pass through Glossary coverage ≥90% (glossary-coverage hook enforces).

Output shape

A CPS-branded Parity Check deliverable in 05_Deliverables_Final/. Pyramid-Principle structured, sourced, and reviewed.

Quality checklist

• Glossary coverage ≥90% (glossary-coverage hook enforces)
• Every translated deliverable has an EN side and AR side with matching structure
• New terms proposed for human approval before adding to glossary

Skill 4: Extend Glossary

Command: /cps-aitranslate:glossary-extend

Purpose

Propose new AR/EN term pairs from a draft document.

Inputs required

client:
  name: "Client Name"
  industry: "Industry"
context:
  scope: "in-scope description"
  constraints: ["constraint 1", "constraint 2"]
references:
  - "Prior deliverable / document name"
  - "External benchmark / source"

Methodology

1. Frame. Translate client request into a structured problem statement and hypotheses.
2. Gather. Pull data from engagement brain, client documents, and external sources.
3. Analyze. Apply the Extend Glossary method using domain frameworks (see Frameworks section of the agent).
4. Synthesize. Produce primary deliverable with recommendations, evidence, and risks.
5. Validate. Run /cps:verify-quality and pass through Glossary coverage ≥90% (glossary-coverage hook enforces).

Output shape

A CPS-branded Extend Glossary deliverable in 05_Deliverables_Final/. Pyramid-Principle structured, sourced, and reviewed.

Quality checklist

• Glossary coverage ≥90% (glossary-coverage hook enforces)
• Every translated deliverable has an EN side and AR side with matching structure
• New terms proposed for human approval before adding to glossary

Cross-skill workflows

Discovery → /cps-aitranslate:glossary-init → /cps-aitranslate:translate → Recommendations

Integration with other CPS plugins

Templates & artifacts

All deliverables use standard CPS branding via:

• /doc-gen for document generation
• assets/cps-branding.json for styling
• scripts/cps-document-generator.js for automation