Localization qa
Skill planifest/planifest-framework/planifest-framework/external-skills/localization-qa
A specification framework for agentic development. Agents build from complete specs - not guesses.
npx -y skills add planifest/planifest-framework --skill localization-qaAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Localization QA workflow for language correctness, layout resilience, and locale-specific behavior validation before release. Use when localized UI/content must be verified across target locales; do not use for backend data-model or deployment pipeline decisions.
SKILL.md
2.2 KB, as published. Nobody here has run it
Localization Qa
Overview
Use this skill to verify that localized experiences remain correct, usable, and release-safe across required locales.
Scope Boundaries
- Use this skill when the task matches the trigger condition described in
description. - Do not use this skill when the primary task falls outside this skill's domain.
Shared References
- Localization defect severity rules:
references/localization-defect-severity-rules.md
Templates And Assets
- Locale QA report template:
assets/localization-qa-report-template.csv
- Localization regression checklist:
assets/localization-regression-checklist.md
Inputs To Gather
- Required locale list and release scope.
- Localized strings, glossary, and style rules.
- UI builds/config for locale switching.
- Critical flows and compliance-sensitive copy.
Deliverables
- Locale-by-locale defect report with severity and ownership.
- Regression verification evidence for critical flows.
- Release recommendation with blocker summary.
- Follow-up retest plan for unresolved issues.
Workflow
- Confirm locale coverage and build readiness.
- Validate language and terminology correctness.
- Stress-test layout expansion/truncation/wrapping behavior.
- Validate locale formatting and directional behavior.
- Record findings in
assets/localization-qa-report-template.csvand close withassets/localization-regression-checklist.md.
Quality Standard
- Required locales are fully covered.
- Critical flows pass with no blocker-level localization defects.
- Severity reflects user/business impact across locales.
- Defect ownership and retest status are explicit.
Failure Conditions
- Stop release recommendation when required locale coverage is incomplete.
- Stop when blocker-level semantic or layout defects remain unresolved.
- Escalate when localization defects affect legal/compliance-critical content.