@jhm1909/ag-kit 0.1.0

package/.agent/skills/business-analysis/references/domains/fnb.md

@@ -0,0 +1,82 @@
+# F&B (Food & Beverage) Domain Reference
+
+## Core Modules
+
+### Menu Management
+
+- Categories, subcategories
+- Items (name, description, images, pricing)
+- Modifiers and add-ons (extra cheese, size options)
+- Combo meals, set menus
+- Seasonal/limited items
+- Nutritional information, allergens
+
+### Order Management
+
+- Order types: Dine-in, Takeaway, Delivery
+- Order lifecycle: received → preparing → ready → served/delivered
+- Table management (for dine-in)
+- Kitchen display system (KDS)
+- Order modifications, special requests
+
+### POS (Point of Sale)
+
+- Cash register integration
+- Payment processing (cash, card, e-wallets, QR codes)
+- Receipt printing
+- Split bills, tips
+
+### Inventory & Kitchen
+
+- Ingredient inventory
+- Recipe management (ingredients per item)
+- Stock alerts, low stock warnings
+- Waste tracking
+- Supplier management
+
+### Delivery & Logistics
+
+- Delivery zones, radius
+- Delivery fees calculation
+- Driver assignment, tracking
+- Integration with delivery platforms (GrabFood, ShopeeFood)
+
+## Common Features
+
+### Customer Experience
+
+- Mobile ordering (app, QR code)
+- Loyalty programs, stamps, points
+- Reservations, waitlist
+- Customer feedback, ratings
+
+### Multi-location
+
+- Branch management
+- Centralized menu with local variations
+- Cross-location reporting
+- Staff assignment per location
+
+### Marketing
+
+- Promotions, happy hours
+- Discount codes, vouchers
+- Push notifications
+- Social media integration
+
+## User Roles
+
+- **Customer**: Order, pay, review
+- **Cashier**: POS operations
+- **Kitchen Staff**: View orders, update status
+- **Manager**: Reports, inventory, staff
+- **Admin**: Full system access
+
+## Key Metrics
+
+- Revenue per day/week/month
+- Average order value (AOV)
+- Table turnover rate
+- Food cost percentage
+- Customer satisfaction (NPS)
+- Order fulfillment time

package/.agent/skills/business-analysis/references/domains/healthtech.md

@@ -0,0 +1,44 @@
+# Domain: HealthTech (Healthcare)
+
+## 1. Core Mindset
+
+- **Privacy First**: HIPAA (USA) / GDPR (EU) compliance is non-negotiable.
+- **Interoperability**: Systems must talk (FHIR, HL7 standards).
+- **Data Integrity**: Lives are at stake. Zero tolerance for data errors.
+
+## 2. Key Terminology (Glossary)
+
+- **PHI (Protected Health Information)**: Any data identifying a patient + health info.
+- **HIPAA**: US law protecting PHI.
+- **EMR/EHR**: Electronic Medical/Health Record.
+- **FHIR (Fast Healthcare Interoperability Resources)**: Modern standard for exchanging health data.
+- **Telemedicine**: Remote delivery of healthcare.
+- **Triage**: Prioritizing patients based on severity.
+
+## 3. Common Entities (Data Models)
+
+- **Patient**: The user. `mrn` (Medical Record Number), `dob`.
+- **Provider**: Doctor/Nurse. `npi` (National Provider Identifier), `specialty`.
+- **Appointment**: `patient_id`, `provider_id`, `time`, `reason`.
+- **Observation**: Vital signs (BP, Heart Rate). FHIR Resource.
+
+## 4. Key Workflows
+
+### A. Appointment Booking
+
+1.  **Availability Search**: Query Provider schedule.
+2.  **Booking**: Create `Appointment` (status: scheduled).
+3.  **Confirmation**: Email/SMS to Patient (No PII in subject line!).
+
+### B. Telehealth Session
+
+1.  **Check-in**: Patient enters virtual waiting room.
+2.  **Provider Join**: Video session starts (WebRTC, HIPAA compliant encrypted).
+3.  **SOAP Note**: Provider documents Subjective, Objective, Assessment, Plan.
+4.  **Billing**: Generate claim (ICD-10 codes).
+
+## 5. Regulatory Compliance Checklist
+
+- [ ] **Encryption**: At rest and in transit.
+- [ ] **Access Logs**: Who viewed what record and when? (Audit Trail).
+- [ ] **BAA (Business Associate Agreement)**: Required for all vendors handling PHI (e.g., AWS, Twilio).

