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

ba

Business Analyst agent. Use when starting a new feature requiring requirements elicitation BEFORE plan or cook. Asks probing questions, identifies hidden requirements, maps stakeholders, defines scope boundaries, and produces a structured Requirements Document that plan and cook consume.

Rune-kit · 已有 AI 审核记录

安装与使用

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

npx skills add Rune-kit/rune --skill ba

技能说明


name: ba description: "Business Analyst agent. Use when starting a new feature requiring requirements elicitation BEFORE plan or cook. Asks probing questions, identifies hidden requirements, maps stakeholders, defines scope boundaries, and produces a structured Requirements Document that plan and cook consume." metadata: author: runedev version: "1.2.1" layer: L2 model: opus group: creation tools: "Read, Write, Glob, Grep" emit: outofscope.match, outofscope.recorded

ba

Purpose

Business Analyst agent — the ROOT FIX for "Claude works a lot but produces nothing." BA forces deep understanding of WHAT to build before any code is written. It asks probing questions, identifies hidden requirements, maps stakeholders, defines scope boundaries, and produces a structured Requirements Document.

Wrong requirements shipped correctly is the most expensive bug. BA's job is to prevent it — measure clarity (Step 2.5), measure completeness (Step 3.5), and measure cross-dimension consistency (Step 3.6) before handoff.

Goal-first (advisory, 2026). The Requirements Document is the goal spec current models want up front. Where the platform has a native goal/outcome command — Claude Code /goal, Managed Agents Outcomes (rubric) — seed it from this document's scope boundaries + acceptance criteria so the whole run stays anchored to the agreed WHAT.

Triggers

  • Called by cook Phase 1 when task is product-oriented (not a simple bug fix)
  • Called by scaffold Phase 1 before any project generation
  • /rune ba <requirement> — manual invocation
  • Auto-trigger: when user description is > 50 words OR contains business terms (users, revenue, workflow, integration)

Calls (outbound)

  • scout (L2): scan existing codebase for context
  • research (L3): look up similar products, APIs, integrations
  • plan (L2): hand off Requirements Document for implementation planning
  • brainstorm (L2): when multiple approaches exist for a requirement
  • design (L2): when requirements include UI/UX components — hand off visual requirements

Called By (inbound)

  • cook (L1): before Phase 2 PLAN, when task is non-trivial
  • scaffold (L1): Phase 1, before any project generation
  • plan (L2): when plan receives vague requirements
  • brainstorm (L2): standalone ideation that picked an approach for a new feature with no spec — hands the chosen approach to ba for requirements before plan
  • mcp-builder (L2): requirements elicitation before MCP server design
  • User: /rune ba direct invocation

Cross-Hub Connections

  • ba → plan — ba produces requirements, plan produces implementation steps
  • ba → brainstorm — ba calls brainstorm when multiple requirement approaches exist
  • ba ↔ cook — cook calls ba for non-trivial tasks, ba feeds requirements into cook's pipeline
  • ba → scaffold — scaffold requires ba output before project generation

Executable Steps

Step 1 — Intake & Classify

Read the user's request. Classify the requirement type:

TypeSignalDepth
Feature Request"add X", "build Y", "I want Z"Full BA cycle (Steps 1-7)
Bug Fix"broken", "error", "doesn't work"Skip BA → direct to debug
Refactor"clean up", "refactor", "restructure"Light BA (Step 1 + Step 4 only)
Integration"connect X to Y", "integrate with Z"Full BA + API research
Greenfield"new project", "build from scratch"Full BA + market context

If Bug Fix → skip BA, route to cook/debug directly. If Refactor → light version (Step 1 + Step 4 only). Skip Steps 2, 2.5, 3, 5, 6.

If existing codebase → invoke rune:scout for context before proceeding.

Step 1.4 — Synthesis Trigger Check

Before proceeding to elicitation, check whether the requirements are already in context. Re-asking what the user already told you is the second-most expensive bug.

Activate Synthesis Mode instead of standard elicitation if ANY of:

SignalThreshold
User pasted a spec / PRD / brief> 200 words describing the feature
Conversation has > 1000 words on this featureSufficient context already gathered
User said "synthesize" / "I already explained" / "just write the spec"Explicit synthesis request
Continuation — .rune/features/<name>/requirements.md exists with prior answersRe-elicitation would duplicate
Issue tracker has filled-in template (problem, story, acceptance criteria)Source already structured

In Synthesis Mode: extract answers from existing context, draft the Requirements Document with source citations for every section, then confirm rather than re-interview. Ask follow-ups ONLY on the 1-2 dimensions with genuine gaps. Skip steps 2, 2.5 if all 5 dimensions are filled or partial-but-acceptable.

Workflow detail + anti-patterns: references/synthesis-mode.md.

Step 1.5 — Out-of-Scope Match Check (READ)

Before any elicitation, check whether the request matches a concept previously rejected.

  1. Glob .out-of-scope/*.md — if directory absent, skip silently.
  2. For each file, parse YAML frontmatter (concept, aliases).
  3. Build a token map (lowercased, split on - and whitespace).
  4. Tokenize the user's request the same way.
  5. Compute lexical overlap per concept; keep the top match's confidence (0.0–1.0).

Action by confidence:

ConfidenceVerdictAction
≥ 0.8exact-matchSurface to user: *"This matches a prior rejection (.out-of-scope/<slug>.md) — closed beca
阅读完整来源 ↗