level-3-diagnostic

Diagnose user-reported issues to uncover the true user goal before proposing fixes.

Updated Feb 17, 2026

Search Tags:#glossary #diagnostic #user-research #bug-report #product-insights #support-conversations #insights-logging

Ready to run

npx skills add https://github.com/0xHoneyJar/construct-observer --skill level-3-diagnostic

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: level-3-diagnostic
Source: https://github.com/0xHoneyJar/construct-observer/tree/main/skills/level-3-diagnostic
Command: npx skills add https://github.com/0xHoneyJar/construct-observer --skill level-3-diagnostic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams identify the true user goal behind reports (bug reports, feedback, or support conversations) before jumping to fixes, reducing misaligned scope and rework.

Core Features & Use Cases

Diagnostic-first workflow: loads domain glossary, collects core goals, traces sources of expectations, and scopes investigations.
Structured logging: logs Level 3 goals, user types, behavioral evidence, and workflow dependencies for insights.
Integration-ready: designed to be invoked before other skills (e.g., /craft) and to feed into continuous learning loops.

Quick Start

Ask the user what they were trying to accomplish when they noticed this issue and follow the Level 3 diagnostic flow to diagnose, scope, fix, and validate.

Frequently Asked Questions about level-3-diagnostic

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

FAQPage Schema

How do I diagnose the true user goal behind bug reports and support conversations?▼

To diagnose the true user goal behind bug reports, apply a Level 3 diagnostic workflow that loads domain glossaries, collects core goals, and traces expectation sources before proposing fixes.

What is the best way to investigate product insights from user-reported issues before scoping a fix?▼

The best way to investigate product insights from user-reported issues is using a diagnostic-first workflow that applies trace questioning to uncover behavioral evidence and workflow dependencies before execution.

How do I log user research insights from support tickets to reduce misaligned scope and rework?▼

You log user research insights from support tickets by using structured templates to record Level 3 goals, user types, behavioral evidence, and workflow dependencies into a continuous learning loop.

When do I need a Level 3 diagnostic workflow for feature requests and bug reports?▼

You need a Level 3 diagnostic workflow for feature requests and bug reports when teams jump to fixes too early and require diagnostic depth to uncover the actual user problem before scoping execution.

Does this diagnostic workflow integrate with other product management skills before execution?▼

Yes, the diagnostic workflow is integration-ready and designed to be invoked before other product management skills to feed diagnostic context and structured insights into downstream execution.

What are the limitations of fixing user-reported issues without tracing the source of user expectations?▼

Fixing user-reported issues without tracing the source of user expectations leads to misaligned scope and rework because the executed fix fails to address the true underlying user goal.