@riligar/agents-kit 1.4.0 → 1.5.1

package/.agent/skills/riligar-business-startup-financial/SKILL.md

@@ -0,0 +1,392 @@
+---
+name: riligar-business-startup-financial
+description: Create detailed 3-5 year financial model with revenue, costs, cash
+    flow, and scenarios
+allowed-tools: Read Write Edit Glob Grep Bash WebSearch WebFetch
+---
+
+# Financial Projections
+
+Create a comprehensive 3-5 year financial model with revenue projections, cost structure, headcount planning, cash flow analysis, and three-scenario modeling (conservative, base, optimistic) for startup financial planning and fundraising.
+
+## Use this skill when
+
+- Working on financial projections tasks or workflows
+- Needing guidance, best practices, or checklists for financial projections
+
+## Do not use this skill when
+
+- The task is unrelated to financial projections
+- You need a different domain or tool outside this scope
+
+## Instructions
+
+- Clarify goals, constraints, and required inputs.
+- Apply relevant best practices and validate outcomes.
+- Provide actionable steps and verification.
+- If detailed examples are required, open `resources/implementation-playbook.md`.
+
+## What This Command Does
+
+This command builds a complete financial model including:
+
+1. Cohort-based revenue projections
+2. Detailed cost structure (COGS, S&M, R&D, G&A)
+3. Headcount planning by role
+4. Monthly cash flow analysis
+5. Key metrics (CAC, LTV, burn rate, runway)
+6. Three-scenario analysis
+
+## Instructions for Claude
+
+When this command is invoked, follow these steps:
+
+### Step 1: Gather Model Inputs
+
+Ask the user for essential information:
+
+**Business Model:**
+
+- Revenue model (SaaS, marketplace, transaction, etc.)
+- Pricing structure (tiers, average price)
+- Target customer segments
+
+**Starting Point:**
+
+- Current MRR/ARR (if any)
+- Current customer count
+- Current team size
+- Current cash balance
+
+**Growth Assumptions:**
+
+- Expected monthly customer acquisition
+- Customer retention/churn rate
+- Average contract value (ACV)
+- Sales cycle length
+
+**Cost Assumptions:**
+
+- Gross margin or COGS %
+- S&M budget or CAC target
+- Current burn rate (if applicable)
+
+**Funding:**
+
+- Planned fundraising (amount, timing)
+- Pre/post-money valuation
+
+### Step 2: Activate startup-financial-modeling Skill
+
+The startup-financial-modeling skill provides frameworks. Reference it for:
+
+- Revenue modeling approaches
+- Cost structure templates
+- Headcount planning guidance
+- Scenario analysis methods
+
+### Step 3: Build Revenue Model
+
+**Use Cohort-Based Approach:**
+
+For each month, track:
+
+1. New customers acquired
+2. Existing customers retained (apply churn)
+3. Revenue per cohort (customers × ARPU)
+4. Expansion revenue (upsells)
+
+**Formula:**
+
+```
+MRR (Month N) = Σ across all cohorts:
+  (Cohort Size × Retention Rate × ARPU) + Expansion
+```
+
+**Project:**
+
+- Monthly detail for Year 1-2
+- Quarterly detail for Year 3
+- Annual for Years 4-5
+
+### Step 4: Model Cost Structure
+
+Break down operating expenses:
+
+**1. Cost of Goods Sold (COGS)**
+
+- Hosting/infrastructure (% of revenue or fixed)
+- Payment processing (% of revenue)
+- Variable customer support
+- Third-party services
+
+Target gross margin:
+
+- SaaS: 75-85%
+- Marketplace: 60-70%
+- E-commerce: 40-60%
+
+**2. Sales & Marketing (S&M)**
+
+- Sales team compensation
+- Marketing programs
+- Tools and software
+- Target: 40-60% of revenue (early stage)
+
+**3. Research & Development (R&D)**
+
+- Engineering team
+- Product management
+- Design
+- Target: 30-40% of revenue
+
+**4. General & Administrative (G&A)**
+
+- Executive team
+- Finance, legal, HR
+- Office and facilities
+- Target: 15-25% of revenue
+
+### Step 5: Plan Headcount
+
+Create role-by-role hiring plan:
+
+**Reference team-composition-analysis skill for:**
+
+- Roles by stage
+- Compensation benchmarks
+- Hiring velocity assumptions
+
+**For each role:**
+
+- Title and department
+- Start date (month/quarter)
+- Base salary
+- Fully-loaded cost (salary × 1.3-1.4)
+- Equity grant
+
+**Track departmental ratios:**
+
+- Engineering: 40-50% of team
+- Sales & Marketing: 25-35%
+- G&A: 10-15%
+- Product/CS: 10-15%
+
+### Step 6: Calculate Cash Flow
+
+Monthly cash flow projection:
+
+```
+Beginning Cash Balance
++ Cash Collected (revenue, consider payment terms)
+- Operating Expenses
+- CapEx
+= Ending Cash Balance
+
+Monthly Burn = Revenue - Expenses (if negative)
+Runway = Cash Balance / Monthly Burn Rate
+```
+
+**Include Funding Events:**
+
+- Timing of raises
+- Amount raised
+- Use of proceeds
+- Impact on cash balance
+
+### Step 7: Compute Key Metrics
+
+Calculate monthly/quarterly:
+
+**Unit Economics:**
+
+- CAC (S&M spend / new customers)
+- LTV (ARPU × margin% / churn rate)
+- LTV:CAC ratio (target > 3.0)
+- CAC payback period (target < 18 months)
+
+**Efficiency Metrics:**
+
+- Burn multiple (net burn / net new ARR) - target < 2.0
+- Magic number (net new ARR / S&M spend) - target > 0.5
+- Rule of 40 (growth% + margin%) - target > 40%
+
+**Cash Metrics:**
+
+- Monthly burn rate
+- Runway in months
+- Cash efficiency
+
+### Step 8: Create Three Scenarios
+
+Build conservative, base, and optimistic projections:
+
+**Conservative (P10):**
+
+- New customers: -30% vs. base
+- Churn: +20% vs. base
+- Pricing: -15% vs. base
+- CAC: +25% vs. base
+
+**Base (P50):**
+
+- Most likely assumptions
+- Primary planning scenario
+
+**Optimistic (P90):**
+
+- New customers: +30% vs. base
+- Churn: -20% vs. base
+- Pricing: +15% vs. base
+- CAC: -25% vs. base
+
+### Step 9: Generate Financial Model Report
+
+Create comprehensive markdown report with tables:
+
+**Section 1: Executive Summary**
+
+- 3-5 year financial snapshot
+- Key metrics at scale
+- Funding requirements
+
+**Section 2: Model Assumptions**
+
+- Revenue model and pricing
+- Growth assumptions
+- Cost structure assumptions
+- Headcount plan summary
+
+**Section 3: Revenue Projections**
+Monthly/quarterly tables showing:
+
+```
+| Month | New Customers | Total Customers | MRR | ARR | Growth % |
+|-------|---------------|-----------------|-----|-----|----------|
+```
+
+**Section 4: Cost Breakdown**
+
+```
+| Department | Year 1 | Year 2 | Year 3 | % Revenue |
+|------------|--------|--------|--------|-----------|
+| COGS       | $X     | $Y     | $Z     | XX%       |
+| S&M        | $X     | $Y     | $Z     | XX%       |
+| R&D        | $X     | $Y     | $Z     | XX%       |
+| G&A        | $X     | $Y     | $Z     | XX%       |
+```
+
+**Section 5: Headcount Plan**
+
+```
+| Department | Current | Year 1 | Year 2 | Year 3 |
+|------------|---------|--------|--------|--------|
+| Engineering| X       | Y      | Z      | W      |
+```
+
+**Section 6: Cash Flow Analysis**
+
+```
+| Quarter | Revenue | Expenses | Net Burn | Cash Balance | Runway |
+|---------|---------|----------|----------|--------------|--------|
+```
+
+**Section 7: Key Metrics**
+
+```
+| Metric | Year 1 | Year 2 | Year 3 | Target |
+|--------|--------|--------|--------|--------|
+| CAC | $X | $Y | $Z | <$A |
+| LTV | $X | $Y | $Z | >$B |
+| Burn Multiple | X | Y | Z | <2.0 |
+```
+
+**Section 8: Scenario Analysis**
+
+```
+| Scenario | Year 3 ARR | Customers | Burn | Runway |
+|----------|------------|-----------|------|--------|
+| Conservative | $Xم | Y | $Z | W mo |
+| Base | $X | Y | $Z | W mo |
+| Optimistic | $X | Y | $Z | W mo |
+```
+
+**Section 9: Funding Requirements**
+
+- Amount needed
+- Use of proceeds breakdown
+- Milestones to achieve
+- Expected valuation impact
+
+**Section 10: Validation**
+
+- Sanity checks performed
+- Benchmark comparisons
+- Risk factors
+- Assumptions to monitor
+
+### Step 10: Save Model
+
+Offer to save as markdown file:
+
+- Suggest filename: `financial-projections-YYYY-MM-DD.md`
+- Include note that user can convert to Excel/Sheets
+- Provide formulas for key calculations
+
+## Financial Model Best Practices
+
+**Do:**
+
+- Use cohort-based revenue model
+- Include 3 scenarios
+- Show monthly detail (Year 1-2)
+- Calculate key metrics
+- Validate against benchmarks
+- Document all assumptions
+- Show cash flow and runway
+- Include fundraising milestones
+
+**Don't:**
+
+- Be overly optimistic on growth
+- Underestimate costs
+- Forget fully-loaded compensation
+- Ignore cash timing
+- Skip scenario analysis
+- Use static headcount
+- Forget to validate
+
+## Integration with Other Commands
+
+Pairs well with:
+
+- `/market-opportunity` - Use SOM for revenue ceiling
+- `/business-case` - Include projections in business case
+
+## Example Usage
+
+```
+User: /financial-projections
+
+Claude: I'll create a comprehensive financial model for your startup. Let me gather the key inputs.
+
+What's your business model?
+→ "B2B SaaS, subscription-based"
+
+Current state?
+→ "$50K MRR, 100 customers, 5-person team, $500K cash"
+
+Growth assumptions?
+→ "Expect 15% MoM growth, 10% monthly churn, $500 ACV"
+
+[Claude builds complete model with all sections]
+```
+
+## Notes
+
+- Model building takes 45-90 minutes
+- Results in comprehensive planning tool
+- Update monthly to track vs. actuals
+- Share with investors and board
+- Use for fundraising decks
+- Basis for budget and hiring decisions

