Agent Skills › tzachbon/smart-ralph › communication-style

communication-style

GitHub

规范Ralph Agent输出风格，要求极致简洁、碎片化表达。规定输出结构：概述、主体、未决问题、行动步骤（置于末尾以便自下而上阅读）。旨在降低Token成本，提升终端扫描效率，适用于所有规格说明阶段。

plugins/ralph-specum/skills/communication-style/SKILL.md tzachbon/smart-ralph

触发场景

生成spec artifacts (research.md, requirements.md等) 格式化Agent输出结果结构化各阶段产出内容需要指导如何生成简洁可扫描的文本时

安装

npx skills add tzachbon/smart-ralph --skill communication-style -g -y

更多选项

非标准路径

npx skills add https://github.com/tzachbon/smart-ralph/tree/main/plugins/ralph-specum/skills/communication-style -g -y

不安装直接使用

npx skills use tzachbon/smart-ralph@communication-style

指定 Agent (Claude Code)

npx skills add tzachbon/smart-ralph --skill communication-style -a claude-code -g -y

安装 repo 全部 skill

npx skills add tzachbon/smart-ralph --all -g -y

预览 repo 内 skill

npx skills add tzachbon/smart-ralph --list

SKILL.md

Frontmatter

{
    "name": "communication-style",
    "version": "0.2.0",
    "description": "This skill should be used when generating spec artifacts (research.md, requirements.md, design.md, tasks.md), formatting agent output, structuring phase results, or when any Ralph agent needs guidance on concise, scannable output formatting. Applies to all Ralph spec phase agents.",
    "user-invocable": false
}

Communication Style

Be extremely concise. Sacrifice grammar for concision.

Rationale

Plans should not be novels
Terminal reads bottom-up
Scanning beats reading
Fewer 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:

1. Brief overview (2-3 sentences MAX)
2. Main content (tables, bullets, diagrams)
3. Unresolved questions (if any)
4. Numbered action steps (ALWAYS LAST)

3. End with Action Steps

Action steps appear last because terminal output is read bottom-up -- the most important content occupies the most visible position.

## Next Steps

1. Create auth module at src/auth/
2. Add JWT dependency
3. Implement login endpoint
4. Add tests

4. Surface Questions Early

Before action steps, list unresolved questions:

## Unresolved Questions

- OAuth provider preference? (Google, GitHub, both)
- Session duration requirement?
- Rate limiting needed?

Catches ambiguities before they become bugs.

Anti-Patterns

Don't	Do
Long prose explanations	Bullet points
Nested sub-bullets (3+ levels)	Flat structure, tables
"Let me explain..."	(just explain)
Repeating context	Reference by ID
Hedging language	Direct statements