What problem does it solve? When a bug is found during testing of an OpenSpec change (a 1C development task), you need a structured way to turn traces, remarks, and screenshots into a verified root-cause analysis and concrete fix tasks captured inside the same change artifacts, instead of ad-hoc debugging in chat. ## Core Features & Use Cases - Structured RCA: Separates verified facts (with trace line and file references) from hypotheses, each hypothesis carrying a verification plan. - Subagent orchestration: Delegates trace parsing to onec-trace-analyst, code exploration to onec-code-explorer, and architectural review to onec-code-architect, saving their reports under the change's reports directory. - Artifact capture: Writes fix tasks into tasks.md with slice-aware placement rules and updates design.md when the bug reveals a design gap, then hands off to /opsx:apply for implementation. - Use Case: A tester reports that a document posting routine excludes the wrong participants and provides a trace file; the skill loads the change context, analyzes the trace, verifies hypotheses against the source XML and BSL code, and records fix tasks in the change. ## Quick Start Run /opsx:debug with a trace file path or a description of the expected versus actual behavior to start a root-cause investigation for the current OpenSpec change.
