feedback

Create or import GitHub Issues and link them to req/spec data.

6|1|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/kicchann/reqord --skill feedback-kicchann
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feedback
Source: https://github.com/kicchann/reqord/tree/main/plugins/reqord/skills/feedback
Command: npx skills add https://github.com/kicchann/reqord --skill feedback-kicchann

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill coordinates GitHub feedback workflows by creating or importing Issues and linking them to related req/spec data.

Core Features & Use Cases

  • Create new feedback as GitHub Issues or ingest existing feedback into your workflow.
  • Classify feedback into types (bug, improvement, gap, etc.) and link to relevant specs or requirements.
  • Synchronize, tag, and close feedback, while keeping traceability and flags up-to-date.

Quick Start

Identify open feedback, classify its type, and create or link GitHub Issues with user-confirmed actions.

Frequently Asked Questions about feedback

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

FAQPage Schema
How do I link GitHub issues to requirements for traceability?

To link GitHub issues to requirements, you can classify feedback items by type and connect them directly to relevant spec data. This coordination creates an auditable traceability flow across your repository items.

Can I import existing GitHub issues into a feedback classification workflow?

Yes, you can ingest existing GitHub issues into your feedback workflow. Once imported, you can classify them into types like bug or improvement and synchronize their status with related spec data.

Do I need GitHub authentication and the gh CLI to automate issue syncing?

Yes, GitHub authentication and the gh CLI are required to automate issue syncing. The workflow uses these dependencies to perform deterministic operations and create or link issues within your repository context.

What is the best way to classify GitHub feedback into types like bug or gap?

The best way to classify GitHub feedback is to use an automated workflow that categorizes issues into types like bug, improvement, or gap. This process tags feedback and links it to relevant specs for tracking.

Does GitHub issue automation require manual confirmation for closing feedback items?

Yes, GitHub issue automation requires user confirmation for actions like closing feedback items. This ensures deterministic operations remain auditable and prevents unintended changes to your linked spec data.