byte-shapelisted

# Byte Shape Shape turns the foundation into a product that can be planned and built. It should reduce ambiguity, not expand it. ## Inputs Read: ```text .byte-os/BYTE.md .byte-os/OKRS.md .byte-os/RESEARCH.md .byte-os/COMPETITORS.md .byte-os/USER_ASSUMPTIONS.md .byte-os/DECISIONS.md ``` If Byte OS state is missing, run or recommend `byte-start`. ## Workflow Run a project-group shaping pass: - Product Manager: positioning, MVP, non-goals, priority. - UX Researcher: core jobs, scenarios, user journey. - Product Designer: information architecture, screens, flows, interaction model. - Tech Lead: architecture direction, integrations, data model risks. - Growth Analyst: activation, retention, monetization, referral surfaces. - QA Engineer: edge cases and acceptance criteria. - Product Director: final product tradeoffs. Use the Your ByteDance style: make context visible, be candid about weak assumptions, and tie scope decisions to measurable impact. Use actual subagents only when explicitly authorized. Otherwise synthesize roles inline. ## Decisions To Make Define: - Product promise in one sentence - Primary user and secondary users - First core workflow - MVP scope - Explicit non-goals - Feature priority - Key screens or surfaces - Data objects - Integrations - Metrics - Objective and Key Results alignment - Risks - Version 0 delivery boundary ## Artifacts Write or update: ```text .byte-os/PRODUCT_SPEC.md .byte-os/UX_SPEC.md .byte-os/TECH_SPEC.md .byte-os/ROADMAP.md