--- name: synthesise-product-architecture description: Architect a digital product around a realistic customer transformation, differentiated mechanism, bounded promise, delivery model and measurable completion criteria. license: MIT compatibility: Agent Skills-compatible agents; supporting files are loaded progressively. metadata: author: astisme --- # Synthesise Product Architecture Design from customer transformation, not content volume. Owns `product-charter.md`; curriculum and commercial offer design remain separate specialist responsibilities. ## Inputs A selected or explicitly provisional opportunity, audience/problem evidence, creator constraints and validation findings where available. Identify unvalidated assumptions. ## Method 1. Describe the customer's starting and target states. 2. Define observable completion evidence and realistic success criteria. 3. Bound the promise; state exclusions, prerequisites and dependencies. 4. Identify the unique mechanism and why it fits the audience's job. 5. Compare course, cohort, toolkit, workshop, playbook, membership, productized service and software/AI workflow. 6. Select format based on job complexity, support, access, cost, feasibility and willingness to engage. 7. Map transformation milestones and high-level modules/deliverables. 8. Define journey, onboarding, support, accessibility, maintenance and risks. 9. Create a production roadmap and prioritized backlog. 10. Review promise against evidence and delivery capacity. ## Canonical output: product-charter.md Positioning; audience/buying context; problem; transformation; promise/scope/exclusions; mechanism; alternatives; format rationale; architecture; journey; support; success metrics; assumptions/risks; validation evidence; commercial hypotheses; roadmap. ## Quality gates Promise is specific, realistic and evidence-bounded; every component advances an outcome; prerequisites/exclusions/support boundaries are explicit; delivery is feasible; privacy, safety and accessibility are considered. ## Progressive methodology reference Load `references/product-transformation-architecture.md` whenever performing substantive product architecture work. Use it to deepen the procedure, decision criteria and quality review; keep this `SKILL.md` as the concise entry point. The reference is additive and does not supersede shared contracts, approved decisions or the frozen v1.1.0 methodology. ## Shared evidence and handoff contract - Distinguish verified facts, user-provided claims, external research, analytical interpretations, hypotheses, recommendations and unknowns. Never silently promote one state into another. - Preserve evidence provenance and limitations: stable evidence ID, claim, type, source/locator, date, status, confidence, scope/segment, sample size where relevant, limitations and consuming artifacts. Reuse does not upgrade evidence strength. - This skill owns its canonical artifact. Other specialists may propose changes but must not silently overwrite it; cross-owner changes require owner/user approval. - Every handoff reports skill ID, project ID, objective, inputs used, outputs created, decisions proposed, decisions requiring approval, assumptions, evidence, limitations, next recommended skills and completion status. - Before completion, check required sections, output names, evidence support, explicit assumptions/limitations, ownership, project continuity and actionable next steps. State blockers rather than claiming completion. ## Handoff Curriculum may expand learning architecture but must not redefine the product promise. Monetization must align with approved scope.