feedback

星标11

分支1

更新时间2026年4月13日 14:31

Walk through structured feedback and submit it as a GitHub Issue on the Acumen repo.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

来源

VGrss

VGrss/Acumen

打开 GitHub 仓库查看创作者相关仓库

下载

Feedback

Collect structured feedback from the user and submit it as a GitHub Issue on the Acumen repository (VGrss/Acumen).

Core behavior

Step 1 — Category

Ask the user to pick one:

Bug report — Something is broken or behaving unexpectedly
Skill idea — A new skill or enhancement to an existing one
General feedback — Anything else (UX, docs, process, direction)

Step 2 — Problem

Ask: "What's the problem?"

Guide the user to describe what happened or what's missing. Be specific — ask follow-up questions if the description is vague. A good problem statement names the trigger ("when I run /diagnose…"), the observed behavior, and the expected behavior.

Step 3 — Impact

Ask: "Who does this affect and how?"

Guide the user to articulate:

Who is impacted (which persona, role, or workflow)
How often it happens (every time, sometimes, edge case)
How severe it is (blocker, friction, cosmetic)

Step 4 — Suggested solution (optional)

Ask: "Do you have a solution in mind? (optional, feel free to skip)"

If the user has an idea, capture it. If not, move on — good feedback describes the problem well, not necessarily the fix.

Step 5 — Review and confirm

Format the feedback as a preview and show it to the user:

## Category
{category}

## Problem
{problem description}

## Impact
{impact description}

## Suggested solution
{solution or "None provided"}

Ask the user to confirm or edit before submitting.

Step 6 — Submit

Use the GitHub CLI to create an Issue with a label matching the category:

gh issue create \
  --repo VGrss/Acumen \
  --label "{category label}" \
  --title "{concise title derived from the problem}" \
  --body "{formatted body}"

Use these labels based on category:

Bug report → bug
Skill idea → enhancement
General feedback → feedback

The body should follow this template:

## Problem
{problem description}

## Impact
{impact description}

## Suggested solution
{solution or "_None provided — feedback only._"}

---
_Submitted via `/feedback`_

Return the Issue URL to the user.

Tone

Be conversational but efficient. Each step is one question — don't dump all questions at once. Guide the user through the flow one step at a time, like a short interview.

同仓库更多 Skills

同仓库

increment

VGrss/Acumen

Scope a single product increment end-to-end — context, spec, implementation, wireframes, and engineering considerations. Use when a feature or bet needs a shippable document before building — typically the option chosen out of /workshop's divergence. Leads to /critique-product.

2026-07-3111

cheatsheet

VGrss/Acumen

Print a quick-reference cheatsheet of all Acumen skills, organized by layer.

2026-07-1711

catchup

VGrss/Acumen

Pull latest code from main, summarize recent changes in product-friendly terms, and report .acumen/ context health (what exists, what's fresh, what's stale, what's missing). Preserves all .acumen/ context files.

2026-07-0911

critique-product

VGrss/Acumen

Evaluate and validate a PM artifact — score for rigor, test riskiest assumptions, and decide if it's ready to ship. Use when reviewing a PRD, spec, increment, strategy, or roadmap.

2026-07-0911

diagnose

VGrss/Acumen

Find what's broken and what's underexploited — problems AND opportunities — grounded in data, value delivery per persona, and current features. The entry point to ideation; hands sharp problems and opportunities to /workshop.

2026-07-0911

teach-acumen

VGrss/Acumen

One-time setup that gathers product context for your project and saves it to .acumen.md. Run once to establish persistent product guidelines.

2026-07-0911

name	feedback
description	Walk through structured feedback and submit it as a GitHub Issue on the Acumen repo.
user-invocable	true

Feedback

Collect structured feedback from the user and submit it as a GitHub Issue on the Acumen repository (VGrss/Acumen).

Core behavior

Step 1 — Category

Ask the user to pick one:

Bug report — Something is broken or behaving unexpectedly
Skill idea — A new skill or enhancement to an existing one
General feedback — Anything else (UX, docs, process, direction)

Step 2 — Problem

Ask: "What's the problem?"

Step 3 — Impact

Ask: "Who does this affect and how?"

Guide the user to articulate:

Who is impacted (which persona, role, or workflow)
How often it happens (every time, sometimes, edge case)
How severe it is (blocker, friction, cosmetic)

Step 4 — Suggested solution (optional)

Ask: "Do you have a solution in mind? (optional, feel free to skip)"

If the user has an idea, capture it. If not, move on — good feedback describes the problem well, not necessarily the fix.

Step 5 — Review and confirm

Format the feedback as a preview and show it to the user:

## Category
{category}

## Problem
{problem description}

## Impact
{impact description}

## Suggested solution
{solution or "None provided"}

Ask the user to confirm or edit before submitting.

Step 6 — Submit

Use the GitHub CLI to create an Issue with a label matching the category:

gh issue create \
  --repo VGrss/Acumen \
  --label "{category label}" \
  --title "{concise title derived from the problem}" \
  --body "{formatted body}"

Use these labels based on category:

Bug report → bug
Skill idea → enhancement
General feedback → feedback

The body should follow this template:

## Problem
{problem description}

## Impact
{impact description}

## Suggested solution
{solution or "_None provided — feedback only._"}

---
_Submitted via `/feedback`_

Return the Issue URL to the user.

Tone

Be conversational but efficient. Each step is one question — don't dump all questions at once. Guide the user through the flow one step at a time, like a short interview.