Resource
Markdown Output Prompt — Lock the Document Structure
The contract that stops AI documents from restructuring themselves: a pinned section skeleton, forced tables, and strict consistency rules.
Product Validation Report Prompt
Consolidate the whole validation into one shareable report — the success metric, the evidence, the hit / partial / miss verdict, and the iterate / pivot / scale decision, in a form the team and stakeholders can act on.
Overview
The metric, the measurement plan, the categorized evidence, and the decision are worth little scattered across four artifacts. This prompt consolidates them into a single Validation Report: what success was defined as, what the evidence showed against the target, the verdict, and the iterate / pivot / scale recommendation with its reasoning — structured so a stakeholder can read the call in the first section and a builder can act on it. It is the primary deliverable of a product-validation pass and the seed of the next planning cycle.
How to use this resource
-
Feed it the finished pieces
Supply the metric, evidence, verdict, and decision from the prior steps — this report consolidates them, it does not re-derive them.
-
Check the verdict is on top
The hit/partial/miss and the decision belong in the first sections; a report that buries the answer won't get read.
-
Hand the Next Cycle section to planning
The reusable metric, plan, and open questions are the input to the next round — route them there, don't let them die in the doc.
Why This Works
- Leading with the verdict and decision gives stakeholders the answer before the detail
- Keeping evidence and recommendation separate makes the call auditable against the data
- The Next Cycle section turns a one-off report into the start of the next planning loop
Best for
- Sharing a validation outcome with people who weren't in the data
- Closing the loop on a shipped product with a written verdict
- Carrying the metric and plan forward into the next iteration
Not for
- Making the iterate/pivot/scale decision itself — that is the Product Validation Decision Framework Prompt
- Planning what to measure — that is the Product Validation Measurement Plan Prompt
- A deployment runbook or release note — this reports the outcome, not the rollout
Use cases
- Writing up a post-launch validation result for stakeholders
- Bundling the metric, evidence, verdict, and decision into one artifact
- Producing the document that feeds the next planning cycle
FAQ
Does this prompt decide whether my product should iterate, pivot, or scale?
It documents the DECISION you already reached, not derives it. The report consolidates the metric, evidence, VERDICT, and the iterate/pivot/scale recommendation from prior steps that you feed in as inputs. The notFor routes making the call itself to the Product Validation Decision Framework Prompt. The markdown-output-builder formats the shareable report; the verdict and its accuracy remain yours to own.
How does the report stop a weak result from being spun as a success?
A rule requires preserving numbers and thresholds exactly and forbids softening a miss or inflating a partial, and EVIDENCE stays visibly separate from DECISION so the call can be audited against the data. The VERDICT, hit, partial, or miss, sits up front. The markdown-output-builder enforces the structure; you supply honest numbers and confirm the framing is fair.
More resources from Markdown Output Builder
Resource
README Prompt Template
Overview, Installation, Usage, Examples, Configuration — the README skeleton with required, runnable code examples.
Resource
API Documentation Prompt
Overview, Authentication, Endpoints, Error Handling, Rate Limits — endpoint docs in an identical structure, with parameter tables and runnable examples forced.
Resources that pair well
Resource
Executive Summary Prompt
Summary, Why It Matters, What Happens Next — the executive summary contract for readers who will never open the source.
Resource
Force JSON Output from AI
Stop getting 'Sure, here is the JSON…' — the output-contract pattern that forces models to return only parseable JSON: schema, example, and a strict rule block.
Resource
Fix Invalid JSON from AI
The JSON won't parse and you can't see why. Deterministic cause-sniffing — trailing commas, single quotes, unclosed brackets — and the repair prompt that fixes it.
Related tools
Tool
Markdown Output Builder
Build prompts that produce documents in a fixed structure — headings, sections, and tables.
Projects that use this resource
Project
Build a SaaS MVP with AI
The full path from idea to a shipped SaaS MVP — define and scope the requirements, design the architecture, API, and data model, then build it reviewed, tested, secured, cost-controlled, and deployed.
Project
Build an AI Support Agent with AI
The full path to a support agent you can put in front of customers — write its instructions, ground it in your docs, route and handle tickets, then evaluate and cost-control it before it goes live.
Project
Build an AI Research Assistant with AI
The full path to an AI research assistant — define its scope, organize the source corpus, ground responses in references, extract key facts, synthesize findings, check groundedness, then validate it for use.
Project
Build an AI Meeting Assistant with AI
The full path to an AI meeting assistant — define the use case, turn transcripts into structured notes, extract decisions and action items, classify follow-ups, write a shareable summary, evaluate accuracy, then ready it for the team.
Project
Build an AI Content Engine with AI
The full path to a content operation that runs, not a pile of posts — set the editorial strategy, research the topics, build a reusable template, then produce and QA structured pieces on repeat.
Project
Build a Programmatic SEO Site with AI
The full path to pages that rank at scale, not penalty bait — map the intents, build the data set, structure it, template the page, then QA before publishing hundreds.
Project
Build a Customer Support System with AI
The full path to a support operation, not just a bot — stand up the knowledge base, route the tickets, add the AI agent, integrate your stack, close the feedback loop, evaluate, and deploy.
Project
Build a Marketplace with AI
The full path to a two-sided platform — define the buyer-and-seller requirements, model the data, design the API, build roles and permissions, wire integrations, design the UI, then test, secure, and ship it.
Project
Build an E-commerce Store with AI
The full path to a store you own end to end — model the catalog and orders, design the storefront and checkout, add customer accounts and payments, then secure it, test it, and ship.
Workflows that use this resource
Workflow
AI Product Validation Workflow
Find out whether the thing you shipped actually worked — define the success metric, plan the measurement, classify the real evidence, then render a verdict and an iterate / pivot / scale decision.