package/.agent/skills/business-analysis/references/domains/internal-tools.md

@@ -0,0 +1,38 @@
+# Internal Tools & Platforms Domain
+
+## Overview
+
+Internal tools are software built for internal stakeholders (employees, operations teams). Focus is on workflow efficiency and integration with existing systems.
+
+## Key Entities
+
+- **Employee/User**: With department, role, permissions
+- **Workflow**: Process steps, Approvals, Escalations
+- **Case/Ticket**: Support cases, operational tasks
+- **Report**: Analytics, exports, dashboards
+
+## Common Use Cases
+
+1. **Task Management**: Create, assign, track, close tasks
+2. **Approval Workflows**: Request → Review → Approve/Reject
+3. **Data Entry/Validation**: Forms with business rule validation
+4. **Reporting**: Generate reports, schedule exports
+5. **Integration Hub**: Sync data between systems
+
+## Key Metrics to Document
+
+- **Time to Resolve (TTR)**: How long to complete a task
+- **Task Completion Rate**: Success vs abandonment
+- **Error Rate**: Mistakes requiring rework
+- **Adoption Rate**: % of employees using the tool
+- **Time Saved**: Efficiency gains vs manual process
+
+## BA Considerations
+
+- **Existing Process Mapping**: Document current state before designing
+- **User Shadowing**: Observe real users in their environment
+- **Edge Cases**: What happens when things go wrong
+- **Offline Capability**: Some environments lack reliable internet
+- **Permission Complexity**: Often complex role hierarchies
+- **Legacy Integration**: APIs, file exports, database syncs
+- **Training Needs**: Users may resist change

package/.agent/skills/business-analysis/references/domains/marketplace.md

@@ -0,0 +1,52 @@
+# Marketplace / Platform Domain
+
+## Overview
+
+Marketplace platforms connect buyers and sellers (or service providers and consumers). BA focus is on balancing needs of multiple user types and trust mechanisms.
+
+## Key Entities
+
+- **Buyer**: Consumer, Shopper, Renter
+- **Seller**: Merchant, Service Provider, Host
+- **Listing**: Product, Service, Property
+- **Transaction**: Order, Booking, Rental
+- **Review**: Ratings, Feedback, Disputes
+
+## Common Use Cases
+
+### Seller Side
+
+1. **Onboarding**: Register → Verify identity → Create first listing
+2. **Listing Management**: Create, edit, deactivate listings
+3. **Order Fulfillment**: Accept order, Ship/Deliver, Confirm completion
+4. **Payout Management**: View earnings, Request payout, Tax documents
+
+### Buyer Side
+
+1. **Discovery**: Search, Filter, Compare listings
+2. **Purchase Flow**: Add to cart → Checkout → Payment
+3. **Communication**: Message seller, Inquire about product
+4. **Post-Purchase**: Track order, Request refund, Leave review
+
+### Platform Side
+
+1. **Dispute Resolution**: Buyer vs Seller conflict handling
+2. **Fraud Prevention**: Suspicious activity detection
+3. **Commission/Fees**: Take rate calculation, Payment splitting
+
+## Key Metrics to Document
+
+- **GMV**: Gross Merchandise Value
+- **Take Rate**: Platform commission percentage
+- **Buyer/Seller Ratio**: Market liquidity
+- **Repeat Transaction Rate**: Customer retention
+- **Time to First Transaction**: Onboarding efficiency
+
+## BA Considerations
+
+- **Chicken-and-Egg**: Can't have buyers without sellers (and vice versa)
+- **Trust Mechanisms**: Reviews, Verification badges, Escrow
+- **Payment Splitting**: Platform fee, Seller payout, Tax handling
+- **Dispute Flow**: Who wins when buyer says "not delivered"?
+- **Fraud Patterns**: Fake reviews, Shill bidding, Payment fraud
+- **Category-Specific Rules**: Different flows for goods vs services

package/.agent/skills/business-analysis/references/domains/saas.md

