byte-planlisted

Convert Your ByteDance / Byte OS specs into dependency-aware executable plans. Use when the product has been shaped and needs multiple plan files for design, engineering, testing, launch, OKR execution, or when the user asks to break the product into project plans before building.
elan6666/your-bytedance-skills · ★ 1 · AI & Automation · score 60

Install: claude install-skill elan6666/your-bytedance-skills

# Byte Plan Plan splits shaped product work into small, executable plan files. Plans are the unit that `byte-build` executes. ## Inputs Read: ```text .byte-os/PRODUCT_SPEC.md .byte-os/UX_SPEC.md .byte-os/TECH_SPEC.md .byte-os/ROADMAP.md .byte-os/OKRS.md .byte-os/DECISIONS.md .byte-os/CODEBASE_MAP.md .byte-os/HARNESS.md .byte-os/AGENTS_AUDIT.md AGENTS.md and relevant module AGENTS.md files ``` If these are missing, run or recommend `byte-shape`. ## Planning Rules - Create plans that can be executed independently when dependencies allow. - Prefer wave-based parallelism over strict 1-to-N order. - Keep write scopes clear to reduce conflicts. - For engineering work, apply `byte-code-rules`: simple scope, surgical changes, explicit assumptions, and verifiable success criteria. - Include acceptance criteria in every plan. - Include verification steps in every plan. - Connect every plan to at least one Objective or Key Result. - Mark dependencies explicitly. - Break every plan into explicit ordered steps: Step 1, Step 2, Step 3, etc. - Each step must state what to do, why it is needed, touched files or modules, expected output, and how to verify that step. - For existing codebases, use `.byte-os/CODEBASE_MAP.md` and `.byte-os/HARNESS.md` to choose the relevant start directory, applicable `CLAUDE.md`/`AGENTS.md`, and scoped commands. - Build an `AGENTS.md` context stack for each plan: root `AGENTS.md`, then the nearest module `AGENTS.md` files that apply to `start_directory`.