ciee-product-architect

Define a testable product architecture and prioritized feature map for the CIEE app.

Updated Feb 22, 2026
One-click install
npx skills add https://github.com/tracyarciaga/ixl-olympics --skill ciee-product-architect
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ciee-product-architect
Source: https://github.com/tracyarciaga/ixl-olympics/tree/main/my-skills/ciee-product-architect
Command: npx skills add https://github.com/tracyarciaga/ixl-olympics --skill ciee-product-architect

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Defines a clear, testable product architecture and prioritized feature map that aligns the CIEE app's Student and Parent experiences with measurable business outcomes such as conversion, payment completion, community retention, and parent trust.

Core Features & Use Cases

  • User journeys to screens: Translate Student and Parent lifecycle stages into concrete screens and modules (Study Planner, AI Match, Wallet & Payment, Parent Approval, Community Join, AI Advisor).
  • MVP prioritization: Distinguish must-have flows for a rapid demo from phase 2 features, tying each feature to a measurable KPI.
  • Handoff artifacts: Produce an architecture blueprint, prioritized roadmap, and KPI definitions for engineering and design handoff.
  • Use Case: For a launch demo, map the checkout-to-parent-approval flow end-to-end, prioritize the minimal payment and approval screens, and define KPIs to measure payment completion and approval latency.

Quick Start

Map Student and Parent journeys into screens, produce a prioritized MVP feature map tied to specific KPIs for conversion, payment completion, retention, and parent trust.

Frequently Asked Questions about ciee-product-architect

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I map user journey stages to concrete app screens for an MVP?

Map user journey stages to screens by translating Student and Parent lifecycle phases into specific modules like Study Planner, AI Match, and Wallet & Payment. This produces a testable product architecture with screen-level mappings for rapid demo delivery.

What is the best way to prioritize MVP features tied to measurable KPIs?

Prioritize MVP features by distinguishing must-have flows for a rapid demo from phase 2 features, tying each feature to a measurable KPI. This approach aligns features with business outcomes like conversion, payment completion, and parent trust.

How do I define a product architecture for parent approval and payment flows?

Define a product architecture for parent approval and payment flows by mapping the checkout-to-parent-approval journey end-to-end. Prioritize minimal payment and approval screens, then define KPIs to measure payment completion and approval latency.

Can I generate implementation-ready handoff artifacts for engineering and design?

Yes, you can generate implementation-ready handoff artifacts including an architecture blueprint, prioritized roadmap, and KPI definitions. These artifacts facilitate seamless engineering and design handoff for rapid demo and phased delivery.

How do I structure a product architecture for both student-facing and parent-facing app experiences?

Structure a dual-sided product architecture by aligning Student and Parent experiences with measurable business outcomes. Map lifecycle stages into concrete screens and modules, covering scenarios like study planning, AI matching, wallet payments, and community joins.

What KPIs should I track for conversion and retention in a student-parent app?

Track KPIs for conversion, payment completion, community retention, and parent trust. Tie each prioritized feature to these measurable business outcomes to ensure the product architecture validates user lifecycle success across student and parent flows.