Ba kit

BA-kit — Business Analysis Workstation

BA-kit biến AI agent thành một BA workstation có lifecycle rõ ràng, artifact có cấu trúc, và handoff chuẩn cho stakeholder/engineering.

Capabilities

• Full BA lifecycle: intake → backbone → FRD → stories → SRS → wireframe handoff → package
• Change impact triage: phân tích ảnh hưởng trước khi sửa artifact
• NLP routing: dùng ngôn ngữ tự nhiên, agent tự route đúng workflow
• Multi-module governance: phân chia module, review, conflict detection
• Template-backed artifacts: mọi deliverable đều có template chuẩn
• Quality gates: cross-artifact consistency, traceability, SMART validation

Quick Start

User nói	BA-kit làm
"Tạo dự án BA mới"	Chạy intake: parse input → gap analysis → scope lock
"Tiếp tục dự án warehouse-rfp"	Detect next step → recommend + execute
"Đánh giá thay đổi: thêm audit log"	Impact analysis → recommend rerun path
"Chuẩn bị handoff UI cho module auth"	Build wireframe constraint pack
"Xuất gói bàn giao"	Package → compiled HTML

Defaults

• Language: Vietnamese (override with English on request)
• Mode: hybrid (backbone + targeted FRD + stories + selective SRS)
• UI baseline: Shadcn UI (overridden by project DESIGN.md)
• Date format: YYMMDD-HHmm

Lifecycle Order

intake → backbone → frd → stories → srs → wireframes → package → status

Routing

When user uses natural language, route intent:

User says	Route to
Tạo dự án mới / phân tích tài liệu mới	intake
Tiếp tục dự án / bước tiếp theo	Inspect artifacts → next step
Đánh giá thay đổi / thêm yêu cầu / sửa requirement	impact
Bare correction statement	impact
Chuẩn bị handoff UI / wireframe constraints	wireframes
Xuất gói bàn giao / export HTML	package
Kiểm tra trạng thái	status
Directly naming a step (backbone, frd, stories, srs)	That step

Priority: When ambiguous between impact and direct edit → prefer impact unless user explicitly says "update", "overwrite", "regenerate", or "rerun".

After routing, display:

BA-kit Routing
Input: {short excerpt}
Routing to: {command}
Reason: {one-line reason}

Directory Structure (Output)

plans/
  {slug}-{YYMMDD-HHmm}/
    PROJECT-HOME.md
    01_intake/intake.md, plan.md
    02_backbone/backbone.md, project-memory.md
    03_modules/{module_slug}/frd.md, user-stories.md, srs.md,
                             wireframe-input.md, wireframe-map.md
    04_compiled/compiled-frd.html, compiled-srs.html
designs/
  {slug}/DESIGN.md

Commands & Prerequisites

Command	Module Required	Requires	Outputs
intake	No	raw input	project_home, intake, plan
backbone	No	intake	backbone, project_memory
frd	Yes	backbone	frd
stories	Yes	backbone	stories
srs	Yes	backbone + stories	srs, wireframe_input
wireframes	Yes	wireframe_input	design_doc, wireframe_map
package	No	at least one artifact	compiled HTML
impact	No	intake	analysis only
status	No	—	inspection only

Resolution Rules

• Slug: explicit --slug → inspect directories → ambiguous = stop and ask
• Date: explicit --date → derive from directory → ambiguous = stop and ask
• Module: explicit --module → single module = use it → multiple = stop and ask

Critical Behavior Rules

1. Fail-Closed: Never silently choose slug/date/module. If ambiguous → stop and ask.
2. Overwrite Protection: Before mutating any artifact, check if exists → ask approval.
3. Impact-First: Never mutate artifacts from bare correction → route through impact.
4. Source of Truth: backbone > intake (once backbone exists).
5. Large Artifact Protocol: >150 lines → write skeleton first, append incrementally.
6. Exact Matching Only: Never infer from partial filenames or mtime.
7. Execution Lock: After user approves mutating rerun → keep locked, don't reopen discovery.

Quality Standards

• Every requirement: clear source, business rationale, testable, SMART
• Stories: As a/I want/so that + Given/When/Then AC + INVEST
• Cross-artifact consistency: UC ↔ Screen ↔ Stories ↔ FRD (same wording)
• Centralized rules: CR-{TYPE}-{NN}, messages: MSG-{TYPE}-{NN}
• Never copy-paste rules between screens — centralize and reference
• Material uncertainty → stop and ask (never fill with plausible prose)

Anti-Patterns (NEVER)

• ❌ Copy-paste rules between screens
• ❌ Redefine portal/nav behavior in final screen descriptions
• ❌ Leave orphaned requirements without business justification
• ❌ Bundle multiple behaviors in one requirement statement
• ❌ Guess missing upstream context (stop and ask instead)
• ❌ Delegate assembly/merge of large artifacts

Reference Files

For detailed instructions per step, load the appropriate reference:

Task	Reference File
Full contract (paths, states)	references/contract-data.md
Behavior policy	references/contract-behavior.md
Intake steps	references/steps-intake.md
Backbone steps	references/steps-backbone.md
FRD steps	references/steps-frd.md
Stories steps	references/steps-stories.md
SRS core (Groups A/B/C)	references/steps-srs-core.md
SRS wireframes (Groups D/E)	references/steps-srs-wireframes.md
SRS assembly (Group F)	references/steps-srs-assembly.md
Wireframe handoff	references/steps-wireframes.md
HTML packaging	references/steps-package.md
Impact triage	references/impact.md
Quality rules	references/quality-rules.md
Templates catalog	references/templates.md
Multi-BA delegation	references/delegation.md
Agent specs	references/agents.md
Collaboration & GitHub	references/skill-collab.md
Notion publishing	references/skill-notion.md
Next step detection	references/skill-next.md

Engagement Modes

Mode	Artifacts	When
lite	intake + backbone + stories	Simple, low-risk
hybrid	+ targeted FRD/SRS	Default for solo IT BA
formal	Full suite	Governance, vendor handoff

Wireframe States

• completed — handoff pack ready
• skipped — user chose to skip
• not-applicable — no UI-backed screens
• missing — expected but not done (blocks package)

Next Step Detection

Check artifacts in order and recommend first missing:

1. No intake → run intake
2. Intake exists, no backbone → run backbone
3. Backbone exists, FRD required but missing → run frd
4. Stories missing → run stories
5. SRS required and missing → run srs
6. Wireframe-input exists, wireframe-state missing → run wireframes
7. Final markdown exists, no HTML → run package
8. Everything exists → run status