package/.agent/skills/riligar-business-startup-market/SKILL.md

@@ -0,0 +1,266 @@
+---
+name: riligar-business-startup-market
+description: Generate comprehensive market opportunity analysis with TAM/SAM/SOM
+    calculations
+allowed-tools: Read Write Edit Glob Grep Bash WebSearch WebFetch
+---
+
+# Market Opportunity Analysis
+
+Generate a comprehensive market opportunity analysis for a startup, including Total Addressable Market (TAM), Serviceable Available Market (SAM), and Serviceable Obtainable Market (SOM) calculations using both bottom-up and top-down methodologies.
+
+## Use this skill when
+
+- Working on market opportunity analysis tasks or workflows
+- Needing guidance, best practices, or checklists for market opportunity analysis
+
+## Do not use this skill when
+
+- The task is unrelated to market opportunity analysis
+- You need a different domain or tool outside this scope
+
+## Instructions
+
+- Clarify goals, constraints, and required inputs.
+- Apply relevant best practices and validate outcomes.
+- Provide actionable steps and verification.
+- If detailed examples are required, open `resources/implementation-playbook.md`.
+
+## What This Command Does
+
+This command guides through an interactive market sizing process to:
+
+1. Define the target market and customer segments
+2. Gather relevant market data
+3. Calculate TAM using bottom-up methodology
+4. Validate with top-down analysis
+5. Narrow to SAM with appropriate filters
+6. Estimate realistic SOM (3-5 year opportunity)
+7. Present findings in a formatted report
+
+## Instructions for Claude
+
+When this command is invoked, follow these steps:
+
+### Step 1: Gather Context
+
+Ask the user for essential information:
+
+- **Product/Service Description:** What problem is being solved?
+- **Target Customers:** Who is the ideal customer? (industry, size, geography)
+- **Business Model:** How does pricing work? (subscription, transaction, etc.)
+- **Stage:** What stage is the company? (pre-launch, seed, Series A)
+- **Geography:** Initial target market (US, North America, Global)
+
+### Step 2: Activate market-sizing-analysis Skill
+
+The market-sizing-analysis skill provides comprehensive methodologies. Reference it for:
+
+- Bottom-up calculation frameworks
+- Top-down validation approaches
+- Industry-specific templates
+- Data source recommendations
+
+### Step 3: Conduct Bottom-Up Analysis
+
+**For B2B/SaaS:**
+
+1. Define customer segments (company size, industry, use case)
+2. Estimate number of companies in each segment
+3. Determine average contract value (ACV) per segment
+4. Calculate TAM: Σ (Segment Size × ACV)
+
+**For Consumer/Marketplace:**
+
+1. Define target user demographics
+2. Estimate total addressable users
+3. Determine average revenue per user (ARPU)
+4. Calculate TAM: Total Users × ARPU × Frequency
+
+**For Transactions/E-commerce:**
+
+1. Estimate total transaction volume (GMV)
+2. Determine take rate or margin
+3. Calculate TAM: Total GMV × Take Rate
+
+### Step 4: Gather Market Data
+
+Use available tools to research:
+
+- **WebSearch:** Find industry reports, market size estimates, public company data
+- **Cite all sources** with URLs and publication dates
+- **Document assumptions** clearly
+
+Recommended data sources (from skill):
+
+- Government data (Census, BLS)
+- Industry reports (Gartner, Forrester, Statista)
+- Public company filings (10-K reports)
+- Trade associations
+- Academic research
+
+### Step 5: Top-Down Validation
+
+Validate bottom-up calculation:
+
+1. Find total market category size from research
+2. Apply geographic filters
+3. Apply segment/product filters
+4. Compare to bottom-up TAM (should be within 30%)
+
+If variance > 30%, investigate and explain differences.
+
+### Step 6: Calculate SAM
+
+Apply realistic filters to narrow TAM:
+
+- **Geographic:** Regions actually serviceable
+- **Product Capability:** Features needed to serve
+- **Market Readiness:** Customers ready to adopt
+- **Addressable Switching:** Can reach and convert
+
+Formula:
+
+```
+SAM = TAM × Geographic % × Product Fit % × Market Readiness %
+```
+
+### Step 7: Estimate SOM
+
+Calculate realistic obtainable market share:
+
+**Conservative Approach (Recommended):**
+
+- Year 3: 2-3% of SAM
+- Year 5: 4-6% of SAM
+
+**Consider:**
+
+- Competitive intensity
+- Available resources (funding, team)
+- Go-to-market effectiveness
+- Differentiation strength
+
+### Step 8: Create Market Sizing Report
+
+Generate a comprehensive markdown report with:
+
+**Section 1: Executive Summary**
+
+- Market opportunity in one paragraph
+- TAM/SAM/SOM headline numbers
+
+**Section 2: Market Definition**
+
+- Problem being solved
+- Target customer profile
+- Geographic scope
+- Time horizon
+
+**Section 3: Bottom-Up Analysis**
+
+- Customer segment breakdown
+- Segment sizing with sources
+- TAM calculation with formula
+- Assumptions documented
+
+**Section 4: Top-Down Validation**
+
+- Industry category and size
+- Filter application
+- Validated TAM
+- Comparison to bottom-up
+
+**Section 5: SAM Calculation**
+
+- Filters applied with rationale
+- SAM formula and result
+- Segment-level breakdown
+
+**Section 6: SOM Projection**
+
+- Market share assumptions
+- Year 3 and Year 5 estimates
+- Customer count implications
+- Revenue projections
+
+**Section 7: Market Growth**
+
+- Industry growth rate (CAGR)
+- Key growth drivers
+- 5-year market evolution
+
+**Section 8: Validation and Sanity Checks**
+
+- Public company comparisons
+- Customer count validation
+- Competitive context
+
+**Section 9: Investment Thesis**
+
+- Market opportunity assessment
+- Key positives and risks
+- Venture-scale potential
+- Next steps
+
+### Step 9: Save Report
+
+Offer to save the report as a markdown file:
+
+- Suggest filename: `market-opportunity-analysis-YYYY-MM-DD.md`
+- Use Write tool to create file
+- Confirm file location with user
+
+## Tips for Best Results
+
+**Do:**
+
+- Start with bottom-up (most credible)
+- Always triangulate with top-down
+- Cite all data sources
+- Document every assumption
+- Be conservative on SOM
+- Compare to public company benchmarks
+- Explain any data gaps or limitations
+
+**Don't:**
+
+- Rely solely on top-down
+- Cherry-pick optimistic data
+- Claim >10% SOM without strong justification
+- Mix methodologies inappropriately
+- Ignore competitive context
+- Skip validation steps
+
+## Example Usage
+
+```
+User: /market-opportunity
+
+Claude: I'll help you create a comprehensive market opportunity analysis. Let me start by gathering some context.
+
+What product or service are you analyzing?
+→ "AI-powered email marketing for e-commerce companies"
+
+Who are your target customers?
+→ "E-commerce companies with $1M+ annual revenue in North America"
+
+What's your pricing model?
+→ "Subscription: $50-500/month based on email volume, average $300/month"
+
+[Claude proceeds with analysis, gathering data, calculating TAM/SAM/SOM, and generating report]
+```
+
+## Integration with Other Commands
+
+This command pairs well with:
+
+- `/financial-projections` - Use SOM to build revenue model
+- `/business-case` - Include market sizing in business case
+
+## Notes
+
+- Market sizing typically takes 30-60 minutes for thorough analysis
+- Quality depends on data availability - explain limitations
+- Update annually as market evolves
+- Conservative estimates build credibility with investors