@@ -0,0 +1,36 @@
+# SaaS (Software as a Service) Domain
+
+## Overview
+
+SaaS products are cloud-based software solutions delivered on a subscription basis. BA focus is on user journeys, subscription management, and self-service capabilities.
+
+## Key Entities
+
+- **Tenant/Organization**: Multi-tenant architecture considerations
+- **User Roles**: Admin, Member, Guest, Billing Admin
+- **Subscription**: Plan, Billing Cycle, Usage Limits
+- **Feature Flags**: Entitlements per plan tier
+
+## Common Use Cases
+
+1. **User Onboarding**: Sign up → Email verify → First-time setup wizard
+2. **Team Management**: Invite users, Assign roles, Remove members
+3. **Subscription Management**: Upgrade, Downgrade, Cancel, Pause
+4. **Usage Tracking**: Quota monitoring, Overage alerts
+5. **Self-Service Support**: Knowledge base, Ticket submission
+
+## Key Metrics to Document
+
+- **ARR/MRR**: Annual/Monthly Recurring Revenue
+- **Churn Rate**: Customer attrition
+- **LTV/CAC**: Lifetime Value vs Customer Acquisition Cost
+- **DAU/MAU**: Daily/Monthly Active Users
+- **NPS**: Net Promoter Score
+
+## BA Considerations
+
+- **Multi-tenancy**: Data isolation between customers
+- **Plan Gating**: Which features at which tier
+- **Trial Logic**: Time-limited trials, feature-limited trials
+- **Billing Integration**: Stripe, Paddle, Chargebee patterns
+- **SSO/SAML**: Enterprise authentication requirements

package/.agent/skills/business-analysis/references/workflows/collaboration.md

@@ -0,0 +1,41 @@
+# Cross-Skill Collaboration Workflow
+
+## 1. Interaction Model
+
+The Business Analyst (BA) defines **WHAT** and **WHY**.
+
+- The **Lead Architect** defines **HOW** (Backend/Data).
+- The **Designer** defines **HOW** (Frontend/UX).
+- The **Product Manager** approves **WHEN** (Scope/Roadmap).
+
+## 2. Integration Points
+
+### With `lead-architect`
+
+- **Trigger**: When functional requirements need concrete technical details (Schema, API, Stack).
+- **Prompt**:
+  > "I have defined the User Stories for [Feature]. Acting as Lead Architect, please transform this into a Technical Specification, specifically defining the DB Schema and API Endpoints."
+- **Validation**:
+  - Does the Schema support the "Given" preconditions?
+  - Do the API error codes cover the "Negative Paths"?
+
+### With `designer`
+
+- **Trigger**: When requirements involve user interaction (UI).
+- **Prompt**:
+  > "I have defined the User Flow for [Feature]. Acting as Designer, please propose a wireframe description or Component Hierarchy that meets these accessibility requirements."
+- **Validation**:
+  - Does the design include the "Empty States" identified?
+  - Are verification steps (e.g., "Confirm Email") visible?
+
+### With `product-manager`
+
+- **Trigger**: When scope creep happens or priorities are unclear.
+- **Prompt**:
+  > "We identified 5 edge cases. Acting as Product Manager, should we include these in MVP or defer to Phase 2?"
+
+## 3. Simulation Mode
+
+If other skills are not explicitly active in the agent session, the BA must **simulate** their persona to generate complete specs.
+
+- _Self-Correction_: "Speaking as the Architect, that query is too expensive. Let's denormalize..."

package/.agent/skills/business-analysis/scripts/verify_mermaid.py

