ba
starsforks
How to install ba?
rune-kit/rune/ba
$npx -y skills add Rune-kit/rune --skill baBusiness 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
SKILL.md
| 1 | # ba |
| 2 | |
| 3 | ## Purpose |
| 4 | |
| 5 | 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. |
| 6 | |
| 7 | > 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. |
| 8 | |
| 9 | > **Goal-first (advisory, 2026).** The Requirements Document is the goal spec current |
| 10 | > models want up front. Where the platform has a native goal/outcome command — Claude |
| 11 | > Code `/goal`, Managed Agents Outcomes (rubric) — seed it from this document's scope |
| 12 | > boundaries + acceptance criteria so the whole run stays anchored to the agreed WHAT. |
| 13 | |
| 14 | <HARD-GATE> |
| 15 | BA produces WHAT, not HOW. Never write code. Never plan implementation. |
| 16 | Output is a Requirements Document → hand off to rune:plan for implementation planning. |
| 17 | </HARD-GATE> |
| 18 | |
| 19 | ## Triggers |
| 20 | |
| 21 | - Called by `cook` Phase 1 when task is product-oriented (not a simple bug fix) |
| 22 | - Called by `scaffold` Phase 1 before any project generation |
| 23 | - `/rune ba <requirement>` — manual invocation |
| 24 | - Auto-trigger: when user description is > 50 words OR contains business terms (users, revenue, workflow, integration) |
| 25 | |
| 26 | ## Calls (outbound) |
| 27 | |
| 28 | - `scout` (L2): scan existing codebase for context |
| 29 | - `research` (L3): look up similar products, APIs, integrations |
| 30 | - `plan` (L2): hand off Requirements Document for implementation planning |
| 31 | - `brainstorm` (L2): when multiple approaches exist for a requirement |
| 32 | - `design` (L2): when requirements include UI/UX components — hand off visual requirements |
| 33 | |
| 34 | ## Called By (inbound) |
| 35 | |
| 36 | - `cook` (L1): before Phase 2 PLAN, when task is non-trivial |
| 37 | - `scaffold` (L1): Phase 1, before any project generation |
| 38 | - `plan` (L2): when plan receives vague requirements |
| 39 | - `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` |
| 40 | - `mcp-builder` (L2): requirements elicitation before MCP server design |
| 41 | - User: `/rune ba` direct invocation |
| 42 | |
| 43 | ## Cross-Hub Connections |
| 44 | |
| 45 | - `ba` → `plan` — ba produces requirements, plan produces implementation steps |
| 46 | - `ba` → `brainstorm` — ba calls brainstorm when multiple requirement approaches exist |
| 47 | - `ba` ↔ `cook` — cook calls ba for non-trivial tasks, ba feeds requirements into cook's pipeline |
| 48 | - `ba` → `scaffold` — scaffold requires ba output before project generation |
| 49 | |
| 50 | ## Executable Steps |
| 51 | |
| 52 | ### Step 1 — Intake & Classify |
| 53 | |
| 54 | Read the user's request. Classify the requirement type: |
| 55 | |
| 56 | | Type | Signal | Depth | |
| 57 | |------|--------|-------| |
| 58 | | Feature Request | "add X", "build Y", "I want Z" | Full BA cycle (Steps 1-7) | |
| 59 | | Bug Fix | "broken", "error", "doesn't work" | Skip BA → direct to debug | |
| 60 | | Refactor | "clean up", "refactor", "restructure" | Light BA (Step 1 + Step 4 only) | |
| 61 | | Integration | "connect X to Y", "integrate with Z" | Full BA + API research | |
| 62 | | Greenfield | "new project", "build from scratch" | Full BA + market context | |
| 63 | |
| 64 | If Bug Fix → skip BA, route to cook/debug directly. |
| 65 | If Refactor → light version (Step 1 + Step 4 only). Skip Steps 2, 2.5, 3, 5, 6. |
| 66 | |
| 67 | If existing codebase → invoke `rune:scout` for context before proceeding. |
| 68 | |
| 69 | ### Step 1.4 — Synthesis Trigger Check |
| 70 | <MUST-READ path="references/synthesis-mode.md" trigger="when prior conversation already contains rich requirement context (pasted spec, > 1000 words discussion, continuation session, filled issue template)"/> |
| 71 | |
| 72 | 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. |
| 73 | |
| 74 | Activate **Synthesis Mode** instead of standard elicitation if ANY of: |
| 75 | |
| 76 | | Signal | Threshold | |
| 77 | |--------|-----------| |
| 78 | | User pasted a spec / PRD / brief | > 200 words describing the feature | |
| 79 | | Conversation has > 1000 words on this feature | Sufficient context already gathered | |
| 80 | | User said "synthesize" / "I already explained" / "just write the spec" | Explicit synthesis request | |
| 81 | | Continuation — `.rune/features/<name>/requirements.md` exists with prior answers | Re-elicitation would duplicate | |
| 82 | | Issue tracker has filled-in template (problem, story, acceptance criteria) | Source already structured | |
| 83 | |
| 84 | In Synthesis Mode: extract answers from existing context, draft the Requirements Document |
People who liked this also viewed
6 picksType
- find-skillsHelps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skSkillsJul 2026
- grill-meA relentless interview to sharpen a plan or design.SkillsJul 2026
- vercel-react-best-practicesVercel's official collection of agent skillsSkillsJul 2026
- improve-codebase-architectureScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.SkillsJul 2026
- setup-matt-pocock-skillsConfigure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.SkillsJul 2026
- triageMove issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.SkillsJul 2026
