Back to Details

beads-create

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Beads Create

Beads 创建

Use this skill to create Beads from a plan/spec and do the review pass so implementers can just pick up issues and ship.
使用此技能根据计划/规格创建Beads，并完成审核环节，以便实施人员可以直接接手议题并推进交付。

Workflow

工作流程

  1. Load beads guidance if needed
    • If bd CLI usage or bead structure is unclear, consult the official Beads GitHub repo at 
      https://github.com/steveyegge/beads
      and follow the documented workflow for your installed 
      bd
      version.
  2. Decide which mode you are in
    • If the user has a finalized plan/spec and wants Beads filed: do Create mode.
    • If the user already has Beads and wants them improved: do Review mode (skip straight to step 5).
  3. Confirm the plan is ready (Create mode)
    • Ensure there is a finalized plan or spec outside Beads.
    • If the plan is still fuzzy, ask for revisions first and iterate up to 5 times before importing.
  4. Translate the plan into Beads structure (Create mode)
    • Create epics that map to major milestones or deliverables.
    • Create issues for concrete, implementable tasks.
    • Hierarchy rule: When an epic has child milestones/tasks, create them as hierarchical children (dotted IDs like 
      EPIC.1
      , 
      EPIC.2
      ) rather than separate top-level issues with only parent-child deps. Follow the bd CLI “Create epic with hierarchical child tasks” flow (create the epic, then create children so bd auto-assigns 
      EPIC.N
      IDs). Verify the returned IDs; if bd doesn’t assign dotted IDs, stop and ask the user how to proceed.
    • Add dependencies, ordering constraints, and opportunities for parallel work.
  5. Review and polish (Create mode + Review mode)
    • Fix vague titles, missing acceptance criteria, or unclear scope.
    • Ensure each issue is something one agent can do in a single task.
    • Verify dependencies, sequencing, and opportunities for parallel work.
    • Add missing design notes / decision context.
    • Split oversized issues; merge duplicates; delete fluff.
  6. Add implementation detail
    • Include design notes, assumptions, and acceptance criteria on each issue.
    • Make tasks small and unambiguous so a fresh agent can pick up a single issue.
  7. Single-pass
    • Do one focused pass in the current context.
    • If another pass is needed, say so explicitly and recommend a separate follow-up run.
  8. Restart the agent
    • Finish this task, then stop. Encourage a fresh agent for the next task to keep sessions small.
  1. 如有需要，查阅Beads指南
    • 如果对bd CLI的使用或Beads结构不清晰，请访问官方Beads GitHub仓库
      https://github.com/steveyegge/beads
      ，并按照已安装的
      bd
      版本对应的文档流程操作。
  2. 确定当前模式
    • 如果用户已有定稿的计划/规格并希望创建Beads：使用创建模式。
    • 如果用户已拥有Beads并希望优化：使用审核模式（直接跳至步骤5）。
  3. 确认计划已就绪（创建模式）
    • 确保存在Beads之外的已定稿计划或规格。
    • 如果计划仍不明确，先要求用户修订，最多迭代5次后再导入。
  4. 将计划转换为Beads结构（创建模式）
    • 创建对应主要里程碑或交付成果的史诗（epics）。
    • 创建具体可实施的任务议题（issues）。
    • 层级规则：当史诗包含子里程碑/任务时，将其创建为层级子项（如
      EPIC.1
      、
      EPIC.2
      这类带点的ID），而非仅设置父子依赖关系的独立顶级议题。遵循bd CLI的“创建包含层级子任务的史诗”流程（先创建史诗，再创建子项，以便bd自动分配
      EPIC.N
      格式的ID）。验证返回的ID；如果bd未分配带点的ID，请停止操作并询问用户如何处理。
    • 添加依赖关系、排序约束以及可并行开展的任务机会。
  5. 审核与优化（创建模式 + 审核模式）
    • 修正模糊的标题、缺失的验收标准或不明确的范围。
    • 确保每个议题都是单个Agent可以在一项任务中完成的内容。
    • 验证依赖关系、任务顺序以及可并行开展的任务机会。
    • 添加缺失的设计说明/决策背景。
    • 拆分过大的议题；合并重复项；删除冗余内容。
  6. 添加实施细节
    • 在每个议题中包含设计说明、假设条件和验收标准。
    • 确保任务规模小且明确，以便新接手的Agent可以直接处理单个议题。
  7. 单次处理
    • 在当前上下文内完成一次专注的处理。
    • 如果需要再次处理，请明确说明并建议单独进行后续操作。
  8. 重启Agent
    • 完成当前任务后停止。建议使用新的Agent处理下一个任务，以保持会话规模精简。

Output expectations

输出要求

  • Provide a concise mapping of epics and issues you created.
  • Call out any dependencies or blockers that need user confirmation.
  • If asked to iterate beyond 5 plan revisions, say you do not think it can be improved further.
  • 提供所创建的史诗和议题的简明映射关系。
  • 指出任何需要用户确认的依赖关系或阻塞点。
  • 如果被要求对计划进行超过5次的迭代修订，请告知用户认为无法进一步优化。