@ruaruababa/vibe-kit 1.0.0

package/skills/competitive-landscape/resources/implementation-playbook.md

@@ -0,0 +1,494 @@
+# Competitive Landscape Analysis Implementation Playbook
+
+This file contains detailed patterns, checklists, and code samples referenced by the skill.
+
+# Competitive Landscape Analysis
+
+Comprehensive frameworks for analyzing competition, identifying differentiation opportunities, and developing winning market positioning strategies.
+
+## Use this skill when
+
+- Working on competitive landscape analysis tasks or workflows
+- Needing guidance, best practices, or checklists for competitive landscape analysis
+
+## Do not use this skill when
+
+- The task is unrelated to competitive landscape 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`.
+
+## Overview
+
+Understand competitive dynamics using proven frameworks (Porter's Five Forces, Blue Ocean Strategy, positioning maps) to identify opportunities and craft defensible competitive advantages.
+
+## Porter's Five Forces
+
+Analyze industry attractiveness and competitive intensity.
+
+### Force 1: Threat of New Entrants
+
+**Barriers to Entry:**
+- Capital requirements
+- Economies of scale
+- Switching costs
+- Brand loyalty
+- Regulatory barriers
+- Access to distribution
+- Network effects
+
+**High Threat:** Low barriers, easy to enter (e.g., simple SaaS tools)
+**Low Threat:** High barriers (e.g., regulated industries, hardware)
+
+**Analysis Questions:**
+- How easy is it for new competitors to enter?
+- What would it cost to launch a competing product?
+- Are there network effects or switching costs protecting incumbents?
+
+### Force 2: Bargaining Power of Suppliers
+
+**Supplier Power Factors:**
+- Supplier concentration
+- Availability of substitutes
+- Importance to supplier
+- Switching costs
+- Forward integration threat
+
+**High Power:** Few suppliers, critical inputs (e.g., cloud infrastructure providers)
+**Low Power:** Many alternatives, commoditized (e.g., generic services)
+
+**Analysis Questions:**
+- Who are our critical suppliers?
+- Could they raise prices or reduce quality?
+- Can we switch suppliers easily?
+
+### Force 3: Bargaining Power of Buyers
+
+**Buyer Power Factors:**
+- Buyer concentration
+- Volume purchased
+- Product differentiation
+- Price sensitivity
+- Backward integration threat
+
+**High Power:** Few large customers, standardized products (e.g., enterprise deals)
+**Low Power:** Many small customers, differentiated product (e.g., consumer subscriptions)
+
+**Analysis Questions:**
+- Can customers easily switch to competitors?
+- Do few customers generate most revenue?
+- How price-sensitive are buyers?
+
+### Force 4: Threat of Substitutes
+
+**Substitute Considerations:**
+- Alternative solutions
+- Price-performance tradeoff
+- Switching costs
+- Buyer propensity to substitute
+
+**High Threat:** Many alternatives, low switching cost (e.g., productivity software)
+**Low Threat:** Unique solution, high switching cost (e.g., ERP systems)
+
+**Analysis Questions:**
+- What alternative ways can customers solve this problem?
+- How do substitutes compare on price and performance?
+- What's the cost to switch to a substitute?
+
+### Force 5: Competitive Rivalry
+
+**Rivalry Intensity Factors:**
+- Number of competitors
+- Industry growth rate
+- Product differentiation
+- Exit barriers
+- Strategic stakes
+
+**High Rivalry:** Many competitors, slow growth, commoditized (e.g., email marketing)
+**Low Rivalry:** Few competitors, fast growth, differentiated (e.g., emerging AI tools)
+
+**Analysis Questions:**
+- How many direct competitors exist?
+- Is the market growing or stagnant?
+- How differentiated are offerings?
+- Are competitors competing on price or value?
+
+### Forces Analysis Summary
+
+Create a scorecard:
+
+| Force | Intensity (1-5) | Impact | Key Factors |
+|-------|-----------------|--------|-------------|
+| New Entrants | 3 | Medium | Low barriers but network effects |
+| Supplier Power | 2 | Low | Many cloud providers |
+| Buyer Power | 4 | High | Enterprise customers concentrated |
+| Substitutes | 3 | Medium | Manual processes alternative |
+| Rivalry | 4 | High | 10+ direct competitors |
+
+**Overall Assessment:** Moderate industry attractiveness with high rivalry and buyer power
+
+## Blue Ocean Strategy
+
+Identify uncontested market space through value innovation.
+
+### Four Actions Framework
+
+**Eliminate:**
+What factors can be eliminated that the industry takes for granted?
+
+**Reduce:**
+What factors can be reduced well below industry standard?
+
+**Raise:**
+What factors can be raised well above industry standard?
+
+**Create:**
+What factors can be created that the industry never offered?
+
+### Strategy Canvas
+
+Map your offering vs. competitors on key factors.
+
+**Example: Budget Hotels**
+
+```
+High |                    ★ Traditional Hotels
+     |          ★ Budget Hotels (new)
+     |
+Low  |___________________________________
+     Price  Luxury  Convenience  Cleanliness
+
+Budget Hotel Strategy:
+- Eliminate: Luxury amenities, room service
+- Reduce: Lobby size, staff
+- Raise: Cleanliness, online booking
+- Create: Self-service kiosks, mobile app
+```
+
+### Value Innovation
+
+Find the sweet spot: Lower cost + higher value
+
+**Steps:**
+1. Map industry competing factors
+2. Identify factors to eliminate/reduce (cost savings)
+3. Identify factors to raise/create (differentiation)
+4. Validate that combination creates new market space
+
+## Competitive Positioning
+
+### Positioning Map
+
+Plot competitors on 2-3 key dimensions.
+
+**Example Dimensions:**
+- Price vs. Features
+- Complexity vs. Ease of Use
+- Enterprise vs. SMB Focus
+- Self-Service vs. High-Touch
+- Generalist vs. Specialist
+
+**How to Create:**
+1. Choose 2 dimensions most important to customers
+2. Plot all competitors
+3. Identify gaps (white space)
+4. Validate gap represents real customer need
+
+**Example:**
+```
+High Price
+    |
+    |  ★ Enterprise A      ★ Enterprise B
+    |
+    |          ● Our Position (gap)
+    |
+    |  ★ Competitor C      ★ Competitor D
+    |
+Low Price |____________________________________________
+        Simple                           Complex
+```
+
+### Differentiation Strategy
+
+**How to Differentiate:**
+
+1. **Product Differentiation**
+   - Unique features
+   - Superior performance
+   - Better design/UX
+   - Integration ecosystem
+
+2. **Service Differentiation**
+   - Customer support quality
+   - Onboarding experience
+   - Response time
+   - Success programs
+
+3. **Brand Differentiation**
+   - Trust and reputation
+   - Thought leadership
+   - Community
+   - Values alignment
+
+4. **Price Differentiation**
+   - Premium positioning
+   - Value positioning
+   - Transparent pricing
+   - Flexible packaging
+
+### Positioning Statement Framework
+
+```
+For [target customer]
+Who [statement of need or opportunity]
+Our product is [product category]
+That [statement of key benefit]
+Unlike [primary competitive alternative]
+Our product [statement of primary differentiation]
+```
+
+**Example:**
+```
+For e-commerce companies
+Who struggle with email marketing automation
+Our product is an AI-powered email platform
+That increases conversion rates by 40%
+Unlike Klaviyo and Mailchimp
+Our product uses AI to personalize at scale
+```
+
+## Competitive Intelligence
+
+### Information Gathering
+
+**Public Sources:**
+- Company websites and blogs
+- Press releases and news
+- Job postings (hint at strategy)
+- Customer reviews (G2, Capterra)
+- Social media and forums
+- Glassdoor (employee insights)
+- SEC filings (public companies)
+- Patent filings
+
+**Direct Research:**
+- Customer interviews
+- Win/loss analysis
+- Sales team feedback
+- Product demos and trials
+- Conference attendance
+
+### Competitor Profile Template
+
+For each key competitor, document:
+
+**Company Overview:**
+- Founded, HQ, funding, size
+- Leadership team
+- Company stage and trajectory
+
+**Product:**
+- Core features
+- Target customers
+- Pricing and packaging
+- Technology stack
+- Recent launches
+
+**Go-to-Market:**
+- Sales model (self-serve, sales-led)
+- Marketing strategy
+- Distribution channels
+- Partnerships
+
+**Strengths:**
+- What they do better than anyone
+- Key competitive advantages
+- Market position
+
+**Weaknesses:**
+- Gaps in product
+- Customer complaints
+- Operational challenges
+
+**Strategy:**
+- Stated direction
+- Inferred priorities
+- Likely next moves
+
+## Competitive Pricing Analysis
+
+### Price Positioning
+
+**Premium (Top 25%):**
+- Superior product/service
+- Strong brand
+- High-touch sales
+- Enterprise focus
+
+**Mid-Market (Middle 50%):**
+- Balanced value
+- Standard features
+- Mixed sales model
+- Broad market
+
+**Value (Bottom 25%):**
+- Basic functionality
+- Self-service
+- Cost leadership
+- High volume, low margin
+
+### Pricing Comparison Matrix
+
+| Competitor | Entry Price | Mid Tier | Enterprise | Model |
+|-----------|-------------|----------|------------|-------|
+| Competitor A | $29/mo | $99/mo | Custom | Subscription |
+| Competitor B | $49/mo | $199/mo | $499/mo | Subscription |
+| Us | $39/mo | $129/mo | Custom | Subscription |
+
+**Analysis:**
+- Are we priced competitively?
+- What does our pricing signal?
+- Are there gaps in our packaging?
+
+## Go-to-Market Strategy
+
+### Market Entry Strategies
+
+**Direct Competition:**
+- Head-to-head against established players
+- Requires differentiation and resources
+- Example: Better features at lower price
+
+**Niche Focus:**
+- Target underserved segment
+- Become specialist vs. generalist
+- Example: "Salesforce for real estate"
+
+**Disruptive Innovation:**
+- Target non-consumers or low end
+- Improve over time to move upmarket
+- Example: Freemium model disrupting enterprise
+
+**Platform Play:**
+- Build ecosystem and network effects
+- Aggregate complementary services
+- Example: Marketplace or API platform
+
+### Beachhead Market
+
+**Characteristics of Good Beachhead:**
+- Specific, reachable segment
+- Acute pain you solve well
+- Limited competition
+- Willing to pay
+- Can lead to expansion
+
+**Example:**
+Instead of "project management software", target "project management for construction teams"
+
+## Competitive Advantage
+
+### Sustainable Advantages
+
+**Network Effects:**
+- Value increases with users
+- Example: Slack, marketplaces
+
+**Switching Costs:**
+- High cost to change
+- Example: CRM systems with data
+
+**Economies of Scale:**
+- Unit costs decrease with volume
+- Example: Cloud infrastructure
+
+**Brand:**
+- Trust and reputation
+- Example: Security software
+
+**Proprietary Technology:**
+- Patents or trade secrets
+- Example: Algorithms, data
+
+**Regulatory:**
+- Licenses or approvals
+- Example: Fintech, healthcare
+
+### Testing Your Advantage
+
+Ask:
+- Can competitors copy this in < 2 years?
+- Does this matter to customers?
+- Do we execute this better than anyone?
+- Is this advantage durable?
+
+If "no" to any, it's not a sustainable advantage.
+
+## Competitive Monitoring
+
+### What to Track
+
+**Product Changes:**
+- New features
+- Pricing changes
+- Packaging adjustments
+
+**Market Signals:**
+- Funding announcements
+- Key hires (especially leadership)
+- Customer wins/losses
+- Partnerships
+
+**Performance Metrics:**
+- Revenue (if public or disclosed)
+- Customer count
+- Growth rate
+- Market share estimates
+
+### Monitoring Cadence
+
+**Weekly:**
+- Product release notes
+- News mentions
+
+**Monthly:**
+- Win/loss analysis review
+- Positioning map updates
+
+**Quarterly:**
+- Deep competitive review
+- Strategy adjustment
+
+**Annually:**
+- Major strategy reassessment
+- Market trends analysis
+
+## Additional Resources
+
+### Reference Files
+- **`references/frameworks-deep-dive.md`** - Detailed application of each framework with worksheets
+- **`references/intel-sources.md`** - Comprehensive list of competitive intelligence sources
+
+### Example Files
+- **`examples/competitor-analysis.md`** - Complete competitive analysis for a SaaS startup
+- **`examples/positioning-workshop.md`** - Step-by-step positioning development process
+
+## Quick Start
+
+To analyze competitive landscape:
+
+1. **Identify competitors** - Direct, indirect, and future threats
+2. **Apply Porter's Five Forces** - Assess industry attractiveness
+3. **Create positioning map** - Visualize competitive space
+4. **Profile top 3-5 competitors** - Deep dive on key rivals
+5. **Identify differentiation** - What makes you unique
+6. **Analyze pricing** - Where do you fit?
+7. **Assess advantages** - What's defensible?
+8. **Develop strategy** - How to win
+
+For detailed frameworks and examples, see `references/` and `examples/`.

package/skills/comprehensive-review-full-review/SKILL.md

@@ -0,0 +1,146 @@
+---
+name: comprehensive-review-full-review
+description: "Use when working with comprehensive review full review"
+---
+
+## Use this skill when
+
+- Working on comprehensive review full review tasks or workflows
+- Needing guidance, best practices, or checklists for comprehensive review full review
+
+## Do not use this skill when
+
+- The task is unrelated to comprehensive review full review
+- 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`.
+
+Orchestrate comprehensive multi-dimensional code review using specialized review agents
+
+[Extended thinking: This workflow performs an exhaustive code review by orchestrating multiple specialized agents in sequential phases. Each phase builds upon previous findings to create a comprehensive review that covers code quality, security, performance, testing, documentation, and best practices. The workflow integrates modern AI-assisted review tools, static analysis, security scanning, and automated quality metrics. Results are consolidated into actionable feedback with clear prioritization and remediation guidance. The phased approach ensures thorough coverage while maintaining efficiency through parallel agent execution where appropriate.]
+
+## Review Configuration Options
+
+- **--security-focus**: Prioritize security vulnerabilities and OWASP compliance
+- **--performance-critical**: Emphasize performance bottlenecks and scalability issues
+- **--tdd-review**: Include TDD compliance and test-first verification
+- **--ai-assisted**: Enable AI-powered review tools (Copilot, Codium, Bito)
+- **--strict-mode**: Fail review on any critical issues found
+- **--metrics-report**: Generate detailed quality metrics dashboard
+- **--framework [name]**: Apply framework-specific best practices (React, Spring, Django, etc.)
+
+## Phase 1: Code Quality & Architecture Review
+
+Use Task tool to orchestrate quality and architecture agents in parallel:
+
+### 1A. Code Quality Analysis
+- Use Task tool with subagent_type="code-reviewer"
+- Prompt: "Perform comprehensive code quality review for: $ARGUMENTS. Analyze code complexity, maintainability index, technical debt, code duplication, naming conventions, and adherence to Clean Code principles. Integrate with SonarQube, CodeQL, and Semgrep for static analysis. Check for code smells, anti-patterns, and violations of SOLID principles. Generate cyclomatic complexity metrics and identify refactoring opportunities."
+- Expected output: Quality metrics, code smell inventory, refactoring recommendations
+- Context: Initial codebase analysis, no dependencies on other phases
+
+### 1B. Architecture & Design Review
+- Use Task tool with subagent_type="architect-review"
+- Prompt: "Review architectural design patterns and structural integrity in: $ARGUMENTS. Evaluate microservices boundaries, API design, database schema, dependency management, and adherence to Domain-Driven Design principles. Check for circular dependencies, inappropriate coupling, missing abstractions, and architectural drift. Verify compliance with enterprise architecture standards and cloud-native patterns."
+- Expected output: Architecture assessment, design pattern analysis, structural recommendations
+- Context: Runs parallel with code quality analysis
+
+## Phase 2: Security & Performance Review
+
+Use Task tool with security and performance agents, incorporating Phase 1 findings:
+
+### 2A. Security Vulnerability Assessment
+- Use Task tool with subagent_type="security-auditor"
+- Prompt: "Execute comprehensive security audit on: $ARGUMENTS. Perform OWASP Top 10 analysis, dependency vulnerability scanning with Snyk/Trivy, secrets detection with GitLeaks, input validation review, authentication/authorization assessment, and cryptographic implementation review. Include findings from Phase 1 architecture review: {phase1_architecture_context}. Check for SQL injection, XSS, CSRF, insecure deserialization, and configuration security issues."
+- Expected output: Vulnerability report, CVE list, security risk matrix, remediation steps
+- Context: Incorporates architectural vulnerabilities identified in Phase 1B
+
+### 2B. Performance & Scalability Analysis
+- Use Task tool with subagent_type="application-performance::performance-engineer"
+- Prompt: "Conduct performance analysis and scalability assessment for: $ARGUMENTS. Profile code for CPU/memory hotspots, analyze database query performance, review caching strategies, identify N+1 problems, assess connection pooling, and evaluate asynchronous processing patterns. Consider architectural findings from Phase 1: {phase1_architecture_context}. Check for memory leaks, resource contention, and bottlenecks under load."
+- Expected output: Performance metrics, bottleneck analysis, optimization recommendations
+- Context: Uses architecture insights to identify systemic performance issues
+
+## Phase 3: Testing & Documentation Review
+
+Use Task tool for test and documentation quality assessment:
+
+### 3A. Test Coverage & Quality Analysis
+- Use Task tool with subagent_type="unit-testing::test-automator"
+- Prompt: "Evaluate testing strategy and implementation for: $ARGUMENTS. Analyze unit test coverage, integration test completeness, end-to-end test scenarios, test pyramid adherence, and test maintainability. Review test quality metrics including assertion density, test isolation, mock usage, and flakiness. Consider security and performance test requirements from Phase 2: {phase2_security_context}, {phase2_performance_context}. Verify TDD practices if --tdd-review flag is set."
+- Expected output: Coverage report, test quality metrics, testing gap analysis
+- Context: Incorporates security and performance testing requirements from Phase 2
+
+### 3B. Documentation & API Specification Review
+- Use Task tool with subagent_type="code-documentation::docs-architect"
+- Prompt: "Review documentation completeness and quality for: $ARGUMENTS. Assess inline code documentation, API documentation (OpenAPI/Swagger), architecture decision records (ADRs), README completeness, deployment guides, and runbooks. Verify documentation reflects actual implementation based on all previous phase findings: {phase1_context}, {phase2_context}. Check for outdated documentation, missing examples, and unclear explanations."
+- Expected output: Documentation coverage report, inconsistency list, improvement recommendations
+- Context: Cross-references all previous findings to ensure documentation accuracy
+
+## Phase 4: Best Practices & Standards Compliance
+
+Use Task tool to verify framework-specific and industry best practices:
+
+### 4A. Framework & Language Best Practices
+- Use Task tool with subagent_type="framework-migration::legacy-modernizer"
+- Prompt: "Verify adherence to framework and language best practices for: $ARGUMENTS. Check modern JavaScript/TypeScript patterns, React hooks best practices, Python PEP compliance, Java enterprise patterns, Go idiomatic code, or framework-specific conventions (based on --framework flag). Review package management, build configuration, environment handling, and deployment practices. Include all quality issues from previous phases: {all_previous_contexts}."
+- Expected output: Best practices compliance report, modernization recommendations
+- Context: Synthesizes all previous findings for framework-specific guidance
+
+### 4B. CI/CD & DevOps Practices Review
+- Use Task tool with subagent_type="cicd-automation::deployment-engineer"
+- Prompt: "Review CI/CD pipeline and DevOps practices for: $ARGUMENTS. Evaluate build automation, test automation integration, deployment strategies (blue-green, canary), infrastructure as code, monitoring/observability setup, and incident response procedures. Assess pipeline security, artifact management, and rollback capabilities. Consider all issues identified in previous phases that impact deployment: {all_critical_issues}."
+- Expected output: Pipeline assessment, DevOps maturity evaluation, automation recommendations
+- Context: Focuses on operationalizing fixes for all identified issues
+
+## Consolidated Report Generation
+
+Compile all phase outputs into comprehensive review report:
+
+### Critical Issues (P0 - Must Fix Immediately)
+- Security vulnerabilities with CVSS > 7.0
+- Data loss or corruption risks
+- Authentication/authorization bypasses
+- Production stability threats
+- Compliance violations (GDPR, PCI DSS, SOC2)
+
+### High Priority (P1 - Fix Before Next Release)
+- Performance bottlenecks impacting user experience
+- Missing critical test coverage
+- Architectural anti-patterns causing technical debt
+- Outdated dependencies with known vulnerabilities
+- Code quality issues affecting maintainability
+
+### Medium Priority (P2 - Plan for Next Sprint)
+- Non-critical performance optimizations
+- Documentation gaps and inconsistencies
+- Code refactoring opportunities
+- Test quality improvements
+- DevOps automation enhancements
+
+### Low Priority (P3 - Track in Backlog)
+- Style guide violations
+- Minor code smell issues
+- Nice-to-have documentation updates
+- Cosmetic improvements
+
+## Success Criteria
+
+Review is considered successful when:
+- All critical security vulnerabilities are identified and documented
+- Performance bottlenecks are profiled with remediation paths
+- Test coverage gaps are mapped with priority recommendations
+- Architecture risks are assessed with mitigation strategies
+- Documentation reflects actual implementation state
+- Framework best practices compliance is verified
+- CI/CD pipeline supports safe deployment of reviewed code
+- Clear, actionable feedback is provided for all findings
+- Metrics dashboard shows improvement trends
+- Team has clear prioritized action plan for remediation
+
+Target: $ARGUMENTS

