Parse and Send Feedback

Split raw feedback blocks into Objective Documents and dispatch each to a headless AG background worker.

Updated Feb 3, 2026
One-click install
npx skills add https://github.com/BedaBeda-Growth/bedabeda-growth-site --skill parse-and-send-feedback
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Parse and Send Feedback
Source: https://github.com/BedaBeda-Growth/bedabeda-growth-site/tree/main/skills/parse-and-send-feedback
Command: npx skills add https://github.com/BedaBeda-Growth/bedabeda-growth-site --skill parse-and-send-feedback

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Collects a block of feedback and splits it into discrete actionable items to prevent cross-item contamination, enabling reliable, isolated processing.

Core Features & Use Cases

  • Shreds a raw feedback block into separate Objective Documents for each actionable item.
  • Dispatches each item to a fresh headless AG background worker in sequence, ensuring zero context bleed.
  • Surfaces pass/fail and evidence to Nick via the message bus for traceability and follow-up.

Quick Start

Provide a feedback block to the skill and observe the sequential dispatch results.

Frequently Asked Questions about Parse and Send Feedback

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I split a block of feedback into isolated tasks?▼

To split feedback into isolated tasks, the skill shreds a raw block of notes into discrete Objective Documents and dispatches each as a separate background worker, ensuring zero context bleed between items.

Why does sequential dispatch matter for processing bug reports?▼

Sequential dispatch matters for bug reports because it processes each item with a fresh context, preventing cross-item contamination and ensuring failures are surfaced individually with isolated evidence.

How do I process QA notes without context bleed between items?▼

To process QA notes without context bleed, the skill parses the block into separate Objective Documents and dispatches each to a fresh headless background worker, keeping all item contexts fully isolated.

Can I track the pass/fail status of dispatched feedback tasks?▼

You can track pass/fail status because each dispatched worker writes its execution results and evidence to the message bus, surfacing the traceability data directly for follow-up.

What is the best way to parse raw client notes into actionable items?▼

The best way to parse raw client notes is to shred the block into separate Objective Documents, dispatching each as a fresh background worker to ensure isolated, reliable processing of every actionable item.