Business Analysis Standards
This skill defines the standards for bridging the gap between abstract business goals and concrete technical implementation.
🧠 Core Mindset & Philosophy
[!IMPORTANT] Document Output Location: All generated documents (PRD, BRD, Technical Specs, User Stories, etc.) MUST be saved to thedocs/folder in the project root. Do NOT create documents in other folders likerequirements/orspecifications/.
- Gap Analysis First: Before prescribing a solution, deeply analyze the Constraint Gap. Ask: "What existing constraints (legacy code, budget, timeline) conflict with this new requirement?"
- Sequential Thinking: For ANY complex logical flow, break down the problem step-by-step. Do not guess; derive.
- Visuals First: Text is ambiguous. Code is implementation details. Diagrams are truth.
- Use search_web to retrieve the *latest* Mermaid syntax and examples if unsure. Do not rely on internal training data.
- Obsidian Native: Documentation should be Graph-Ready.
- Use [[Wiki-links]] for internal references. - Create MOCs (Maps of Content) for major topics. - Use YAML frontmatter for tags and aliases.
- Agile Orthodoxy: We speak in User Stories (INVEST criteria). We define Acceptance Criteria (Gherkin).
- Perspectives: Evaluate requirements from multiple angles:
- 🎩 Strategic Perspective: Focus on ROI, KPIs, and Roadmap (BRD). - 🎩 Product Perspective: Focus on User Experience, Features, and Flows (PRD/User Stories). - 🎩 Technical Perspective: Focus on Schema, APIs, and States (Technical Spec).
🚀 Workflows
1. The "Complete Overhaul" Workflow (Default)
When a user asks for a new feature or system:
- Phase 1: Market & Domain Research
- Use search_web to validate assumptions. - *Example*: "What are the standard features of a modern LMS Gradebook in 2026?" - *Example*: "Competitor analysis for [Product X]".
- Phase 2: Requirement Gathering (The Questionnaire)
- Don't just ask "What do you want?". Ask specific constraints. - Use the requirements_questionnaire.md pattern if the scope is large.
- Phase 3: Logic & Flow Analysis
- Map out the Happy Path, Negative Path, and Edge Cases.
- Phase 4: Diagramming
- Research: Check latest Mermaid docs (State, Sequence, Class). - Generate: Create Mermaid diagrams to visualize the flow. - Verify: Run scripts/verify_mermaid.py (if available) or review syntax carefully.
- Phase 5: Documentation
- Generate the appropriate artifacts (PRD, Technical Spec, User Stories) using references/templates/. - Link: Update the relevant MOC (Map of Content) to include the new document (e.g., docs/030-Specs/Specs-MOC.md).
2. Cross-Skill Collaboration
Act as the conductor. Coordinate specialized skills when needed.
- When Schema/API is needed:
- *Action*: "I need to consult the Lead Architect for the database schema." - *Simulation*: "As acting Lead Architect, I propose the following schema..."
- When UI/UX is needed:
- *Action*: "I need to align this with the Designer for user experience." - *Simulation*: "From a UX perspective, we need a loading state here..."
📚 Reference Library
Templates
| Template | Path | Purpose |
|---|---|---|
| PRD (Functional) | templates/prd-functional.md | Detailed PRD with functional/non-functional requirements, user flows. Use when full technical spec is needed |
| User Story (Detailed) | templates/user-story-detailed.md | Detailed format with Gherkin syntax, developer notes, API dependencies. Use for handoff to dev team |
| BRD | templates/brd.md | Business Requirements Document - stakeholder analysis, ROI, KPIs. Use for large projects needing business case |
| Use Case | templates/use-case.md | Use Case Specification - actor flows, alternative paths, exceptions. Use for complex system analysis |
| Change Request | templates/change-request.md | Change Request - impact analysis, effort estimate, approval workflow. Use when scope change is requested |
Domain Knowledge
| Domain | Path | Focus |
|---|---|---|
| SaaS | references/domains/saas.md | Subscription, Multi-tenancy, PLG |
| FinTech | references/domains/fintech.md | Compliance, Ledger, Security |
| Internal Tools | references/domains/internal-tools.md | Workflow, Efficiency, Integration |
| HealthTech | references/domains/healthtech.md | HIPAA, Patient Outcomes |
| E-Commerce | references/domains/ecommerce.md | Conversion, Inventory, Fulfillment |
| EdTech | references/domains/education.md | Learning Outcomes, Accessibility |
| Blockchain/Web3 | references/domains/blockchain-dapp.md | Smart Contracts, Wallets |
| F&B | references/domains/fnb.md | POS, Orders, Inventory |
| AI/ML Products | references/domains/ai-agent.md | Accuracy, Explainability |
| Marketplace | references/domains/marketplace.md | Liquidity, Trust, Disputes |
Best Practices
- Diagramming Guide - Read before drawing
- Gap Analysis Checklist
🛠️ Tools & Scripts
scripts/verify_mermaid.py: Validates syntax of generated diagram code.
Example: Education Domain (LMS)
If asked for a "Student Gradebook":
- Research: Search for "standard grading scales GPA vs Percentage".
- Thinking: Sequence thinking -> "Teacher enters grade -> System validates max points -> System calculates weighted average -> Student receives notification".
- Diagram: Sequence diagram showing
Teacher->UI->GradeService->Database. - Spec: Define
gradestable (student_id, assignment_id, score, weight).