package/skills/comprehensive-review-pr-enhance/SKILL.md

@@ -0,0 +1,46 @@
+---
+name: comprehensive-review-pr-enhance
+description: "You are a PR optimization expert specializing in creating high-quality pull requests that facilitate efficient code reviews. Generate comprehensive PR descriptions, automate review processes, and ensure PRs follow best practices for clarity, size, and reviewability."
+---
+
+# Pull Request Enhancement
+
+You are a PR optimization expert specializing in creating high-quality pull requests that facilitate efficient code reviews. Generate comprehensive PR descriptions, automate review processes, and ensure PRs follow best practices for clarity, size, and reviewability.
+
+## Use this skill when
+
+- Writing or improving PR descriptions
+- Summarizing changes for faster reviews
+- Organizing tests, risks, and rollout notes
+- Reducing PR size or improving reviewability
+
+## Do not use this skill when
+
+- There is no PR or change list to summarize
+- You need a full code review instead of PR polishing
+- The task is unrelated to software delivery
+
+## Context
+The user needs to create or improve pull requests with detailed descriptions, proper documentation, test coverage analysis, and review facilitation. Focus on making PRs that are easy to review, well-documented, and include all necessary context.
+
+## Requirements
+$ARGUMENTS
+
+## Instructions
+
+- Analyze the diff and identify intent and scope.
+- Summarize changes, tests, and risks clearly.
+- Highlight breaking changes and rollout notes.
+- Add checklists and reviewer guidance.
+- If detailed templates are required, open `resources/implementation-playbook.md`.
+
+## Output Format
+
+- PR summary and scope
+- What changed and why
+- Tests performed and results
+- Risks, rollbacks, and reviewer notes
+
+## Resources
+
+- `resources/implementation-playbook.md` for detailed templates and examples.