Create proposal-execution skill: Enable researchers to

Tinker

Home Epics Create proposal-execution skill: Enable researchers to execute approved proposalsEdit

Create proposal-execution skill: Enable researchers to execute approved proposals

Cancel

Title *

Project *

Description

## Context
From approved proposal #30: Researchers create proposals but cannot execute them once approved.

## Problem
- 7 memory_cleanup proposals approved → memories not deleted
- #29 (Retrospective Skill) approved → no ticket created
- #23 (withdraw #11) approved → proposal not withdrawn

Researchers can only suggest work, not execute it.

## Solution: proposal-execution skill

A skill that allows Researchers to **execute approved proposals**.

### MCP Tool to Add
```ruby
execute_proposal(proposal_id)
```

### Workflow by Proposal Type

**memory_cleanup:**
- Validate: proposal.approved?
- Delete memories from metadata.memory_ids_to_delete
- Mark proposal as "executed"
- Log: "Deleted memories [ids] per proposal #N"

**feature/refactor:**
- Validate: proposal.approved?
- Create ticket from proposal content
- Set ticket.proposal_id = proposal.id
- Mark proposal as "in_progress"

**new_ticket (withdrawals):**
- Validate: proposal created by researcher?
- Mark target proposal as "withdrawn"
- Close target proposal

### Guardrails
- Only execute proposals with status="approved"
- Only execute proposals created by researcher (can't execute others')
- Validation: metadata has required fields for proposal type
- Audit log for all executions
- Error if proposal already executed

### Permissions
- Add to researcher role in mcp_permissions.yml
- Only for researcher agent (not worker, reviewer, orchestrator)

### Files
- `.claude/skills/proposal-execution/` - New skill
- `/rails/app/controllers/api/v1/mcp_controller.rb` - Add handle_execute_proposal
- `/rails/config/tinker/mcp_permissions.yml` - Add execute_proposal to researcher
- `spec/requests/api/v1/mcp_spec.rb` - Test coverage