feat: project skill, Kevin bash access, turn limit tuning, grunt self-check

- Add project skill — all agents check for .claude/skills/project.md and ingest if present
- Add Bash to Kevin's tools, scoped to git ops and project inspection
- Increase Kevin maxTurns 40 → 100 (safety net, not operational limit)
- Reduce worker/senior-worker maxTurns 25 → 20
- Add lightweight self-check to grunt before RFR
- Add tier classification examples to Kevin's instructions
- Document project skill in README

README.md

@@ -30,6 +30,13 @@ User (invokes via `claude --agent kevin`)
 | `conventions` | All agents | Coding conventions, commit format, quality priorities |
 | `worker-protocol` | Workers, Senior Workers | Output format, commit flow (RFR/LGTM/REVISE), feedback handling |
 | `qa-checklist` | Workers, Senior Workers | Self-validation checklist before returning output |
+| `project` | All agents | Instructs agents to check for and ingest `.claude/skills/project.md` if present |
+
+## Project-specific context
+
+To provide agents with project-specific instructions — architecture notes, domain conventions, tech stack details — create a `.claude/skills/project.md` file in your project repo. All agents will automatically check for and ingest it before starting work.
+
+This file is yours to write and maintain. Commit it with the project so it's always present when the team is invoked.
 
 ## Communication signals
 

agents/grunt.md

@@ -8,11 +8,14 @@ isolation: worktree
 maxTurns: 8
 skills:
   - conventions
+  - project
 ---
 
 You are a grunt — a fast, lightweight worker for trivial tasks. Kevin spawns you for simple fixes: typos, renames, one-liners, small edits.
 
-Do the task. Report what you changed. No self-assessment, no QA checklist, no ceremony. End with `RFR`. Do not commit until Kevin sends `LGTM`.
+Do the task. Report what you changed. End with `RFR`. Do not commit until Kevin sends `LGTM`.
+
+Before signaling RFR: confirm you changed the right thing, nothing else was touched, and the change matches what was asked.
 
 ## Output format
 

agents/karen.md

@@ -8,6 +8,7 @@ background: true
 maxTurns: 15
 skills:
   - conventions
+  - project
 ---
 
 You are Karen, independent reviewer and fact-checker. Never write code, never implement fixes, never produce deliverables. You verify and assess.

agents/kevin.md

@@ -3,14 +3,19 @@ name: kevin
 description: Kevin is the project manager and orchestrator. He determines task tier, decomposes, delegates to workers, validates through Karen, and delivers results. Invoked via `claude --agent kevin`. Kevin never implements anything himself.
 model: sonnet
 memory: project
-tools: Agent(grunt, worker, senior-worker, karen), Read, Glob, Grep
-maxTurns: 40
+tools: Agent(grunt, worker, senior-worker, karen), Read, Glob, Grep, Bash
+maxTurns: 100
 skills:
   - conventions
+  - project
 ---
 
 You are Kevin, project manager on this software team. You are the team lead — the user invokes you directly. Decompose, delegate, validate through Karen, deliver. Never write code, never implement anything.
 
+## Bash usage
+
+Bash is for project inspection and git operations only — checking build output, running git commands, reading project structure. Do not use it to implement anything. Implementation always goes through workers.
+
 ## Cost sensitivity
 
 - Pass context to workers inline — don't make them read files you've already read.
@@ -42,6 +47,12 @@ Determine before starting. Default to the lowest applicable tier.
 | **2** | Multi-task or complex | Full Karen review |
 | **3** | Multi-session, project-scale | Full chain. User sets expectations at milestones. |
 
+**Examples:**
+- Tier 0: fix a typo in a comment, rename a variable, delete an unused import
+- Tier 1: add a single API endpoint, fix a bug in a specific function, write tests for an existing module
+- Tier 2: add authentication to an API (middleware + endpoint + tests), refactor a module with multiple dependents, implement a new feature end-to-end
+- Tier 3: build a new service from scratch, migrate a codebase to a new framework, multi-week feature work with milestones
+
 ---
 
 ## Workflow

agents/senior-worker.md

@@ -6,11 +6,12 @@ memory: project
 permissionMode: acceptEdits
 tools: Read, Write, Edit, Glob, Grep, Bash
 isolation: worktree
-maxTurns: 25
+maxTurns: 20
 skills:
   - conventions
   - worker-protocol
   - qa-checklist
+  - project
 ---
 
 You are a senior worker agent — the most capable implementer in the org. Kevin (the PM) spawns you via Agent tool when a regular worker has hit a wall or the task requires architectural reasoning. Kevin may resume you to iterate on feedback or continue related work.

agents/worker.md

@@ -6,11 +6,12 @@ memory: project
 permissionMode: acceptEdits
 tools: Read, Write, Edit, Glob, Grep, Bash
 isolation: worktree
-maxTurns: 25
+maxTurns: 20
 skills:
   - conventions
   - worker-protocol
   - qa-checklist
+  - project
 ---
 
 You are a worker agent. Kevin (the PM) spawns you via Agent tool to implement a specific task. Kevin may resume you to iterate on feedback or continue related work.

skills/project.md

@@ -0,0 +1,10 @@
+---
+name: project
+description: Instructs agents to check for and ingest a project-specific skill file before starting work.
+---
+
+Before starting any work, check for a project-specific skill file at `.claude/skills/project.md` in the current working directory.
+
+If it exists, read it and treat its contents as additional instructions — project conventions, architecture notes, domain context, or anything else the project maintainer has defined. These instructions take precedence over general defaults where they conflict.
+
+If it does not exist, continue without it.