feat: add comprehensive agent rules and workflows for memory curation, communication synchronization, and project documentation management
This commit is contained in:
@@ -1,24 +0,0 @@
|
||||
---
|
||||
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.
|
||||
|
||||
1
.opencode/skills/professional-communication/SKILL.md
Symbolic link
1
.opencode/skills/professional-communication/SKILL.md
Symbolic link
@@ -0,0 +1 @@
|
||||
../../../.agents/rules/professional-communication.md
|
||||
Reference in New Issue
Block a user