القائمة
[Meta] How to use BA-Kit effectively. Use when starting with BA-Kit, unsure which agent to invoke, or when an AI agent needs to map user intent to the right skill.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
[Agentic] Agile BA Practices - User Story Mapping, MVP Definition, Hypothesis-Driven Development
[Agentic] Business Rules Management - decision tables, decision trees, rule catalog, conflict detection
[Agentic] Change Management - ADKAR, readiness assessment, training needs, go-live planning, benefits realization
[Agentic] Communication & Reporting - audience-adapted messaging, status reports, executive summaries
[Agentic] Conflict Resolution & Negotiation - resolve stakeholder disagreements (SKILL-06)
[Agentic] Confluence Integration Bridge — publish BA docs to Confluence, import existing pages, sync specs with Transport Gate reflection
| name | using-ba-kit |
| description | [Meta] How to use BA-Kit effectively. Use when starting with BA-Kit, unsure which agent to invoke, or when an AI agent needs to map user intent to the right skill. |
| version | 1.0.0 |
When NOT to use:
@ba-writing)Every BA task fits one of 6 phases. Map task → phase → agent(s):
DISCOVER ANALYZE SPECIFY VALIDATE DELIVER AUDIT
┌──────────┐ ┌──────────┐ ┌──────────┐ ┌──────────┐ ┌──────────┐ ┌──────────┐
│ Who? │▶ │ What? │▶ │ How? │▶ │ Good? │▶ │ Ship! │▶ │ Review │
│ Why? │ │ Process │ │ Contract │ │ Test │ │ Deploy │ │ Health │
└──────────┘ └──────────┘ └──────────┘ └──────────┘ └──────────┘ └──────────┘
/ba-discover /ba-analyze /ba-specify /ba-validate /ba-deliver /ba-audit
| User Intent | Primary Skill | Chain |
|---|---|---|
| "New project, where to start?" | @ba-master | → identity → strategy → discover chain |
| "Who are the stakeholders?" | @ba-identity | → elicitation |
| "What's the business context?" | @ba-strategy | → systems → questioning |
| "Prepare me for a stakeholder meeting" | @ba-questioning | → elicitation |
| "Interview me about Login feature" | @ba-elicitation | → writing |
| "Who are the users really?" | @ba-ux | → writing |
| "Write User Stories for [feature]" | @ba-writing | → validation → test-gen |
| "Write BRD/SRS/FRD" | @ba-writing | → validation → export |
| "Visual scan this mockup" | @ba-writing | → validation |
| "Design data model for [module]" | @ba-data | → writing → consistency |
| "Document business rules" | @ba-business-rules | → test-gen |
| "Draw process flow / BPMN" | @ba-process | → writing |
| "Create Mermaid diagram" | @ba-diagram | → confluence |
| "Review this spec" | @ba-validation | → quality-gate |
| "Generate test cases from AC" | @ba-test-gen | → quality-gate |
| "Check consistency US vs API vs DB" | @ba-consistency | → traceability |
| "Score the BRD quality" | @ba-quality-gate | → writing (fix) |
| "Define NFRs / ISO 25010" | @ba-nfr | → validation |
| "Prioritize the backlog" | @ba-prioritization | → agile |
| "Stakeholders disagree, mediate" | @ba-conflict | → solution |
| "Calculate ROI / NPV" | @ba-solution | → prioritization |
| "Plan a workshop" | @ba-facilitation | → elicitation |
| "Plan go-live / training" | @ba-change | → communication |
| "Write status report / exec summary" | @ba-communication | → identity |
| "Create Jira tickets" | @ba-jira | → writing |
| "Publish to Confluence" | @ba-confluence | → diagram |
| "Export to DOCX" | @ba-export | — |
| "Root cause analysis / 5 Whys" | @ba-root-cause | → systems |
| "Design A/B test" | @ba-innovation | → metrics |
| "Measure quality trends" | @ba-metrics | → auditor |
| "Map traceability RTM" | @ba-traceability | → auditor |
| "Full project health audit" | @ba-auditor | — |
| "Search knowledge base" | @ba-wiki | — |
For Claude Code users, use slash commands to invoke whole phases:
| Command | Invokes |
|---|---|
/ba-discover | identity → strategy → questioning → elicitation → ux |
/ba-analyze | process / data / systems / business-rules (based on need) |
/ba-specify | writing → nfr → traceability → diagram |
/ba-validate | validation → quality-gate → consistency → test-gen → auditor |
/ba-deliver | export → jira → confluence → communication → change |
/ba-audit | auditor → traceability → consistency → metrics |
| Goal | Chain |
|---|---|
| Zero to BRD | strategy → elicitation → writing → validation → quality-gate → export |
| Sprint Planning | writing → validation → prioritization → jira |
| Screenshot to Ticket | writing (visual) → validation → test-gen → jira |
| Stakeholder War | identity → conflict → solution → facilitation |
| Production Postmortem | root-cause → validation → metrics → writing |
| Quality Audit | consistency → quality-gate → traceability → auditor |
| Confluence Docs | writing → diagram → export → confluence |
See docs/workflow-cookbook.md for 15 full scenarios.
When activated via @using-ba-kit (or when an agent needs to route):
Read the user's request. Classify:
Output a structured plan:
## Recommended Approach
Phase: [phase name]
Primary Agent: @ba-[name]
Chain: @ba-[1] → @ba-[2] → @ba-[3]
Rationale: [why this chain]
Estimated Time: [minutes/hours]
STOP & THINK.
@ba-validation? That's the most common mistake."Present the routing plan + rationale + first prompt the user should send.
Always recommend starting with the first agent in the chain.
| Rationalization | Reality |
|---|---|
| "I'll just ask ChatGPT directly, faster" | Generic LLMs don't enforce INVEST, BABOK, or System 2 Reflection. You'll get plausible-looking output that fails review. |
| "I know what I'm doing, no need for @ba-master" | Even experts benefit from the routing safety net. Skipping leads to missed handoffs. |
| "This is a simple task, one agent is enough" | 90% of "simple" BA tasks cross 2-3 domains (e.g., Writing + NFR + Validation). Single-agent = incomplete output. |
| "I'll validate later" | You won't. The spec ships without validation 80% of the time. Run /ba-validate immediately after /ba-specify. |
| "Skipping discovery because I already know the domain" | Assumptions kill projects. Even a 10-minute @ba-questioning session catches hidden constraints. |
@ba-writing without any context or persona@ba-validation is skipped between Writing and Delivery@ba-master route for ambiguous intentAfter routing a request, confirm:
docs/README.md, docs/agent-cheat-sheet.md, docs/workflow-cookbook.md.claude/commands/ba-*.mdActivation Phrase: "Usage Guide ready. Describe the task — I'll route you to the right skill."