problem-discuss

Break multi-item client issue reports into discrete cases and classify each against product behavior.

1|Updated Apr 22, 2026
One-click install
npx skills add https://github.com/AbsolutSystems/absolutpowers --skill problem-discuss
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: problem-discuss
Source: https://github.com/AbsolutSystems/absolutpowers/tree/main/claude/skills/problem-discuss
Command: npx skills add https://github.com/AbsolutSystems/absolutpowers --skill problem-discuss

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you turn vague, multi-item client or stakeholder reports into a structured investigation so you can separate real defects from missing features, configuration issues, bad data, and simple misunderstandings.

Core Features & Use Cases

  • Decompose mixed reports into individual issues so each discrepancy is handled separately.
  • Verify expected behavior against code and evidence by tracing the relevant flow and checking attachments or supporting files.
  • Classify each issue as bug, feature gap, configuration problem, data anomaly, misunderstanding, or insufficient information.
  • Route the work correctly to debugging, feature planning, direct fixes, data correction, clarification, or further questioning.
  • Use case: a customer sends one message with five complaints about production behavior, and this Skill splits them into clear cases and tells you what to do next for each one.

Quick Start

Paste the client’s mixed report and any supporting attachments, and ask the Skill to break it into separate issues, verify each one against the code and rules, classify them, and recommend the next step for each case.

Frequently Asked Questions about problem-discuss

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

FAQPage Schema
How do I triage a mixed client report with multiple complaints into discrete issues?

Triage a mixed client report by decomposing it into discrete cases and classifying each against expected product behavior, separating actual bugs from feature gaps and misunderstandings before routing each case to the correct next step.

What is the best way to classify whether a stakeholder complaint is a bug or a feature gap?

Classify a stakeholder complaint by tracing the relevant code flow and reviewing supporting attachments to verify expected behavior, categorizing the issue as a bug, feature gap, configuration problem, data anomaly, or misunderstanding.

Can I use code investigation to route production discrepancies without implementing changes?

Yes, code investigation routes production discrepancies by evaluating per-case evidence and directing work to debugging, feature planning, direct fixes, data correction, clarification, or follow-up questions without implementing changes.

How do I handle a vague client issue report that contains insufficient information?

Handle a vague client issue report by decomposing it into individual cases and classifying each one, routing cases with insufficient information to clarification or follow-up questions to gather missing context.

When should I separate configuration issues from actual defects during bug triage?

Separate configuration issues from actual defects during bug triage when a mixed report contains multiple discrepancies, verifying each case against expected product behavior to distinguish configuration problems from real bugs before routing.