Assessing investment readiness
Gives the investment committee an evidence-based view of likely twelve-month delivery, distinguishing credible commitments from claims that exceed demonstrated capacity.
— Product & Tech
Tests product roadmap commitments against engineering capacity, delivery history and dependencies to give investment committees a defensible view of what is likely to ship within twelve months.
2–3 weeks → ~25 minutes
For a typical multi-document review workflow
No coding required
— USE CASES
Gives the investment committee an evidence-based view of likely twelve-month delivery, distinguishing credible commitments from claims that exceed demonstrated capacity.
Assesses whether available engineering capacity supports the promised scope and timing. Highlights where delivery expectations rely on assumptions that need stronger evidence.
Identifies planned work without clear ownership or adequate dependency coverage, showing where apparently firm commitments carry unresolved delivery risk.
Compares stated product commitments with backlog evidence and shipped-on-time history, giving advisers a defensible basis for challenging delivery claims.
— HOW IT BEHAVES
The mechanics behind this specific template — what it reads, what it calculates, and where a human stays in the loop.
Each process step is assessed against criteria you control and weight, so the same standard applies to every process step in the end-to-end process.
The figures behind each process step are computed by formula during the run, so the arithmetic is identical every time and can be checked line by line.
Figures buried in narrative process documentation and run data are extracted as data you can compute and compare with.
Every process step is captured in the same field structure, so records drawn from different documents and sources stay comparable.
All of your process documentation and run data is processed as one set, so patterns across documents surface instead of being read one file at a time.
Current external sources on the end-to-end process are researched during the run rather than recalled from training data, and every source travels with the output.
Product roadmaps often present ambition as commitment, leaving investment teams to judge delivery prospects without a clear link between promised scope and engineering capacity. In practice it shows up as assessing investment readiness: gives the investment committee an evidence-based view of likely twelve-month delivery, distinguishing credible commitments from claims that exceed demonstrated capacity. It is the kind of work that decides whether a recommendation survives scrutiny — and the kind that quietly eats 2–3 weeks of senior time whenever it comes round.
As a Skill, the work is already sequenced. You bring the evidence, and the run produces evidence-based roadmap realism assessment plus engineering capacity versus committed scope analysis. What sits between input and output is the codified method: thresholds, sequencing and the points where a human confirms a call — all of it visible and editable in the Skill. In effect, 2–3 weeks of senior time compresses into ~25 minutes — and the output is comparable across clients, quarters and colleagues instead of shaped by whoever ran it.
Product roadmap realism check exports as a structured SKILL.md file and is MCP-ready, so the same method runs in ChatGPT, Claude, Copilot or your own AI products. Adapt it to your methodology, and the intelligence stays yours — not locked to one vendor.
Assesses a reported vulnerability against severity scoring, real exposure and the criticality of the affected asset, then returns a governed remediation decision — patch now, take it in the next cycle or formally accept the risk — with the reasoning recorded and a security lead sign-off before work is scheduled.
Maps a target’s data and intellectual property assets, clarifying ownership, licence obligations and portability constraints to support migration and exit planning.
Builds a complete inventory of the technology estate — every system with its vendor, purpose, integrations, hosting and build-or-buy status — and flags where concentration, lock-in or vendor viability creates risk.
Assesses security controls and supporting evidence against relevant compliance frameworks, producing a risk-led remediation plan or an assurance summary grounded in documented findings.
Assesses infrastructure headroom against documented peak demand, projects the first constraints at 2× and 5× load, and identifies the bottleneck to prioritise before growth puts service reliability at risk.
Reviews data rights, AI use and model controls against governance maturity, producing a deal-risk memo or readiness summary that clarifies exposure and its implications for the transaction.