What problem does it solve? Teams often jump into implementation based on vague tickets, rough verbal requests, or unverified assumptions, wasting effort on the wrong problem. This Skill treats every Issue or request as a hypothesis and re-evaluates it against the actual codebase, data, and existing specs before any code is written. ## Core Features & Use Cases - Hypothesis-based issue triage: Fetches Linear issues (via MCP) or GitHub issues (via gh CLI), decomposes claims, and separates confirmed facts from unverified assumptions. - Fact-grounded investigation: Searches code, git history, logs, and monitoring data to validate whether the reported problem is real, its scope, and whether similar solutions already exist. - Structured decision support: Produces a re-evaluation report with options (do nothing, measure first, minimal fix, full implementation) plus closed-ended questions (A/B/C format) that minimize the requester's reply cost. - Use Case: A teammate pastes "TES-123調べて" into chat. The Skill fetches the Linear issue, checks the relevant code and git history, finds the reported bug is actually intended behavior, and presents a report recommending monitoring instead of a fix. ## Quick Start Ask the agent to investigate and re-evaluate a specific Linear or GitHub issue before starting implementation, for example by saying "このIssueについて調査して" with the issue ID.