Mission
Product — codename VECTOR — translates strategy into roadmaps, requirements, and shipped releases. The team's job is to make sure the studio is building the right thing, in the right order, for the right reason.
How they work together
Four lanes: management (orchestration, prioritization, releases), requirements (PRDs, user stories, acceptance criteria), research (user research, feedback synthesis, experiments), and analytics (metrics, A/B testing, experiment tracking). The pattern: product-manager sets the cycle, prd-writer or requirements-generator scopes the work, product-engineer maps it to technical capabilities, and sprint-prioritizer sequences it into a 6-day cycle.
For launches, project-shipper owns release coordination and stakeholder communication. For experiments, experiment-tracker runs the A/B framework and analytics-reporter synthesizes the results.
Best practices
- Write the PRD before the code. prd-writer produces testable requirements with explicit acceptance criteria. No ambiguity at handoff.
- 6-day cycles, no exceptions. sprint-prioritizer plans for value delivery in one sprint. Multi-sprint features get split.
- Feedback compounds. feedback-synthesizer runs continuously, not just before launches. Patterns surface from volume.
- Experiments need stop conditions. experiment-tracker sets the success threshold and the kill date before the test starts.
Do's
- Use product-manager as the orchestrator for cross-team initiatives.
- Pull in product-engineer the moment a customer use case meets a technical capability gap.
- Hand launches to project-shipper — they own go-to-market, not just code freeze.
- Let experiment-tracker pause work when an experiment is mid-flight; you don't ship into an active test.
Don'ts
- Don't ship without acceptance criteria. prd-writer writes them; engineering signs off on them.
- Don't measure success by ship date. analytics-reporter measures it by outcome metrics.
- Don't conflate research with validation. ux-researcher explores; experiment-tracker confirms.
Common tools
Read, Write, Edit, Grep, Glob — for PRDs, specs, and roadmaps. WebSearch / WebFetch for competitive and market research. TodoWrite for sprint and launch coordination.
When to call on Product
New features, prioritization decisions, launch planning, A/B tests, or any moment where "what should we build next?" needs an answer with evidence behind it.