discuss-in-french
French Discussion, English Output
This skill guides the agent to conduct all conversations and clarifications with the user in French, while ensuring that all written outputs, including code, documentation, and issue text, are in English.
Process
1. Conduct discussion in French
- All questions, clarifications, and explanations addressed to the user must be written in French.
- The agent should engage naturally, asking for clarifications, confirming details, and discussing implementation in French.
2. Generate output in English
- Any output produced as a result of the discussion must be written entirely in English.
- This includes:
- Implementation instructions or code
- Documentation, issue descriptions, or templates
- Examples or summaries
3. Maintain the language separation
- Never switch the output language to French.
- Keep the conversation language and output language strictly separate.
4. Example
- User discussion: “Peux-tu préciser comment tu veux gérer la mise en page du frontend ?”
- Output: “The frontend layout will use a responsive grid system with components for each section. Buttons will follow the standard design system…”
More from sones3/skills
prd-to-issues
Break a PRD into independent GitHub issues, with backend-first then frontend-linked workflow. Each issue is fully discussed before implementation. Use when converting a PRD to actionable work items.
13grill-me
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
12write-a-prd
Create a business-focused PRD through user interview, repo exploration, and rigorous clarification, then review it with the user before submitting it as a GitHub issue. Use when the user wants to write a PRD, create a product requirements document, scope a feature, or plan a new capability.
11ubiquitous-language
Extract a DDD-style ubiquitous language glossary from the current conversation, flagging ambiguities and proposing canonical terms. Saves to UBIQUITOUS_LANGUAGE.md. Use when user wants to define domain terms, build a glossary, harden terminology, create a ubiquitous language, or mentions "domain model" or "DDD".
11start-next-issue
Suggests the next GitHub issue to work on from a PRD breakdown, confirms it with the user, and initiates the pre-implementation discussion.
10start-implementation
Implements a GitHub issue continuously until finished, documents the work and recommendations, commits, and closes the issue. Confirms the issue with the user only if it is not already in context.
8