david.delagneau
8026da5719
- Introduced new commands and skills for workspace memory curation, professional communication, and status reporting. - Updated existing commands to utilize new skills and improve clarity in instructions. - Created a new workspace context command to load reusable core and active project profile. - Enhanced Mattermost inbox integration with support for generic environment variables. - Established a clear separation between project-independent core logic and project-specific profiles. - Improved documentation across various files to reflect changes in workflow and command usage. - Added operational memory management rules to ensure accurate context promotion and correction. - Updated README and workflow documents to guide users in utilizing the new structure effectively.
25 lines
905 B
Markdown
25 lines
905 B
Markdown
---
|
|
name: professional-communication
|
|
description: Rewrite rough technical notes into clear, concise, stakeholder-ready professional English while preserving scope and technical meaning.
|
|
compatibility: opencode
|
|
---
|
|
|
|
## When To Use
|
|
|
|
Use this skill for manager updates, stakeholder messages, translations, issue clarification, Jira comments, and communication polishing.
|
|
|
|
## Workflow
|
|
|
|
1. Identify audience, purpose, scope, and requested action.
|
|
2. Preserve technical meaning and uncertainty.
|
|
3. Make ownership, reproducibility, environment, and next action explicit when relevant.
|
|
4. Use Context, Observation, Action when it improves readability.
|
|
5. Avoid vague comparisons and generic progress language.
|
|
|
|
## Output Rules
|
|
|
|
- Write natural professional US English.
|
|
- Keep messages concise enough for workplace chat unless the user asks for a longer document.
|
|
- Do not invent facts, evidence, or commitments.
|
|
|