package/.agent/skills/riligar-dev-architecture/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: architecture
+name: riligar-dev-architecture
 description: Architectural decision-making framework. Requirements analysis, trade-off evaluation, ADR documentation. Use when making architecture decisions or analyzing system design.
 allowed-tools: Read, Glob, Grep
 ---
@@ -12,22 +12,22 @@ allowed-tools: Read, Glob, Grep
 
 **Read ONLY files relevant to the request!** Check the content map, find what you need.
 
-| File | Description | When to Read |
-|------|-------------|--------------|
-| `context-discovery.md` | Questions to ask, project classification | Starting architecture design |
-| `trade-off-analysis.md` | ADR templates, trade-off framework | Documenting decisions |
-| `pattern-selection.md` | Decision trees, anti-patterns | Choosing patterns |
-| `examples.md` | MVP, SaaS, Enterprise examples | Reference implementations |
-| `patterns-reference.md` | Quick lookup for patterns | Pattern comparison |
+| File                    | Description                              | When to Read                 |
+| ----------------------- | ---------------------------------------- | ---------------------------- |
+| `context-discovery.md`  | Questions to ask, project classification | Starting architecture design |
+| `trade-off-analysis.md` | ADR templates, trade-off framework       | Documenting decisions        |
+| `pattern-selection.md`  | Decision trees, anti-patterns            | Choosing patterns            |
+| `examples.md`           | MVP, SaaS, Enterprise examples           | Reference implementations    |
+| `patterns-reference.md` | Quick lookup for patterns                | Pattern comparison           |
 
 ---
 
 ## 🔗 Related Skills
 
-| Skill | Use For |
-|-------|---------|
-| `@[skills/database-design]` | Database schema design |
-| `@[skills/api-patterns]` | API design patterns |
+| Skill                             | Use For                 |
+| --------------------------------- | ----------------------- |
+| `@[skills/database-design]`       | Database schema design  |
+| `@[skills/api-patterns]`          | API design patterns     |
 | `@[skills/deployment-procedures]` | Deployment architecture |
 
 ---