{"id":"communication-style","name":"communication-style","summary":"すべてのエージェントに対する出力ルール - 簡潔でスキャン可能、実行可能。マット・ポコックの計画原則に基づいています。","body":"# Communication Style\n\n## Core Rule\n\n**Be extremely concise. Sacrifice grammar for concision.**\n\n## Why\n\n- Plans shouldn't be novels\n- Terminal reads bottom-up\n- Scanning > reading\n- Less tokens = faster, cheaper\n\n## Output Rules\n\n### 1. Brevity First\n\n| Instead of | Write |\n|------------|-------|\n| \"The user will be able to...\" | \"User can...\" |\n| \"This component is responsible for...\" | \"Handles...\" |\n| \"In order to achieve this, we need to...\" | \"Requires:\" |\n| \"It should be noted that...\" | (delete) |\n\n**Use:**\n- Fragments over full sentences\n- Tables over paragraphs\n- Bullets over prose\n- Diagrams over descriptions\n\n### 2. Structure for Scanning\n\nEvery output follows this order:\n\n```text\n1. Brief overview (2-3 sentences MAX)\n2. Main content (tables, bullets, diagrams)\n3. Unresolved questions (if any)\n4. Numbered action steps (ALWAYS LAST)\n```\n\n### 3. End with Action Steps\n\n**ALWAYS** end with numbered concrete steps.\n\n```markdown\n## Next Steps\n\n1. Create auth module at src/auth/\n2. Add JWT dependency\n3. Implement login endpoint\n4. Add tests\n```\n\nThis is the LAST thing visible in terminal. Most important = most visible.\n\n### 4. Surface Questions Early\n\nBefore action steps, list unresolved questions:\n\n```markdown\n## Unresolved Questions\n\n- OAuth provider preference? (Google, GitHub, both)\n- Session duration requirement?\n- Rate limiting needed?\n```\n\nCatches ambiguities before they become bugs.\n\n## Anti-Patterns\n\n| Don't | Do |\n|-------|-----|\n| Long prose explanations | Bullet points |\n| Nested sub-bullets (3+ levels) | Flat structure, tables |\n| \"Let me explain...\" | (just explain) |\n| Repeating context | Reference by ID |\n| Hedging language | Direct statements |\n\n## Examples\n\n### Bad (verbose)\n\n```text\nThe authentication system will need to handle user login\nfunctionality. In order to accomplish this, we will need\nto implement a JWT-based authentication mechanism that\nallows users to securely log in to the application.\n```\n\n### Good (concise)\n\n```text\nAuth system: JWT-based login\n\nComponents:\n- Login endpoint: POST /auth/login\n- Token generation: JWT with 24h expiry\n- Middleware: verify token on protected routes\n```\n\n## SpecKit-Specific Guidelines\n\n### Constitution References\n\nUse markers, not prose:\n- `[C§3.1]` not \"as defined in constitution section 3.1\"\n- `[MUST]` not \"this is required by our principles\"\n\n### User Story References\n\nUse IDs:\n- `[US1]` not \"the first user story about...\"\n- `T001 [US1]` links task to story\n\n### Task Descriptions\n\nInclude file path inline:\n- `Add auth middleware \\`src/middleware/auth.ts\\``\n- Not \"Create a new file called auth.ts in the middleware folder\"","author":"@tzachbon","ownerProfile":null,"authorContacts":null,"sourceUrl":"https://github.com/tzachbon/smart-ralph/tree/main/plugins/ralph-speckit/skills/communication-style","license":"MIT","category":"writing","lang":"en","tokens":653,"stars":0,"calls30d":1,"claimed":false,"visibility":"public","origin":"crawler","version":"0.1.0","createdAt":"2026-08-22","updatedAt":"2026-08-22","files":[],"requires":{"mcp":[],"tools":[]},"safety":{"flags":[],"scannedAt":"2026-08-22","hasScripts":false,"networkEndpoints":[]}}