@@ -0,0 +1,86 @@
+import sys
+import re
+import subprocess
+import shutil
+
+def check_mermaid_cli():
+    """Check if mmdc (Mermaid CLI) is installed."""
+    return shutil.which("mmdc") is not None
+
+def validate_mermaid_content(content):
+    """
+    Validates Mermaid syntax.
+    1. Basic Regex checks for common errors.
+    2. (Optional) Runs mmdc --dry-run if available.
+    """
+    errors = []
+    
+    # Check 1: Empty content
+    if not content.strip():
+        return ["Error: Diagram content is empty."]
+
+    # Check 2: Known Diagram Types
+    valid_starts = [
+        "flowchart", "graph", "sequenceDiagram", "classDiagram", 
+        "stateDiagram", "erDiagram", "gantt", "pie", "journey", 
+        "gitGraph", "C4Context"
+    ]
+    
+    first_line = content.strip().split('\n')[0].strip()
+    # Remove options like 'flowchart TD' -> 'flowchart'
+    diagram_type = first_line.split(' ')[0]
+    
+    if diagram_type not in valid_starts:
+        errors.append(f"Warning: Unknown or missing diagram type '{diagram_type}'. Supported: {', '.join(valid_starts)}")
+
+    # Check 3: Brackets balance (simple check)
+    if content.count('{') != content.count('}'):
+        errors.append("Error: Mismatched curly braces '{}'.")
+    
+    # Check 4: Sequence Diagram participants
+    if diagram_type == "sequenceDiagram":
+        if "participant" not in content and "->" not in content and "-->>" not in content:
+             errors.append("Warning: Sequence diagram appears to lack interactions (arrows).")
+
+    return errors
+
+def main(filepath):
+    try:
+        with open(filepath, 'r') as f:
+            content = f.read()
+            
+        print(f"Validating {filepath}...")
+        errors = validate_mermaid_content(content)
+        
+        if errors:
+            print("❌ Validation Failed:")
+            for err in errors:
+                print(f"  - {err}")
+            sys.exit(1)
+        else:
+            print("✅ Syntax looks plausible (regex check).")
+            
+            # Optional: Real validation using CLI
+            if check_mermaid_cli():
+                print("Running mmdc (Mermaid CLI) for strict validation...")
+                try:
+                    # Run a dry run or output to null
+                    subprocess.run(["mmdc", "-i", filepath, "-o", "/dev/null"], check=True, capture_output=True)
+                    print("✅ mmdc validation passed.")
+                except subprocess.CalledProcessError as e:
+                    print("❌ mmdc validation failed:")
+                    print(e.stderr.decode())
+                    sys.exit(1)
+            else:
+                 print("ℹ️  mmdc not found. Skipping strict CLI validation. Install @mermaid-js/mermaid-cli for better checks.")
+
+    except FileNotFoundError:
+        print(f"Error: File {filepath} not found.")
+        sys.exit(1)
+
+if __name__ == "__main__":
+    if len(sys.argv) < 2:
+        print("Usage: python verify_mermaid.py <path_to_mermaid_file>")
+        sys.exit(1)
+        
+    main(sys.argv[1])

package/.agent/skills/business-analysis/templates/brd.md

@@ -0,0 +1,46 @@
+# Business Requirements Document (BRD)
+
+## 1. Executive Summary
+
+- **Project Name**: ...
+- **Sponsor**: ...
+- **Objective**: High-level goal (e.g., "Increase conversion by 20%").
+- **Key Driver**: Why now? (e.g., Compliance, Market opportunity).
+
+## 2. Business Problem
+
+- **Current State**: Description of the pain point or inefficiency.
+- **Proposed Solution**: High-level description of the change.
+- **Scope**:
+  - **In Scope**: ...
+  - **Out of Scope**: ...
+
+## 3. Business Value (ROI)
+
+- **Tangible Benefits**: Revenue increase, cost saving ($).
+- **Intangible Benefits**: Brand reputation, user satisfaction.
+- **Success Metrics (KPIs)**:
+  - KPI 1: ...
+  - KPI 2: ...
+
+## 4. Stakeholder Analysis
+
+| Stakeholder Group | Impact (High/Med/Low) | Needs/Interests      |
+| :---------------- | :-------------------- | :------------------- |
+| Finance           | High                  | Accurate reporting   |
+| Customer Support  | Med                   | Training on new tool |
+
+## 5. Market Analysis
+
+- **Competitor Overview**: ...
+- **Target Market**: ...
+
+## 6. High-Level Requirements
+
+- **BR-01**: Must support multi-currency.
+- **BR-02**: Must integrate with SAP.
+
+## 7. Risks & Constraints
+
+- **Risks**: Regulatory changes, Technical debt.
+- **Constraints**: Budget cap, Strict deadline.

package/.agent/skills/business-analysis/templates/change-request.md

@@ -0,0 +1,41 @@
+# Change Request (CR)
+
+## 1. Change Summary
+
+- **CR ID**: CR-[YYYY]-[Number]
+- **Date**: YYYY-MM-DD
+- **Requestor**: [Name/Dept]
+- **Title**: ...
+
+## 2. Description of Change
+
+- **Current Functionality**: ...
+- **Requested Change**: ...
+- **Reason/Business Justification**: Why is this needed now? What happens if we don't do it?
+
+## 3. Impact Analysis
+
+### Technical Impact
+
+- **Files/Modules Affected**: ...
+- **Complexity**: Low/Med/High
+- **Risks**: Regression in [Feature X].
+
+### Project Impact
+
+- **Effort Estimate**: [Hours/Days]
+- **Cost Impact**: [$]
+- **Schedule Delay**: [Days]
+
+## 4. Recommendation
+
+- [ ] **Approve** (Proceed immediately)
+- [ ] **Defer** (Move to Backlog/Next Phase)
+- [ ] **Reject** (Out of scope/Not feasible)
+
+## 5. Approval
+
+| Role            | Name | Signature | Date |
+| :-------------- | :--- | :-------- | :--- |
+| Project Manager |      |           |      |
+| Client Sponsor  |      |           |      |

