// engine/universal-rules/rules/planu-english-specs.ts — Universal rule: specs are written in English
function buildBody() {
    return `# Planu Artifacts Must Be Written in English

Auto-generated by \`init_project\`. Do not edit manually.

## Rule

All generated Planu-owned artifacts are written in English, regardless of the user's conversation language:

- \`spec.md\`
- Planu skills, including \`SKILL.md\` and host-adapted skill blocks
- Planu agent instructions, including \`AGENTS.md\`, \`CLAUDE.md\`, \`GEMINI.md\`, and host-specific sections
- Planu rules, including \`.claude/rules/*.md\`, Codex rule blocks, and Gemini conventions
- inline \`## Technical\`, \`## Files\`, and \`## Progress\` sections
- acceptance criteria, implementation notes, validation notes, and reconciliation notes

User-facing chat may use the user's preferred language. The persisted Planu contract stays in English so every agent, tool, and CI gate can parse it consistently.

## Hard Blocks

- Do not create mixed-language acceptance criteria.
- Do not translate BDD keywords.
- Do not generate Planu-owned skills, agents, or rules in Spanish, Portuguese, or mixed language.
- Do not create standalone \`technical.md\`, \`progress.md\`, \`HU.md\`, \`FICHA-TECNICA.md\`, or \`PROGRESS.md\`.
- Do not approve a spec that contains unresolved placeholders such as \`to be determined\`, \`TBD\`, \`TODO\`, or equivalent filler.
`;
}
export const planuEnglishSpecsRule = {
    id: 'planu-english-specs',
    name: 'Planu English Artifacts',
    description: 'Requires Planu spec, skill, agent, and rule artifacts to be written in English.',
    category: 'quality',
    applicableHosts: ['all'],
    defaultEnabled: true,
    buildContent: (_host) => buildBody(),
};
//# sourceMappingURL=planu-english-specs.js.map