pace-feedback

Collect user feedback, classify production incidents, and generate postmortems.

73|6|Updated Feb 20, 2026
One-click install
npx skills add https://github.com/arch-team/devpace --skill pace-feedback
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pace-feedback
Source: https://github.com/arch-team/devpace/tree/main/skills/pace-feedback
Command: npx skills add https://github.com/arch-team/devpace --skill pace-feedback

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of collecting user feedback, managing production incidents, and ensuring a closed loop for continuous improvement in software development.

Core Features & Use Cases

  • Feedback Collection: Systematically gather user feedback, bug reports, and feature requests.
  • Incident Management: Open, track, and close production incidents with structured timelines and postmortem generation.
  • Root Cause Analysis: Assists in identifying the root cause of issues and suggests preventative measures.
  • Use Case: A user reports a critical bug in production. Using /pace-feedback report "Login button is broken", the skill automatically creates a hotfix ticket, tracks the incident, and guides the team through resolution and postmortem analysis.

Quick Start

Use the pace-feedback skill to report a production issue with the description "Users are unable to log in".

Frequently Asked Questions about pace-feedback

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

FAQPage Schema
How do I collect user feedback and track production incidents for continuous improvement?

Incident management and user feedback collection involve systematically gathering reports, classifying issues into production events or defects, and initiating structured workflows for resolution and analysis. This creates a closed loop linking feedback to the development lifecycle.

How do I create a postmortem after resolving a production incident?

Postmortem generation is initiated after incident creation and timeline tracking. The process assists in identifying the root cause of issues and suggests preventative measures, ensuring structured analysis and continuous improvement across the development lifecycle.

What is the best way to classify incoming bug reports and feature requests?

Classifying feedback involves categorizing reports into production events, defects, improvements, or new requests. This structured classification initiates specific workflows for resolution, tracking, and root cause analysis within incident management.

Can I track production incidents with structured timelines from initial report to closure?

Tracking production incidents supports structured timelines from opening to closing. It links user feedback directly to the development lifecycle, ensuring continuous improvement through guided resolution and postmortem generation.

Do I need any specific bug tracking tools to perform root cause analysis on production events?

No specific bug tracking tools are required as dependencies. The process manages production events by collecting reports, classifying issues, and initiating structured workflows for resolution and root cause analysis without external tool prerequisites.

Why should I use structured incident management instead of ad hoc bug tracking?

Structured incident management ensures a closed loop for continuous improvement by linking feedback to the development lifecycle. Unlike ad hoc bug tracking, it provides timeline tracking, root cause analysis, and postmortem generation for systematic resolution.