skills.rest
eventbalancer
eventbalancerCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

plan-translator

Translates finalized implementation plans into a target locale while preserving code tokens and structure.

9|Updated Jun 10, 2026
Search Tags:#documentation#markdown#mermaid#localization#translation#implementation plan#i18n
One-click install
npx skills add https://github.com/eventbalancer/agent-quorum --skill plan-translator-eventbalancer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan-translator
Source: https://github.com/eventbalancer/agent-quorum/tree/main/skills/plan-translator
Command: npx skills add https://github.com/eventbalancer/agent-quorum --skill plan-translator-eventbalancer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Finalized implementation plans are written in English, but distributed teams often need the same plan in their native language without losing the machine-validated references, identifiers, and structure that make the plan executable. ## Core Features & Use Cases - Faithful localization: Translates headings, prose, tables, and Mermaid Impact Graph labels into the requested BCP-47 locale while keeping the document structure identical. - Canonical token preservation: Keeps file paths, file:line references, code identifiers, shell commands, frontmatter, and coverage tables byte-for-byte unchanged. - Status fidelity: Preserves the plan's clean or needs-review status and all convergence identifiers exactly. - Use Case: After agent-quorum produces a finalized English plan, render a Russian or Portuguese companion plan that engineers in that locale can execute against the same codebase. ## Quick Start Translate the finalized plan.final.md into the requested locale, keeping all code tokens, paths, and the frontmatter unchanged.

Frequently Asked Questions about plan-translator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I translate an implementation plan into another language?▼

Provide the finalized plan text along with a target locale tag such as ru or pt-BR. The output is the full localized markdown plan with headings, prose, and diagram labels translated while code tokens stay unchanged.

What parts of the plan are never translated?▼

File paths, file:line references, code identifiers, shell commands, environment variables, JSON/YAML keys, version strings, inline code, and fenced code content stay byte-for-byte identical. The YAML frontmatter and System Coverage table are also copied verbatim.

Does the translation change the Mermaid Impact Graph structure?▼

No. Node ids, arrows, subgraph keywords, and graph directives remain exactly as-is, and no nodes or edges are added, removed, or reordered. Only the human-readable label text inside brackets or on edges is translated.

Can the translator fix or improve plan content during translation?▼

No. It performs translation only, never a rewrite, review, or improvement. Heading hierarchy, section order, tables, and bullets must match the source exactly, even if a flaw is spotted.

What output format does the plan translation produce?▼

The output is plain markdown text starting with the YAML frontmatter block, with no JSON wrapper and no enclosing code fence. The translated title follows the frontmatter and the Impact Graph ends the document.

Related Skills

Explore More Software Engineering Skills→
AGMO-IncAGMO-Inc
4

plan-review

Validate plans through iterative critic reviews and acceptance criteria.

Official
Advanced
lossyroblossyrob
39

paw-code-research

Document codebase component interactions with exact file:line references.

Community
Basic
Fr-e-dFr-e-d
157

i18n-glossary-sync

Synchronize locale files with a markdown glossary and flag missing translations.

Community
Advanced
musical-basicsmusical-basics

outlines

Constrain token generation with grammars and finite state machines for valid JSON, XML, and code outputs.

Community
Advanced