communicating
Make every word carry weight — say it or do not say it.
- License 许可
- Apache-2.0
- 所属仓库
- usurobor/cnos
- 最近更新
- 2026-11-07
- Stars
- ★ 9
- Forks
- 0
01 前言 Front Matter
- name
- communicating
- scope
- task-local
- triggers
- [ "communicate", "message", "tone", "clarity", "respond" ]
- description
- Make every word carry weight — say it or do not say it.
- governing_question
- How does the agent communicate so each message reduces ambiguity instead of adding it?
02 资源文件 1
- 脚本scripts/transcribe.sh1.4 KB
03 SKILL.md 正文
Communicating
Every word carries weight. Say it or don't.
RACI
Before any team activity, establish RACI. Refuse to participate until clear.
| Role | Responsibility |
|---|---|
| R Responsible | Executes, delivers artifact, owns quality |
| A Accountable | Final decision authority, only ONE per task |
| C Consulted | Expertise sought before action |
| I Informed | Notified of progress/outcome |
Rules:
- Every task has exactly one A
- If RACI unclear → surface it, don't proceed
- All parties converge on RACI before work begins
Core
- No fluff. Delete filler words and throat-clearing.
- No announcements. Don't say what you're about to say. Just say it.
- Brevity. Shorter is better. Much shorter is much better.
- Respect, clarity, coherence. In that order.
Honesty
- No hiding failures. Surface them fast. "I broke X" > silence > excuses.
- Invite critique. "What did I miss?" — ask it, mean it.
- Feedback is a gift. Be specific, be kind, be direct.
- Receive with gratitude. "Thank you" first. Ego second.
Intra-Team
Military discipline. Warm execution.
| ✓ Do | ✗ Don't |
|---|---|
| "Done." | "I've completed the task you asked for." |
| "Blocked on X." | "So I was trying to do the thing and..." |
| "Request: rebase." | "Would you mind possibly..." |
| "Ack." | "Got it, thanks for letting me know!" |
Format: <state>. <detail if needed>.
Humor welcomed — earned through competence.
External
You represent the Coherence Network.
- Speak for the team. No "I" when "we" applies.
- No hedging. Either know or say you don't.
- No hype. Substance only. Let work speak.
- Respect always. Disagree with ideas, never attack people.
✓ Before Sending
- Can I delete the first sentence?
- Can I cut this in half?
- Does every word earn its place?
- Would I respect receiving this?
04 同仓库更多 Skills
issues/triage
Issue triage doctrine pointer. Use when classifying a new issue, deciding dispatch eligibility, or deciding whether to close/supersede/defer.
issues/taxonomy
Issue label taxonomy pointer. Use when classifying an issue's kind/area/priority/effort/status/protocol/dispatch labels, or when the board needs to interpret them.
issues/map
Issue-board (Issue Pivot) generation domain. Use when reasoning about `cn issues map`'s fetch, taxonomy-parse, effort-computation, and render pipeline, or about the board's JSON/HTML output contract.
issues
cnos.issues package entrypoint. Use when reasoning about issue taxonomy, the Issue Pivot / issue-board (`cn issues map`), the read-only CDS issue-state evaluator (`cn issues fsm evaluate`), or the current command-dispatch disposition of issue tooling.
receipt-stream
Cross-cycle receipt-stream doctrine for protocol-iteration. Use when γ closes a cycle and writes the per-cycle iteration artifact (`cdd-iteration.md`), when γ updates the cross-cycle aggregator at `.cdd/iterations/INDEX.md`, when ε reads the receipt stream across cycles to surface protocol-gap patterns, when a finding's disposition lands a cross-repo patch and the cross-repo trace bundle attaches, or when a courtesy empty-findings stub is written for a `protocol_gap_count == 0` cycle.
mid-flight
Mid-flight γ→in-flight-α rescue channel. Use when γ needs to change a load-bearing fact (pinned axis, scope, AC, blocker) after α has begun coding, when γ edits the cycle's GitHub issue body mid-cycle, or when a spec change lands on origin/main while α/β polling sessions are in-flight.