byte-statuslisted

# Byte Status Status reports where the Your ByteDance project stands and what should happen next. ## Workflow 1. Check whether `.byte-os/` exists. 2. Read `STATUS.md` if present. 3. Inspect core artifacts: ```text BYTE.md OKRS.md RESEARCH.md COMPETITORS.md USER_ASSUMPTIONS.md BRAINSTORM.md DISCUSSION.md PRODUCT_SPEC.md UX_SPEC.md TECH_SPEC.md CODEBASE_MAP.md HARNESS.md AGENTS_AUDIT.md ROADMAP.md BUILD_LOG.md DELIVERY.md ``` Also check whether root `AGENTS.md` and relevant module `AGENTS.md` files exist when the project is an existing codebase. 4. Inspect directories: ```text plans/ reviews/ iterations/ users/ subagents/ ``` 5. Count plan statuses: ```text pending ready in_progress complete blocked ``` 6. Identify next action: - No `.byte-os/`: `byte-start` - `BRAINSTORM.md` exists but no chosen direction or specs: `byte-discuss` - Stage is discussing or `DISCUSSION.md` exists but no specs: `byte-shape` - Started but no specs: `byte-shape` - Existing codebase but no harness: `byte-codebase-harness` - Existing codebase with missing, stale, or bloated `AGENTS.md`: `byte-codebase-harness` - Specs but no plans: `byte-plan` - Plans incomplete: `byte-build` - Build complete but no review: `byte-review` - Review says iterate or block: `byte-iterate` - Review says ship: `byte-deliver` - Real feedback provided: `byte-users` ## Output Return: ```text Stage: Progress: Objective: Key Results: Artifacts: Plans: Reviews: Iterations: Real user feedback: Brainstorm: Discussion: