What problem does it solve? When you need to know whether something is possible before committing to a build — "can library X handle our use case?", "is this API rate limit acceptable?" — a full design-and-development pipeline is overkill. This Skill runs a light-weight exploration that answers the question with evidence, skipping design, gate review, and code entirely. ## Core Features & Use Cases - Light Requirement Analysis: Dispatches only the Requirement Analyst to frame the question, success criteria, and candidates — no acceptance criteria or user stories. - Evidence-Gathering Exploration: Reads code, runs probe commands (pip show, npm info, curl), and fetches upstream docs to investigate the question directly. - Cited Findings Document: Produces findings.md with a direct answer, evidence with file:line or link citations, project implications, and a recommended next step. - Use Case: Before adopting a new provider API, run an exploration to verify its rate limits against your expected volume, then receive a findings document recommending whether to proceed via a design pipeline or abandon the approach. ## Quick Start Ask the AI to run /harness-explore to investigate whether a specific library or approach can handle your use case and produce a findings document with evidence.
