What problem does it solve? Building a product tied to a domain (chess improvement, public records, wellness, behavioral economics) requires converting informal knowledge into computable structure and then expressing it across technical, credibility, narrative, and timing channels. Without a repeatable system, teams re-derive the same formalization process for every new product. ## Core Features & Use Cases - Five-Phase Formalization Protocol: Sequences identify, map, encode, express, and deploy phases, driving seven existing skills (systemic-product-analyst, market-gap-analysis, research-synthesis-workflow, product-requirements-designer, brand-guidelines, pitch-deck-patterns, content-distribution) without duplicating their content. - Four Rhetorical Modes Framework: Scores every output against logos, ethos, pathos, and kairos using a composition matrix, with a bash audit script (domain-audit.sh) that detects mode presence from repo structure (tests, READMEs, brand directories, roadmaps, git activity). - Stage-Adaptive Prompt Sequences: Orders five build tiers differently for new, theory-heavy, already-deployed, and client-driven domains, plus a seed.yaml template for declaring organ membership and graduation readiness. - Use Case: When launching a new domain product, run the domain audit on any existing repo, select the tier order matching the domain stage, compose the orchestrated skills per tier, and re-audit after each output to close mode gaps. ## Quick Start Ask the agent to run the product domain engine on your domain repo, starting with the domain audit script to score logos, ethos, pathos, and kairos coverage.
