From ralph-speckit
Enforces concise, scannable agent outputs: brevity rules, scanning structure, action steps, unresolved questions. Includes SpecKit guidelines for refs and tasks.
npx claudepluginhub tzachbon/smart-ralph --plugin ralph-speckitThis skill uses the workspace's default tool permissions.
**Be extremely concise. Sacrifice grammar for concision.**
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.
Enforces extreme brevity and signal-over-noise in outputs by cutting filler, repetition, and meta-commentary. Auto-triggers on every response for dense docs, updates, and conversations.
Provides standardized Markdown templates for research, planning, implementation, and review agent outputs. Use when generating or parsing agent responses in autonomous dev workflows.
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)
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.
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 |
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.
Auth system: JWT-based login
Components:
- Login endpoint: POST /auth/login
- Token generation: JWT with 24h expiry
- Middleware: verify token on protected routes
Use markers, not prose:
[C§3.1] not "as defined in constitution section 3.1"[MUST] not "this is required by our principles"Use IDs:
[US1] not "the first user story about..."T001 [US1] links task to storyInclude file path inline:
Add auth middleware \src/middleware/auth.ts``