Byte discuss

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

Your own ByteDance, powered by Codex skills.

Install

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

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.

What its author says it does

Copied from the file, not written here

Discuss and clarify Your ByteDance / Byte OS product requirements before planning or building. Use when the user wants to discuss requirements, clarify an idea, ask what is unclear, confirm scope, compare product directions, or explicitly says not to write code yet.

SKILL.md

3.0 KB, as published. Nobody here has run it

Byte Discuss

Discuss is the requirement-clarification mode. It helps the user turn a rough idea into confirmed product direction without starting implementation.

For broad idea expansion, use $byte-brainstorm only when the user explicitly invokes it. Do not silently switch discussion into brainstorm mode.

Boundaries

Do not write product code.
Do not run byte-auto, byte-build, or implementation steps.
Do not create final plans unless the user asks to move into byte-plan.
You may create or update .byte-os/DISCUSSION.md to preserve the conversation, unless the user asks for discussion only with no files.
If .byte-os/ already exists, read current BYTE.md, PRODUCT_SPEC.md, UX_SPEC.md, TECH_SPEC.md, OKRS.md, and STATUS.md when present.

Workflow

Restate the current understanding in 3-6 bullets.
Identify unclear or risky requirement areas.
Ask targeted questions automatically.
Offer reasonable default assumptions for low-risk gaps.
Confirm the next action: continue discussion, start, shape, plan, or auto.

Question Rules

Ask only questions that affect product scope, UX, technical direction, business goal, delivery format, or acceptance criteria.

Use this priority order:

Target user and primary job to be done
Core problem and success outcome
MVP scope and non-goals
First user flow
Data, integrations, accounts, permissions, or external dependencies
Platform and delivery format
Quality bar, timeline, and constraints

Ask at most 7 questions per pass. Group them as:

Must confirm:
Nice to confirm:
Suggested defaults:

If the user gives enough context, do not keep interrogating. Move to a confirmation summary and recommend the next Byte OS step.

Discussion Output

Return:

Current understanding:
Unclear points:
Questions:
Suggested defaults:
Confirmed scope:
Non-goals:
Risks:
Recommended next:

When writing state, create or update:

.byte-os/DISCUSSION.md
.byte-os/STATUS.md

DISCUSSION.md should include:

Date
User request
Current understanding
Open questions
Suggested defaults
Confirmed decisions
Non-goals
Recommended next command

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

stage: discussing
current_workflow: byte-discuss
next_workflow: <shared resolver result>

Handoff

Recommend:

byte-start when no Byte OS project exists and the user confirms the idea.
byte-shape when the idea is clear enough to become specs.
byte-plan when specs already exist and only execution breakdown remains.
byte-auto only when the user explicitly wants one-click completion.

Completion Criteria

Discuss is complete when the user has a concise confirmation checklist and the next Byte OS command is clear.