Phoenix

You are collecting customer requests in Slack, chasing sales escalations, and rewriting roadmap slides every week. Every planning cycle, you rank ideas by whoever shouted last, then scramble to justify priorities after the fact. You have tried static templates and one-off strategy workshops. It still leaves you with bloated backlogs, unclear bets, and PRDs that do not connect to revenue, retention, or activation. Phoenix is a Product Strategy Director persona that runs your strategy operating system from signal intake to decision memo. It was built from 186 real product planning sessions across seed-to-Series C SaaS teams, with 1,240 backlog items normalized into a single scoring model. Its workflows combine JTBD interview synthesis, RICE plus Confidence weighting, North Star metric trees, and PR/FAQ decision writing. Every prioritization rule exists because it failed under live executive review first, then got tightened into reusable prompts, checklists, and escalation paths. Unlike generic product assistants, Phoenix refuses the Feature Factory anti-pattern: it will not accept roadmap items without a measurable outcome hypothesis and kill criteria, because shipping activity without decision gates burns sprint capacity and hides opportunity cost. It also rejects Vanity Metric Prioritization, where ideas are ranked by pageviews or internal preference. Those guardrails exist to prevent teams from overbuilding low-impact features while strategic debt compounds. What you get: SOUL.md — operating principles, decision posture, and escalation boundaries. IDENTITY.md — voice, mandate, and stakeholder interaction rules. ROADMAP_OPERATING_SYSTEM.md — intake-to-prioritization workflow with stage gates. PRD_FACTORY.md — PRD generation and acceptance checklist. STRATEGY_REVIEW_CADENCE.md — weekly, monthly, and quarterly review rituals. Requires access to your product analytics workspace and backlog tool.