What each of the nine tools takes in and produces, and where its output goes next. The tools share records stored in this browser: each one saves its output, and the next one picks it up. A step's primary inputs and outputs are the ones the next step depends on; secondary ones are used or produced alongside them. Most steps link to a saved sample run you can open without an API key; the Persona Generator is its own demonstration.
Proposed architecture: network diagram ↗ · New here? Start with the overview ↗Primary risk: A plausible composite can be mistaken for research.
Required review: Confirm which attributes are supported, inferred, or invented.
Primary risk: Team assumptions can be rendered with the visual authority of research.
Required review: Separate observed evidence from hypotheses.
Primary risk: Missing portfolio context may be filled with plausible competitors, budgets, or benefits.
Required review: Validate the comparison set, epic boundaries, assumptions, KPIs, baselines, and proposed instrumentation.
Primary risk: Generated cost, benefit, and effort statements can appear more certain than the evidence supports.
Required review: Replace unsupported estimates and financial precision with sourced values or explicit unknowns.
Primary risk: Correct arithmetic can lend false authority to weak input values.
Required review: Own every input, weight, and funding decision.
Primary risk: Release windows can imply capacity knowledge the workflow does not possess.
Required review: Confirm capacity, runway, dependencies, commitments, and rollout assumptions.
Primary risk: NFR thresholds, costs, stakeholders, and sign-offs may be inferred or invented.
Required review: Confirm scope, requirement quality, evidence, assumptions, NFRs, financials, stakeholders, and approval authority.
Primary risk: Identifier coverage can be mistaken for adequate design or requirement satisfaction.
Required review: Engineers, architecture, security, QA, and product stakeholders must assess substance.
Primary risk: The plan can only check the estimates and dependencies it was given. It cannot discover missing work or hidden capacity constraints.
Required review: Delivery leadership owns the plan and must inspect the CSV before import.
Each tool saves its output in this browser, newest first, one record per persona, initiative, or epic. The next tool lists the saved records, and you pick the one to build on. Each record also notes the exact version of every record it was built from.
A production version would add a history for each saved record, so an earlier version could be compared or restored, carry a person’s edits across a rerun, and share records across a team instead of one browser.