Byte shape

Skill elan6666/your-bytedance-skills/byte-shape

Shape a Your ByteDance / Byte OS project into product positioning, MVP scope, non-goals, user flows, UX structure, technical direction, metrics, OKRs, and an initial roadmap. Use after byte-start or byte-research, or when the user asks to define what the product should be before implementation.From its SKILL.md

Install

npx -y skills add elan6666/your-bytedance-skills --skill byte-shape

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.8 KB, 617 tokens by cl100k_base, as published. Nobody here has run it

Byte Shape

Shape turns the foundation into a product that can be planned and built. It should reduce ambiguity, not expand it.

Do not pull parked entries from .byte-os/FUTURE.md into the MVP, specs, or roadmap. Only the user's explicit promotion can return an entry to the active discuss, research, or shape workflow.

Inputs

Read:

.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:

.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/STATUS.md
.byte-os/DECISIONS.md

PRODUCT_SPEC.md must include:

Positioning
Target users
Problems and jobs to be done
MVP
Non-goals
Requirements
Acceptance criteria

UX_SPEC.md must include:

Core user journey
Screen or page list
Navigation model
Empty, loading, error, and success states
First-run experience

TECH_SPEC.md must include:

Proposed architecture
Data model
APIs or integrations
Implementation risks
Testing strategy

ROADMAP.md must include:

v0 deliverable
v1 improvements
Later opportunities

Update STATUS.md using the shared Byte OS state contract:

stage: shaped
current_workflow: byte-shape
next_workflow: byte-plan

Completion Criteria

The step is complete when a team can create executable plans without asking what the product is supposed to do.

What ships with it: 1 file

197 B alongside SKILL.md

agents/

openai.yaml197 B