---
name: barefootford-request-feature
description: "Send a feature request or idea to the ButterCut team. Use when the user says \"request a feature\", \"I wish ButterCut could…\", \"can you ask the team for…\", \"suggest an idea\", or wishes out loud for something ButterCut doesn't do."
license: "NOASSERTION"
metadata:
  decimalai-skill-id: "f3c783ed-8ade-4770-8509-83b8b2fe9698"
  decimalai-version-id: "d4a5aee0-b1dc-4202-88a2-f8b95bce3c90"
  decimalai-version: "1"
  decimalai-body-sha256: "627d0d60d07eba865c7651420616030d64b098e7b1fae3ec0346eccf4ba75733"
  decimalai-name: "barefootford/request-feature"
  decimalai-format: "1"
  decimalai-invocation: "model"
  decimalai-category: "sales-support"
  decimalai-source: "https://app.decimal.ai/s/barefootford-request-feature@1/SKILL.md"
---
# Skill: Request a Feature

The user wants ButterCut to do something it doesn't do. This sends their idea to the people who build it. It always goes through them — you write it up, they approve it, you send it — so it is **not** governed by the error-reporting setting: someone who turned error reports off can still ask for multicam support.

## Step 1 — Make sure it isn't already there

Check skills, `AGENTS.md`, `libraries/settings.yaml`, and `CHANGELOG.md` first — if ButterCut can already do it, just show them how. If it's a Pro feature and they're on the free edition (`ruby lib/buttercut/library.rb edition` prints `core`), tell them it exists in ButterCut Pro instead of sending a request.

## Step 2 — Write it up with them

Draft in their words: a one-line **title** ("Support multicam angles in exports") and a few-sentence **request** — what they're trying to do and why the current way doesn't get them there. The *why* is the useful part. Same rule as bug reports: **their footage stays out of it** — no library, clip, client, or subject names ("a recent two-camera shoot", not "the Hendricks wedding").

## Step 3 — Confirm, then send

Read it back, and only when they approve:

```bash
ruby lib/buttercut/report.rb send \
  --kind feature \
  --title "Support multicam angles in exports" \
  --narrative "Shoots weddings with two cameras and syncs them by hand in Resolve after exporting. Wants both angles to land on the timeline already lined up."
```

If they've saved an email (`ruby lib/buttercut/report.rb consent` shows it), it rides along automatically so the team can reply. If they haven't and they'd want an answer, offer to add `error_report_email:` to `libraries/settings.yaml`.

Then confirm it landed, without promising it'll get built:

> "Sent — that's with the ButterCut team now. No promises on timing, but they read every one."

Don't show them the JSON, the UUID, or a status code. If the send failed, say so plainly and offer to try again later.

---

**Developer mode.** With `.buttercut_mode` present, `report.rb send` refuses. Use `--dry-run` to see what would go.