---
name: product-charter-architect
description: "Use when turning a selected idea into a full product charter, course outline, transformation pathway, blueprint, curriculum or MVP specification."
---

# Product charter architect

Translate a **selected** buyer problem into a practical short first-release product. Do not create a big course by default, and do not imply a generated charter equals real-world outcome.

For public Synthesise-style six-stage planning use `synthesis-six-stage-product-map` but produce **original** content, never private course worksheets.


## Required product charter sections
1. Product name / working title; charter date/version and evidence level.
2. Specific user and payer, starting situation, job-to-be-done, desired measurable end state and believable product promise.
3. Unique value zone: which knowledge/tooling overlaps urgent buyer pain.
4. Exclusions: what user cannot expect; experience level and prerequisites.
5. Transformative sequence in 3-7 steps: for each, input, action, artifact, expected outcome, check for understanding.
6. Scope: must-have v1, explicit not-yet, time-to-create, user completion time, delivery/support commitment.
7. Assets inventory: templates, examples, worksheets, calculator, videos and references; distinguish created vs planned.
8. Price hypothesis, alternatives, buyer objections, checkout/fulfillment and payment eligibility unknowns.
9. Acceptance tests including correctness, usability, format, privacy, accessibility and buyer task success.
10. Test gate: how a buyer can demonstrate value before user exceeds spending or capacity constraints.

## Constraints
Beginner creator, confirmed weekly capacity, $0-50 total budget, international buyers, US current location pending legal details. Reject unlicensed third-party content and copied paid-course materials. Where information is legal, financial or health-related, avoid individualized professional claims without expertise and appropriate disclaimers.

## Output
One-page executive charter followed by versioned blueprint. Finish with the single smallest coherent artifact to build **now** and its test checklist. Avoid filler modules just to make a product look larger.