unknowns

Surfaces unknown unknowns before unfamiliar work and rewrites the user's prompt.

Updated Aug 5, 2026
One-click install
npx skills add https://github.com/harivansh-afk/loom-index-e2e --skill unknowns-harivansh-afk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: unknowns
Source: https://github.com/harivansh-afk/loom-index-e2e/tree/main/skills/unknowns
Command: npx skills add https://github.com/harivansh-afk/loom-index-e2e --skill unknowns-harivansh-afk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Starting work in an unfamiliar domain or codebase area often fails because of blind spots: decisions you didn't know existed, conventions you never saw, and failure modes invisible from the entry point. This Skill runs a structured blind spot pass before work begins so those gaps surface early instead of mid-implementation. ## Core Features & Use Cases - Calibrated gap analysis: Anchors on what the user already knows, then sweeps code paths, git history, prior PRs, and repo conventions for what would surprise them. - Categorized report: Groups findings into architecture-changing decisions, what good looks like, prior art and potholes, and vocabulary needed to prompt precisely. - Rewritten prompt: Ends by producing the prompt the user should have written, with resolved unknowns folded in, and offers to proceed with it. - Use Case: Before modifying an unfamiliar payment module, run the pass to discover a deprecated API migration in progress, a known race condition guard, and the team's naming conventions, then start work with a corrected prompt. ## Quick Start Run a blind spot pass on my plan to add caching to the search service and tell me what I'm missing.

Frequently Asked Questions about unknowns

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find unknown unknowns before starting a coding task?▼

Run a blind spot pass that anchors on your current knowledge, then sweeps the relevant code paths, git history, and prior PRs for surprises. Findings are grouped into decisions, quality bars, prior art, and vocabulary, ending with a rewritten prompt.

What is a blind spot pass in software planning?▼

A blind spot pass is a short structured review done before work begins that maps the gap between what was asked and what the territory requires. It takes minutes of scanning and produces one structured reply, not a deep-dive project.

When should I run an unknowns analysis instead of just starting work?▼

Run it when entering a domain or codebase area you say you don't know, or when a task touches unfamiliar architecture. If you already know the conventions, prior art, and failure modes, the pass adds little value.

Does the blind spot pass replace a full design review?▼

No, it is deliberately scoped to minutes of scanning and one structured reply. Deep dives happen only after you pick which unknown matters, so it complements rather than replaces design review.

What does the rewritten prompt at the end contain?▼

It is the prompt you should have written originally, with the resolved unknowns folded in: chosen decision defaults, the quality bar, relevant prior art, and correct domain vocabulary. You can then proceed with it directly.