跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
设计与 UI

build-feature

Use when the user runs /build-feature or asks to implement or build a feature end to end. Don't use when a bug is already in play, for typos, comments, formatting, docs-only work, or when the user only wants a single leaf skill.

AlemTuzlak · 已有 AI 审核记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add AlemTuzlak/skills --skill build-feature

技能说明


name: build-feature description: Use when the user runs /build-feature or asks to implement or build a feature end to end. Don't use when a bug is already in play, for typos, comments, formatting, docs-only work, or when the user only wants a single leaf skill.

Build Feature

Run the full feature path. This skill is the driver. It loads other pack skills. It does not invent a third planning method.

Leaves stay callable alone. This is the only pack skill that names them for a pipeline, besides fix-bug offering prove-it.

When To Use

Load when the user runs /build-feature, or asks to implement / build a feature (including a refactor that is not a failure).

Skip if a failure is already in play. That job is fix-bug. Skip typos, comments, format, docs-only. Skip if they only asked for one leaf (/touch-map, /lego-plan, and similar).

Hard Gates

  1. No production code until plan 2 is approved. Spec and DAG first.
  2. Two blocks. Plan 1 (design spec) must be approved. Plan 2 (implementation plan + DAG) must be approved. Silence is not approval. approved, go, yes, or looks good counts.
  3. grill-me is the only interview. Do not run Superpowers brainstorming questions.
  4. Do not commit the spec file or the plan file.
  5. Same-layer nodes run in parallel. Do not use Superpowers subagent-driven-development as the dispatcher (that loop is one task, then review, then the next).
  6. Every implementer subagent must be told to load typescript-standards, test-hygiene, reuse-first, and docs. Pass the confirmed reader list and tone. Workers do not re-ask persona or tone. Workers do not get grill-me, touch-map, lego-plan, writing-plans, or prove-it.
  7. Do not load prove-it until the end ask. Default skip. A green DAG is not proof.
  8. The driver paints. Subagents never paint. After every live-board status change, the next user-visible message MUST contain a full Mermaid of the board. done nodes are green (:::done). A JSON write, a prose recap, a todo list, or waiting until the layer (or the whole run) ends does not count. If several subagents return in one wake, paint once with every new status. Do not skip the fence because more than one finished.

Flow

grill-me (or skip if design is already settled)
  → docs Phase 1 + persona gate (stop)
  → write spec, open, wait for approved          [block 1]
  → touch-map
  → reuse-first (once, on files-to-touch)
  → lego-plan
  → writing-plans file from the DAG, open, wait  [block 2]
  → one tone gate if any node writes docs pages
  → implement layers in parallel; driver paints DAG after each return
  → optional prove-it

Load each named skill and follow it. Overrides in this file win where they conflict (writing-plans grain, no sequential dispatcher, do not commit those two files, driver paints the live DAG). lego-plan forbids classDef on the plan emit. This driver paint is the exception.

Paint the live DAG

The user-facing product during implement is the colored Mermaid, not the JSON.

The driver (this conversation, the main agent) paints. A worker subagent must not emit the live DAG. Ignore a worker mermaid if one appears.

Paint after:

  1. Setting a ready layer to in-progress, before spawn.
  2. Each subagent return (this conversation wakes). First actions: update JSON from done when, then paint in the user-visible reply, then continue.
  3. Marking a node red.

The paint is a fenced mermaid block in chat. Tool logs and subagent transcripts are not the paint.

Form (ids match the live board; apply :::pending / :::inprogress / :::done / :::failed from JSON status):

flowchart TD
  classDef pending fill:#e5e7eb,stroke:#9ca3af,color:#111
  classDef inprogress fill:#fde68a,stroke:#d97706,color:#111
  classDef done fill:#86efac,stroke:#16a34a,color:#111
  classDef failed fill:#fca5a5,stroke:#dc2626,color:#111
  fetch-order[fetch-order]:::done
  order-card[order-card]:::inprogress
  wire-loader[wire-loader]:::pending
  fetch-order --> wire-loader
  order-card --> wire-loader

Keep every node and the same edges. Do not drop finished nodes. :::done is green so the user can see what landed.

Procedures

Procedure 1: Route

  1. If a test is red, CI is red, or the user says it is broken / fix this: stop. Tell them to use fix-bug. Do not start this flow.
  2. Else Procedure 2.

Procedure 2: Grill or skip

  1. If this conversation already has a settled design (grill already done, or they pasted a spec): do not run grill-me. Write or copy it to the plan-1 path if that file is missing. Then Procedure 3.
  2. Else load grill-me and follow it until the design is shared. Then Procedure 3.
  3. If the spec file already exists and they already approved it in this conversation and readers are already confirmed: Procedure 5.

Procedure 3: Docs readers (persona gate)

  1. Load docs. Run Phase 1 only: who reads this, and which pages are new or changed.
  2. Show the persona list in chat. Stop. That message is the turn.
  3. After they confirm, drop, or add readers: Procedure 4.
  4. If readers were already confirmed in this conversation: skip the wait. Procedure 4.

Procedure 4: Write spec (plan 1) and block

  1. Path: docs/superpowers/specs/YYYY-MM-DD-<topic>-design.md (today’s date, kebab topic). New file. Create parent dirs if needed.
  2. Write a short design spec: what we build, choices from the grill, confirmed readers, doc-impact pages. Not a task list. Not full source.
  3. Open the file. Do not git add it. Do not commit it.
  4. Wait until they approve. If they want changes: edit, open, wait again.
  5. Procedure 5.

Procedure 5: Map, reuse, lego

  1. Load touch-map and follow it (six-section map, then it stops).
  2. Load reuse-first once on the files-to-touch list. Record the reuse: line. The DAG must not invent a helper that this pass found.
  3. Load lego-plan and follow it (chat D
阅读完整来源 ↗