ChanningYul

Find Unknowns — AI skill for Claude Code

AI community

Agent Skill: Unknowns SOP for AI coding agents — blind spot scan, prototype, interview, implementation notes, quiz.

How to install Find Unknowns

This entry records only its repository, not the path inside it, so there is no exact command to give. Open ChanningYul/find-unknowns and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Find Unknowns does

Agent Skill: Unknowns SOP for AI coding agents — blind spot scan, prototype, interview, implementation notes, quiz. Surface unknown unknowns before you ship. Install: npx skills add ChanningYul/find-unknowns

Alternatives in AI

  • Codeburn — Free, local tool to track AI coding token usage and cost across 37 tools and agents (Claude Code, Cursor, Code 9.7k ★
  • Surface — Show ranked attack surface for a target from its recon manifest + hunt memory 3.8k ★
  • AI Agent Interview Guide — AI Agent 面试全攻略:从零到Offer,包含200+面试题、企业级项目(Python/Java/Go)、简历模板、STAR面试稿、哆啦A梦漫画图解 637 ★

README

find-unknowns — Agent Skill: Surface Your Unknowns Before You Ship

**English** | [中文说明见下](#中文说明)

`find-unknowns` is an [Agent Skill](https://agentskills.io) (SKILL.md) that gives your AI coding agent a repeatable SOP to systematically discover **unknown unknowns** — the gaps between the map (everything you've told the agent) and the territory (where the real work happens: your codebase, constraints, and users).

Instead of letting the agent guess what you want at every blind spot, this skill forces it to surface those blind spots **before, during, and after implementation** — so you make the decisions that matter and the agent handles the rest.

Why

Every agent mistake traces back to an unknown: requirements it guessed, edge cases it didn't foresee, "obvious" context that was never written down. This skill categorizes unknowns into four types and maps each to a concrete technique:

Unknown type Meaning Technique
Known knowns Already in the prompt (already on the map)
Known unknowns You know you haven't decided ③ Interview
Unknown knowns Too obvious to write down ② Brainstorm & prototype
Unknown unknowns Never even considered ① Blind spot scan

Plus two universal techniques: ④ reference material (point at source code instead of describing) and ⑤ implementation plan (final gate before coding).

What's inside — 8 techniques across 3 phases

  • Phase 1 — Before implementation: ① Blind spot scan (dig out unknown unknowns) · ② Brainstorm & prototype (2–4 wildly different directions, fake data, no wiring) · ③ Interview (one question at a time, architecture-changing answers first) · ④ Reference material (source > screenshot > text) · ⑤ Implementation plan (decisions-you'll-tweak on top, mechanical work buried)
  • Phase 2 — During implementation: ⑥ Implementation notes (implementation-notes.md: Deviations / Open Questions / Decisions — conservative picks, keep running, only stop for architecture-level d