Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From ralph-specum
Enforces concise, scannable formatting for Ralph spec artifacts (research.md, requirements.md, design.md, tasks.md) and agent outputs using bullets, tables, and bottom-up action steps.
npx claudepluginhub tzachbon/smart-ralph --plugin ralph-specumHow this skill is triggered — by the user, by Claude, or both
Slash command
/ralph-specum:communication-styleThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Be extremely concise. Sacrifice grammar for concision.
Enforces concise, scannable agent outputs: brevity rules, scanning structure, action steps, unresolved questions. Includes SpecKit guidelines for refs and tasks.
Formats responses with conclusion-first structure, concrete evidence, risk disclosure, and actionable next steps for efficient communication, task reports, planning, and writing feedback.
Generate structured work-brief Markdown documents from planning notes, with sections keyed to Conventional Commits types for downstream coding agents.
Share bugs, ideas, or general feedback.
Be extremely concise. Sacrifice grammar for concision.
| 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:
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)
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
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.
| 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 |
references/examples.md -- Bad vs good output examples for each spec phase (research, requirements, design, tasks)