## Problem
Planner and Orchestrator agents add "Files to Create" and "Files to Modify" sections to tickets. This constrains worker agents - they only touch the listed files and don't think about broader scope.
**Example:**
If ticket says "Files to modify: agents.rb" but the change also requires updating `mcp-bridge/src/tools/index.ts`, the worker won't touch the MCP bridge file because it's not listed.
**Root Cause:**
Agents interpret "Files to Modify" as an **exhaustive list** rather than a **starting point**. They don't think "what else might need changing?" - they just execute on the specified files.
## Solution
**Planner and Orchestrator must NEVER add:**
- "Files to Create" sections
- "Files to Modify" sections
**Instead:**
- Describe the **outcome** required
- Let the worker agent figure out **which files** need to change
- Agent should explore the codebase and identify all affected files
### Example - Bad (Current)
```markdown
## Files to Modify
- agents.rb
## Files to Create
- .claude/skills/memory/SKILL.md
```
Worker thinks: "Only edit agents.rb and create that one file."
Result: Misses updating mcp-bridge/src/tools/index.ts, mcp_permissions.yml
### Example - Good (Fixed)
```markdown
## What You're Building
A memory skill that agents can use to store and retrieve knowledge. The skill should:
- Be discoverable by Claude Code runtime
- Expose search_memory and store_memory tools
- Be assigned to all agent types
## Technical Notes
Skills live in `.claude/skills/<name>/SKILL.md` and are assigned via `skills: []` array in agents.rb. MCP tools must be registered in mcp-bridge and permissions set in mcp_permissions.yml.
```
Worker thinks: "What files do I need to touch to accomplish this?"
Result: Explores codebase, finds all the files that need updating.
## Updated Agent Instructions
Add to Planner/Orchestrator banners:
```markdown
## TICKET CREATION RULES
❌ DO NOT list "Files to Create" or "Files to Modify"
❌ DO NOT specify exact file paths
✅ DO describe the desired outcome
✅ DO provide context and constraints
✅ DO let workers discover which files need changes
Why: File lists constrain thinking. Workers stop exploring and only touch listed files, missing related changes.
```
## Acceptance Criteria
1. Planner banner updated with "no file lists" rule
2. Orchestrator banner updated with "no file lists" rule
3. Future tickets describe outcomes, not file lists
4. Review tickets to ensure no file listing sections exist
## Problem
Planner and Orchestrator agents add "Files to Create" and "Files to Modify" sections to tickets. This constrains worker agents - they only touch the listed files and don't think about broader scope.
**Example:**
If ticket says "Files to modify: agents.rb" but the change also requires updating `mcp-bridge/src/tools/index.ts`, the worker won't touch the MCP bridge file because it's not listed.
**Root Cause:**
Agents interpret "Files to Modify" as an **exhaustive list** rather than a **starting point**. They don't think "what else might need changing?" - they just execute on the specified files.
## Solution
**Planner and Orchestrator must NEVER add:**
- "Files to Create" sections
- "Files to Modify" sections
**Instead:**
- Describe the **outcome** required
- Let the worker agent figure out **which files** need to change
- Agent should explore the codebase and identify all affected files
### Example - Bad (Current)
```markdown
## Files to Modify
- agents.rb
## Files to Create
- .claude/skills/memory/SKILL.md
```
Worker thinks: "Only edit agents.rb and create that one file."
Result: Misses updating mcp-bridge/src/tools/index.ts, mcp_permissions.yml
### Example - Good (Fixed)
```markdown
## What You're Building
A memory skill that agents can use to store and retrieve knowledge. The skill should:
- Be discoverable by Claude Code runtime
- Expose search_memory and store_memory tools
- Be assigned to all agent types
## Technical Notes
Skills live in `.claude/skills/<name>/SKILL.md` and are assigned via `skills: []` array in agents.rb. MCP tools must be registered in mcp-bridge and permissions set in mcp_permissions.yml.
```
Worker thinks: "What files do I need to touch to accomplish this?"
Result: Explores codebase, finds all the files that need updating.
## Updated Agent Instructions
Add to Planner/Orchestrator banners:
```markdown
## TICKET CREATION RULES
❌ DO NOT list "Files to Create" or "Files to Modify"
❌ DO NOT specify exact file paths
✅ DO describe the desired outcome
✅ DO provide context and constraints
✅ DO let workers discover which files need changes
Why: File lists constrain thinking. Workers stop exploring and only touch listed files, missing related changes.
```
## Acceptance Criteria
1. Planner banner updated with "no file lists" rule
2. Orchestrator banner updated with "no file lists" rule
3. Future tickets describe outcomes, not file lists
4. Review tickets to ensure no file listing sections exist