Menu
Output rules for all agents - concise, scannable, actionable. Based on Matt Pocock's planning principles.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | communication-style |
| description | Output rules for all agents - concise, scannable, actionable. Based on Matt Pocock's planning principles. |
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
How to delegate implementation tasks to workers via Codex MCP or Task sub-agents. Use when executing tasks that require code implementation.
Core principle that the main agent is a coordinator, not an implementer. All work must be delegated to subagents.
Detect fix vs add goals, diagnose failures before work, verify fixes after. Ensures "fix X" specs actually fix X.
Spec-driven development workflow for building features with research, requirements, design, and task phases
Criteria for reviewing Codex worker outputs across 5 dimensions. Use when reviewing code submitted by workers before approval.
4-layer verification system for task completion. Use when verifying that a task has been fully completed before marking it done.