observe_bug_task_specs_impl - Claude MCP Skill

# Observe: Bug Task, Specs, Implementation

## O1: Study AGENTS.md as a Whole

Read AGENTS.md to understand:
- Operational guide and conventions
- Project-specific workflows
- Accumulated learnings
- How agents interact with this repository

## O3: Study AGENTS.md for Specification/Implementation Definitions

Identify from AGENTS.md:
- What constitutes "specification" in this repository?
- What file paths or patterns define specs?
- What constitutes "implementation"?
- What file paths or patterns define implementation?
- How do specs and implementation relate?

## O5: Study AGENTS.md for Task File Location

Identify from AGENTS.md:
- Where is the bug/task description located?
- What format is it? (file path, environment variable, command to run)
- How to access the bug details?

## O6: Study AGENTS.md for Draft Plan Location

Identify from AGENTS.md:
- Where is the draft plan file located?
- What format is it? (markdown, JSON, etc.)
- What structure does it follow?
- May not exist yet (first iteration)

## O9: Study Task File per AGENTS.md

Read the bug/task description:
- What are the symptoms?
- What is the expected vs actual behavior?
- What are the reproduction steps?
- What is the severity and impact?
- What functionality is affected?
- What error messages or logs exist?

## O10: Study Draft Plan File per AGENTS.md

If draft plan exists, read it:
- What spec adjustments are already identified?
- What structure is being used?
- What needs to be refined?
- May not exist (first iteration of draft planning)

## O11: Study Specifications per AGENTS.md Definition

Examine the specifications:
- Study all spec files per AGENTS.md definition
- Study specs related to the affected functionality
- Study acceptance criteria for the buggy feature
- Study edge cases and error handling
- Identify what's missing or incorrect in specs

## O12: Study Implementation per AGENTS.md Definition

Examine the implementation:
- Study file tree structure
- Study symbols related to the buggy functionality
- Study implementation of the affected feature
- Study error handling patterns
- Study test coverage for the buggy area
- Identify where the bug manifests