Skip to content
cccskills
FreePublished on GitHub

communication-style

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

The English summary is being prepared. Showing the original description.

tzachbon/smart-ralph
See how to install

Files included (1)

  • SKILL.md2.7 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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 ofWrite
"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

ALWAYS end with numbered concrete steps.

## Next Steps

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

This is the LAST thing visible in terminal. Most important = most visible.

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'tDo
Long prose explanationsBullet points
Nested sub-bullets (3+ levels)Flat structure, tables
"Let me explain..."(just explain)
Repeating contextReference by ID
Hedging languageDirect statements

Examples

Bad (verbose)

The authentication system will need to handle user login
functionality. In order to accomplish this, we will need
to implement a JWT-based authentication mechanism that
allows users to securely log in to the application.

Good (concise)

Auth system: JWT-based login

Components:
- Login endpoint: POST /auth/login
- Token generation: JWT with 24h expiry
- Middleware: verify token on protected routes

SpecKit-Specific Guidelines

Constitution References

Use markers, not prose:

  • [C§3.1] not "as defined in constitution section 3.1"
  • [MUST] not "this is required by our principles"

User Story References

Use IDs:

  • [US1] not "the first user story about..."
  • T001 [US1] links task to story

Task Descriptions

Include file path inline:

  • Add auth middleware \src/middleware/auth.ts``
  • Not "Create a new file called auth.ts in the middleware folder"

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Command Development

Free

This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.

The English summary is being prepared. Showing the original description.

tzachbon/smart-ralph559Updated Sep 16, 2026

communication-style

Free

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.

The English summary is being prepared. Showing the original description.

tzachbon/smart-ralph559Updated Sep 16, 2026

delegation-principle

Free

Core principle that the main agent is a coordinator, not an implementer. All work must be delegated to subagents.

The English summary is being prepared. Showing the original description.

tzachbon/smart-ralph559Updated Sep 16, 2026

Hook Development

Free

This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.

The English summary is being prepared. Showing the original description.

tzachbon/smart-ralph559Updated Sep 16, 2026

interview-framework

Free

This skill should be used when a Ralph phase must identify critical user decisions, run a layered grill, persist partial answers, obtain explicit approval, or resume an interrupted phase interview before delegating artifact work.

The English summary is being prepared. Showing the original description.

tzachbon/smart-ralph559Updated Sep 16, 2026

interview-framework-codex

Free

Internal Ralph Specum contract for Codex phase interviews, skill manifests, approval, and delegation gates. Phase coordinators load this skill directly; users do not invoke it as a workflow phase.

The English summary is being prepared. Showing the original description.

tzachbon/smart-ralph559Updated Sep 16, 2026

See all skills by tzachbon

Report a problem with this skill