[projman] Sprint planning approval should grant execution permissions #233

Closed
opened 2026-01-28 15:21:57 +00:00 by lmiranda · 0 comments
Owner

Problem

User approves sprint items during /sprint-plan, but agents still need individual tool permissions during /sprint-start. This creates friction and defeats the purpose of upfront approval.

User feedback: "I dont want to give you permissions for doing something we already stressed by reviewing. How can we have this happening without my approval?"

Current Behavior

  1. User reviews and approves 26 items during sprint planning
  2. Sprint starts, agents are dispatched
  3. Agents immediately hit permission blocks (Write, Edit, Bash)
  4. User has to manually add permissions to settings.local.json
  5. Agents need to be restarted

Expected Behavior

  • Sprint planning generates a permissions manifest
  • User approves the manifest along with the sprint
  • Execution phase uses pre-approved permissions
  • No mid-sprint permission interruptions

Suggested Solutions

  1. Permissions manifest in plan mode - Use ExitPlanMode allowedPrompts parameter
  2. Sprint-scoped permissions - Temporary permissions file for sprint duration
  3. Permission inheritance - Agents inherit permissions from parent session

Acceptance Criteria

  • Sprint approval includes permission approval
  • Agents can execute without permission blocks
  • Permissions are scoped to sprint work (not blanket access)
## Problem User approves sprint items during `/sprint-plan`, but agents still need individual tool permissions during `/sprint-start`. This creates friction and defeats the purpose of upfront approval. User feedback: "I dont want to give you permissions for doing something we already stressed by reviewing. How can we have this happening without my approval?" ## Current Behavior 1. User reviews and approves 26 items during sprint planning 2. Sprint starts, agents are dispatched 3. Agents immediately hit permission blocks (Write, Edit, Bash) 4. User has to manually add permissions to settings.local.json 5. Agents need to be restarted ## Expected Behavior - Sprint planning generates a permissions manifest - User approves the manifest along with the sprint - Execution phase uses pre-approved permissions - No mid-sprint permission interruptions ## Suggested Solutions 1. **Permissions manifest in plan mode** - Use ExitPlanMode allowedPrompts parameter 2. **Sprint-scoped permissions** - Temporary permissions file for sprint duration 3. **Permission inheritance** - Agents inherit permissions from parent session ## Acceptance Criteria - [ ] Sprint approval includes permission approval - [ ] Agents can execute without permission blocks - [ ] Permissions are scoped to sprint work (not blanket access)
lmiranda added the Component/BackendType/FeaturePriority/High labels 2026-01-28 15:23:43 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: personal-projects/leo-claude-mktplace#233