package/.agent/skills/business-analysis/templates/prd-functional.md

@@ -0,0 +1,38 @@
+# Product Requirements Document (PRD)
+
+## 1. Introduction
+
+- **Problem**: What user problem are we solving?
+- **Goals**: Success metrics (KPIs).
+- **Target Audience**: Who is this for?
+
+## 2. User Flows
+
+_(Describe the high-level flow step-by-step)_
+
+1. User logs in...
+2. User sees dashboard...
+
+## 3. Functional Requirements
+
+| ID    | Priority | Requirement Description | Acceptance Criteria |
+| :---- | :------- | :---------------------- | :------------------ |
+| FR-01 | P0       | System must allow...    | ...                 |
+| FR-02 | P1       | ...                     | ...                 |
+
+## 4. Non-Functional Requirements
+
+- **Performance**: Load time < 200ms
+- **Scalability**: Support 10k concurrent users
+- **Security**: Compliance with GDPR
+
+## 5. UI/UX Requirements
+
+- **Mobile**: Responsive layout required?
+- **Theme**: Dark mode support?
+  _(Link to Figma/Wireframes if available)_
+
+## 6. Roadmap / Phases
+
+- **Phase 1 (MVP)**: Core features only.
+- **Phase 2**: Nice-to-haves.

package/.agent/skills/business-analysis/templates/use-case.md

@@ -0,0 +1,40 @@
+# Use Case Specification
+
+## UC-[ID]: [Use Case Name]
+
+- **Actor(s)**: [Primary Actor], [Secondary Actor]
+- **Description**: Brief summary of the interaction.
+- **Trigger**: What starts this use case?
+- **Preconditions**: What must be true before this starts? (e.g., User is logged in).
+- **Postconditions**: What is the state of the system after success?
+- **Priority**: High/Medium/Low
+
+## Main Flow (Happy Path)
+
+| Step | Actor Action             | System Response                    |
+| :--- | :----------------------- | :--------------------------------- |
+| 1    | Navigate to "My Profile" | Displays profile form              |
+| 2    | Updates phone number     | Validates format                   |
+| 3    | Clicks "Save"            | Saves data and shows success toast |
+
+## Alternative Flows
+
+### A1. Invalid Input
+
+- **At Step 2**: User enters invalid phone format.
+- **System**: Displays "Invalid format" error below field.
+- **Return**: To Step 2.
+
+### A2. Network Error
+
+- **At Step 3**: API call fails.
+- **System**: Displays "Connection failed, retry?" modal.
+
+## Exceptions (Error Conditions)
+
+- **E1**: Database is locked.
+- **E2**: Session expires during action.
+
+## Business Rules associated
+
+- **BR-05**: Phone number must be unique.

package/.agent/skills/business-analysis/templates/user-story-detailed.md

@@ -0,0 +1,36 @@
+# User Story Template (Agile/Scrum)
+
+## Core Story
+
+**Title**: [User Role] - [Feature Key Name]
+
+> **As a** [Role]
+> **I want** [Feature/Action]
+> **So that** [Benefit/Value]
+
+## Acceptance Criteria (Gherkin)
+
+```gherkin
+Scenario: [Happy Path Title]
+Given [Precondition]
+When [Action]
+Then [Expected Result]
+
+Scenario: [Negative Path Title]
+Given [Precondition]
+When [Action on Edge Case]
+Then [Error Message/Fallback state]
+```
+
+## Developer Notes
+
+- **API Dependency**: [Link to API Endpoint if known]
+- **UI Component**: [Component Name/Design Link]
+- **State Impact**: [Which Redux/Context slice is affected]
+
+## Definition of Done (DoD)
+
+- [ ] Component implemented
+- [ ] Unit tests passed
+- [ ] Visual regression tested
+- [ ] Accessibility (ARIA) checked