Build a 'Boil the Lake' completeness audit for your roadmap

The Problem

AI has made it cheap to generate product artifacts. You can produce a PRD in ten minutes, a competitive analysis in fifteen, a go-to-market plan in twenty. But cheaper production has not led to better products. It has led to faster shipping of incomplete work.

Teams are now moving so quickly that they skip the boring, unglamorous work of completeness: edge case analysis, dependency mapping, rollback planning, compliance review. The roadmap looks full, but the items on it are hollow. They have descriptions without acceptance criteria, timelines without dependencies, and risk sections that say "low" without evidence.

A Standish Group study found that 66% of software projects experience cost overruns or schedule delays, and the leading cause is incomplete requirements. Not wrong requirements, incomplete ones. The gaps that no one checked for because checking felt slow.

According to the Project Management Institute, organizations that invest in thorough requirements analysis waste 28% less budget on rework compared to those that rush to execution. Completeness is not perfectionism. It is economic discipline.

The Completeness Paradox

AI created the paradox: the same tool that makes it easy to generate artifacts also makes it easy to skip the hard parts. When a PRD takes ten minutes to write, the incentive to spend thirty minutes auditing it disappears. But the cost of an incomplete PRD is not thirty minutes. It is three sprints of rework.

How This Prompt Works

This prompt runs a completeness audit on your roadmap, inspired by the consulting practice of "boiling the lake," systematically touching every item to verify it meets a quality bar. AI made generating the artifacts cheap. This prompt makes auditing them cheap too.

The audit operates across five dimensions:

• Requirements completeness: Does every roadmap item have defined acceptance criteria, user stories, and edge cases?
• Dependency mapping: Are cross-team and cross-system dependencies identified and sequenced correctly?
• Risk assessment: Does every item have identified risks with mitigation plans, not just a "low/medium/high" label?
• Measurement definition: Does every item have a success metric defined before development starts?
• Rollback readiness: Does every item have a defined rollback procedure in case it fails in production?

The prompt walks through your entire roadmap item by item, scoring each dimension, flagging gaps, and generating specific recommendations for what needs to be added. The output is a completeness scorecard with a prioritized remediation list.

When to Use It

• Before a planning cycle, to audit the roadmap you are about to commit to
• After rapid roadmap generation, to quality-check AI-assisted output
• When inheriting a roadmap from another PM or team
• Before a board meeting or stakeholder review, to ensure nothing is missing

Common Pitfalls

• Treating the audit as a gate instead of a tool: The audit should identify gaps, not block progress. Some gaps are acceptable if acknowledged. The goal is informed decision-making, not perfect documents.
• Auditing at the wrong level: A roadmap item that says "Improve onboarding" is too vague to audit. Break items down to a level where completeness can be evaluated against specific criteria.
• Doing it once: The highest value comes from auditing at a regular cadence, not just before big milestones. Quarterly audits catch drift before it compounds.

Further Reading

• The CHAOS Report: Project Success and Failure Trends - Standish Group
• The Cost of Poor Requirements - Project Management Institute
• Product Roadmap Best Practices - ProdPad