Discovery Gap Finder

# Discovery Gap Finder

## Purpose

Find the missing facts, documents, access, decisions, and interviews
that prevent the team from making a reliable engagement plan.

Use this after context distillation and path classification. The output
should become the follow-up agenda for discovery.

## Inputs

Use one or more of:

- Engagement context summary.
- Engagement path recommendation.
- Kickoff notes.
- Evidence already provided by the client.
- Existing artifact drafts.

## Process

1. List what is known and what evidence supports it.
2. Compare known context against the recommended path.
3. Identify missing documents, missing access, and missing owners.
4. Identify decisions that are blocked by missing information.
5. Generate prioritized follow-up questions.
6. Separate must-have discovery from nice-to-have discovery.
7. Assign confidence to the overall readiness level.

## Output format

```markdown
# Discovery Gap Report

## Readiness summary

Readiness: High / Medium / Low
Reason:

## Missing evidence

| Evidence needed | Why it matters | Source to ask | Priority            |
| --------------- | -------------- | ------------- | ------------------- |
|                 |                |               | High / Medium / Low |

## Missing access

| Access needed | System | Purpose | Blocking? |
| ------------- | ------ | ------- | --------- |
|               |        |         | Yes / No  |

## Missing documents

| Document | Why it matters | Likely owner | Priority            |
| -------- | -------------- | ------------ | ------------------- |
|          |                |              | High / Medium / Low |

## Blocked decisions

| Decision | Blocked by | Owner needed | Impact              |
| -------- | ---------- | ------------ | ------------------- |
|          |            |              | High / Medium / Low |

## Follow-up questions

1. Question:
   Why it matters:
   Who should answer:

## Discovery scope recommendation

Must have before planning:

-

Useful but not blocking:

-

## Recommended next step

Use the Artifact Pack Generator after must-have gaps are answered or
explicitly accepted as risks.
```

## Quality bar

- Do not treat unanswered questions as facts.
- Prioritize gaps that affect scope, risk, cost, or schedule.
- Distinguish missing evidence from missing access.
- Identify when the team can proceed with an explicit assumption.
- Keep questions specific enough for a stakeholder to answer.