Find Blindspots
Definition
Search for what has not been considered yet. Ask expert-style questions and inspect project evidence when possible, but do not implement the fix unless the user moves into another workflow phase.
Questions To Ask
- What might we be missing?
- What hidden dependency, permission, data state, failure mode, edge case, or operational constraint might matter?
- What would break if our main assumption is false?
- What would an expert ask before proceeding?
- What should we verify before committing to this path?
- What could become expensive to change later?
Question Rules
- Ask blindspot questions near phase boundaries and before irreversible work.
- Prefer concrete risk categories over vague worry.
- Use project inspection to discover hidden dependencies and failure modes.
- Mark credible blindspots as blockers, investigations, assumptions, or deferred risks.
Existing Project Comparison
- Inspect code paths, tests, schemas, permissions, logs, docs, deployment files, and prior delivery notes when available.
- Compare likely blindspots against existing workflow documents.
- Flag missing evidence, unknown dependencies, and unsafe interactions.
Suggestive Plan
- Identify the current plan or intended next step.
- Generate domain-specific blindspot questions.
- Inspect the project for evidence when possible.
- Classify blindspots by risk and action.
- Update
UNKNOWNS.md and recommend whether to continue or pause.
Example
Before building an auth provider, ask about account linking, session migration, tenant permissions, token refresh, rollback, existing auth modules, and test coverage.
Vocabulary
- Unknown unknown: risk or fact not yet considered.
- Blindspot: important missing perspective or evidence.
- Hidden dependency: behavior relying on another system or module in a nonobvious way.
- Unsafe interaction: two individually acceptable choices that create risk together.
Expected Outcome
Produce an Unknown Unknowns section in UNKNOWNS.md with blindspot questions, investigations, risk classifications, evidence gaps, and recommended next action.
1---2name: find-blindspots3description: Ask question-first prompts to uncover unknown unknowns before or during software work. Use for any domain when hidden assumptions, missing failure modes, unseen dependencies, security risks, data risks, edge cases, or expert concerns could change the plan.4---56# Find Blindspots78## Definition910Search for what has not been considered yet. Ask expert-style questions and inspect project evidence when possible, but do not implement the fix unless the user moves into another workflow phase.1112## Questions To Ask1314- What might we be missing?15- What hidden dependency, permission, data state, failure mode, edge case, or operational constraint might matter?16- What would break if our main assumption is false?17- What would an expert ask before proceeding?18- What should we verify before committing to this path?19- What could become expensive to change later?2021## Question Rules2223- Ask blindspot questions near phase boundaries and before irreversible work.24- Prefer concrete risk categories over vague worry.25- Use project inspection to discover hidden dependencies and failure modes.26- Mark credible blindspots as blockers, investigations, assumptions, or deferred risks.2728## Existing Project Comparison2930- Inspect code paths, tests, schemas, permissions, logs, docs, deployment files, and prior delivery notes when available.31- Compare likely blindspots against existing workflow documents.32- Flag missing evidence, unknown dependencies, and unsafe interactions.3334## Suggestive Plan35361. Identify the current plan or intended next step.372. Generate domain-specific blindspot questions.383. Inspect the project for evidence when possible.394. Classify blindspots by risk and action.405. Update `UNKNOWNS.md` and recommend whether to continue or pause.4142## Example4344Before building an auth provider, ask about account linking, session migration, tenant permissions, token refresh, rollback, existing auth modules, and test coverage.4546## Vocabulary4748- Unknown unknown: risk or fact not yet considered.49- Blindspot: important missing perspective or evidence.50- Hidden dependency: behavior relying on another system or module in a nonobvious way.51- Unsafe interaction: two individually acceptable choices that create risk together.5253## Expected Outcome5455Produce an `Unknown Unknowns` section in `UNKNOWNS.md` with blindspot questions, investigations, risk classifications, evidence gaps, and recommended next action.
harsh817