What problem does it solve? When a 1C developer receives a raw bug report, trace file, or vague customer question, this Skill turns it into a structured investigation: it triages the input, delegates trace and code analysis to specialized agents, and ends with a ready-to-use change request (ZNi) statement instead of an unstructured chat log. ## Core Features & Use Cases - Unified entry point: Any free-form text (bug, question, raw customer text, screenshots) enters one explore flow with a mandatory brief card (symptom, route, question, confirmation) before any code reading. - Profile-based investigation: Bug profile analyzes traces (.pff, TRACE) via a trace-analyst agent; question profile answers how-things-work queries via a code-explorer agent; feature requests redirect to /opsx:new. - Structured handoff: Bug investigations finish with a ## Постановка ЗНИ block in chat (symptom, verified root cause, fix approach, acceptance criteria) that downstream commands /opsx:new and /opsx:extend consume directly. - Use Case: A customer reports "valid Kontur signature shows as invalid" with a trace file. The Skill builds a brief, runs trace analysis, checks archive relevance, and outputs a complete change-request statement with verified root cause and acceptance criteria. ## Quick Start Type /opsx:explore followed by a description of your 1C defect, question, or paste the raw customer text to receive a structured brief and investigation plan.
