skills.rest
k-negishi
k-negishiCOMMUNITY
Explore all skills by this author →
GitHub

feedback-response

Classify user feedback into actionable tasks with RED-GREEN-REFACTOR cycles.

1|Updated Nov 8, 2025
Search Tags:#workflow#planning#tdd#feedback#refinement#communication#steering
One-click install
npx skills add https://github.com/k-negishi/calendar-auto-register --skill feedback-response
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: feedback-response
Source: https://github.com/k-negishi/calendar-auto-register/tree/main/.claude/skills/feedback-response
Command: npx skills add https://github.com/k-negishi/calendar-auto-register --skill feedback-response

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill streamlines handling user feedback during and after implementation by providing a repeatable, documentation-driven workflow that ensures adjustments are planned, tracked, and validated through a structured process.

Core Features & Use Cases

  • Classifies feedback into micro-adjustments vs new features or bugs (within scope for adjustments).
  • Plans iterative phases in steering files with an explicit RED-GREEN-REFACTOR cycle.
  • Records progress and outcomes in task planning artifacts to ensure traceability and quality.

Quick Start

Run the feedback-response skill to classify feedback, create a steering phase, and start a RED-GREEN-REFACTOR cycle.

Frequently Asked Questions about feedback-response

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

FAQPage Schema
How do I turn user feedback into actionable development tasks?▼

To turn user feedback into actionable tasks, this skill classifies inputs into micro-adjustments or bugs, plans iterative phases in steering files, and runs a RED-GREEN-REFACTOR cycle to ensure traceable, validated refinements.

What is the best way to manage UI/UX adjustments after implementation?▼

Managing UI/UX adjustments after implementation requires a structured refinement workflow that records progress in task planning artifacts, ensuring changes are tracked, validated, and tied directly to the original feedback.

Can I use this workflow to classify minor tweaks versus new feature requests?▼

Yes, the workflow explicitly classifies feedback into micro-adjustments versus new features or bugs, helping you determine what falls within scope for immediate iterative refinements and what requires separate planning.

How does the RED-GREEN-REFACTOR cycle apply to product refinements?▼

The RED-GREEN-REFACTOR cycle applies to product refinements by planning iterative phases in steering files, running quality checks, and recording outcomes in task planning artifacts to drive structured, traceable adjustments.

When should I not use a documentation-driven workflow for feedback response?▼

A documentation-driven feedback response workflow is not suited for ad-hoc, untracked changes, as it requires planning iterative phases in steering files and recording outcomes in task planning artifacts to maintain traceability and quality.

Does this feedback response process require external dependencies or components?▼

No external dependencies or components are required, as the process organizes user feedback into formal tasks using built-in steering-file updates, task planning artifacts, and RED-GREEN-REFACTOR cycles.

Related Skills

Explore More Product & Management Skills→
yu13130122297yu13130122297

scout

Identify uncertainties in research framing, datasets, metrics, and baselines.

Community
Intermediate
KrismithReddy12KrismithReddy12

land-and-deploy

Merge pull requests, trigger CI/CD pipelines, and validate production health.

Community
Advanced
xbklairithxbklairith
2

spec-driven-implementation

Translate feature designs into task-based test-driven execution workflows.

Community
Advanced
jmaglyjmagly
175

issue-driven-ralph

Orchestrate issue-driven AI loops that post status updates and incorporate feedback via Gitea and GitHub APIs.

Community
Advanced