# Byte Plan

> Create an appropriately detailed execution plan. Use when the user explicitly asks for a plan, roadmap, implementation approach, sequencing, dependencies, or acceptance criteria before execution.

- Skill: `elan6666/byte-plan` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds@latest add elan6666/byte-plan`
- Raw SKILL.md: https://api.skillmd.com/api/skills/elan6666/byte-plan/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Product & Planning
- Author: elan6666 (https://skillmd.com/u/elan6666)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/elan6666/byte-plan

---


# Byte Plan

Plan only to the depth that improves execution. Inspect relevant context before
planning, and prefer a short actionable plan over project-management theater.

## Choose The Planning Depth

- Small, clear task: a few ordered actions in chat.
- Multi-file or multi-stage task: a concise plan with dependencies and checks.
- Long-running or collaborative task: persistent plan files and state may help.

Do not require OKRs, waves, owner roles, subagent fields, or a fixed number of
plans unless the project actually needs them.

## Useful Plan Content

Every plan should make three things understandable:

- the result being pursued;
- the next meaningful actions and important dependencies;
- how completion will be checked.

Add scope boundaries, touched areas, risks, alternatives, or rollout steps when
they affect execution. Resolve low-risk details during implementation rather than
enumerating them prematurely.

For an existing codebase, use repository instructions and live inspection. A
missing Byte OS artifact or harness is not by itself a planning blocker.

Apply relevant active lessons before planning. If evidence or user correction
confirms a reusable wrong assumption, update `.byte-os/LESSONS.md` with the
corrected premise and prevention rule. Do not log ordinary plan revision.

Save plans only when they need to survive the current turn, coordinate multiple
tracks, or support resumption. Reuse the project's existing planning convention;
otherwise prefer `.byte-os/PLAN.md` over many mandatory plan files.

Planning is complete when another capable agent could begin safely without the
plan pretending to eliminate all judgment.

## Long-Running Boundaries

Default complex execution plans to bounded actionable goals. For training or
another long external job, plan a preparation goal
whose acceptance includes the monitoring design and ends before launch, a
launch-and-monitor handoff, and monitor shutdown before any post-run goal.
Never plan an active goal and enabled monitor for the same workflow together. Keep final project acceptance separate from each
phase. Follow [the long-running workflow](references/long-running-work.md)
when designing these boundaries; planning alone does not authorize goal tools,
job execution, or scheduled checks.

## Source And Updates

Canonical repository: [elan6666/your-bytedance-skills](https://github.com/elan6666/your-bytedance-skills). Use its current `main` branch when checking for or installing updates.