菜单
Pre-build interview that decomposes a new build into Streams, Currents, Checkpoints, and Scenarios before Pulse planning. Use before Architect writes PLAN.md whenever a build needs structured decomposition.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Automated build orchestration system. Spawns headless Zo workers (Drops) in parallel Waves, monitors health, validates Deposits via LLM judgment, handles dead Drops, and escalates via SMS. Supports sequential Streams within Waves. Replaces manual Build Orchestrator for unattended execution.
Close normal interactive conversation threads. Handles tier detection, position extraction, AAR generation, and commit suggestions. For Pulse workers use drop-close. For post-build synthesis use build-close.
Meeting ingestion pipeline v3 with calendar triangulation, CRM enrichment, org classification, quality gates, HITL queue, and canonical S-shape generation. Unified CLI for transcript processing from ingest to archive.
Close Pulse worker (Drop) threads. Writes structured deposit JSON for orchestrator review. Does NOT commit - that's the orchestrator's job. For normal threads use thread-close. For post-build synthesis use build-close.
Improve layout, spacing, and visual rhythm. Fixes monotonous grids, inconsistent spacing, and weak visual hierarchy to create intentional compositions.
Post-build synthesis for Pulse builds. Aggregates all deposits, synthesizes decisions and learnings, extracts positions, generates build AAR. Replaces N per-worker closes with 1 build-level close. For normal threads use thread-close. For Pulse workers use drop-close.
基于 SOC 职业分类
| name | pulse-interview |
| description | Pre-build interview that decomposes a new build into Streams, Currents, Checkpoints, and Scenarios before Pulse planning. Use before Architect writes PLAN.md whenever a build needs structured decomposition. |
| compatibility | Created for Zo Computer |
| metadata | {"author":"va.zo.computer","version":"1.0.0"} |
| created | "2026-06-10T00:00:00.000Z" |
| last_edited | "2026-06-10T00:00:00.000Z" |
| version | 1 |
| provenance | con_sQ03t9FFBWIVZTXO |
Pre-build interview to decompose work into Streams, Currents, Checkpoints, and Scenarios.
Use before any build that will use Pulse orchestration.
These become Streams.
These become Currents.
These are strategic quality gates at high-risk junctures.
Identify build type:
Identify high-risk handoffs:
Place checkpoints:
| Build Type | Common Checkpoint Placements |
|---|---|
| API | After schema, before frontend integration |
| Data Pipeline | After ingest, after transform |
| Frontend | After components, before deploy |
| Integration | After both sides built, before E2E |
These inform the Learning Landscape in the plan.
These become Scenarios in each Drop brief.
For each major deliverable, extract:
Format each scenario as:
S1: <Descriptive name>
Given: <Initial state or precondition>
When: <Action or trigger>
Then: <Expected observable outcome>
Verify: <Executable command or "LLM: <what to check>">
Verify clause guidance:
Target: 3-5 scenarios per Drop. More for complex Drops, fewer for simple ones.
Generate in N5/builds/<slug>/:
meta.json — build metadata with streams, drops, checkpointsdrops/D*.md — Drop briefsdrops/C*.md — Checkpoint briefs