communication-style

仓库创建 2026年1月12日最近提交 4 天前SkillHot 收录 20 天前

▸ 精选理由

显著提升生成文本的可读性与执行性，适合所有任务型代理。

这个 Skill 做什么

定义代理输出的简洁、可扫描、可操作化的沟通风格规则。

为所有代理输出制定一套极简、可扫描、可执行的沟通规则，强调短句、要点化和可操作步骤，参考 Matt Pocock 的规划原则。用在需要统一团队或 agent 输出风格时，确保说明和计划不是长篇大论而是便于快速查阅。核心原则是优先简洁（Brevity First），宁可牺牲语法也要保证可扫读性和效率。

▸ 展开 SKILL.md 英文原文

Output rules for all agents - concise, scannable, actionable. Based on Matt Pocock's planning principles.

Skill 开发管理沟通风格简洁可扫描Claude Code

431

Stars

Forks

仓库内 Skill

+16

7 日增星

安装 / 使用

给你的 Agent 一句话（通用）

帮我安装这个 skill：https://raw.githubusercontent.com/tzachbon/smart-ralph/main/plugins/ralph-speckit/skills/communication-style/SKILL.md

或 curl 直取 SKILL.md

curl -fsSL "https://raw.githubusercontent.com/tzachbon/smart-ralph/main/plugins/ralph-speckit/skills/communication-style/SKILL.md"

SKILL.MD 节选查看完整文件 ↗

# Communication Style

## Core Rule

**Be extremely concise. Sacrifice grammar for concision.**

## Why

- Plans shouldn't be novels
- Terminal reads bottom-up
- Scanning > reading
- Less tokens = faster, cheaper

## Output Rules

### 1. Brevity First

| Instead of | Write |
|------------|-------|
| "The user will be able to..." | "User can..." |
| "This component is responsible for..." | "Handles..." |
| "In order to achieve this, we need to..." | "Requires:" |
| "It should be noted that..." | (delete) |

**Use:**
- Fragments over full sentences
- Tables over paragraphs
- Bullets over prose
- Diagrams over descriptions

### 2. Structure for Scanning

Every output follows this order:

```tex

via SKILL·HOT · 数据来自 GitHub 公开信息 · 原文版权归作者所有