omgkit 2.9.1 → 2.10.1

package/plugin/workflows/content/marketing.md

@@ -0,0 +1,118 @@
+---
+name: marketing
+description: Create marketing content and materials
+category: content
+complexity: low
+estimated-time: 1-4 hours
+agents:
+  - copywriter
+  - brainstormer
+  - researcher
+skills: []
+commands:
+  - /planning:brainstorm
+  - /planning:research
+prerequisites:
+  - Product/feature defined
+  - Target audience known
+---
+
+# Marketing Content Workflow
+
+## Overview
+
+The Marketing Content workflow helps create compelling marketing materials including landing page copy, product descriptions, and promotional content.
+
+## When to Use
+
+- Launching new products
+- Creating landing pages
+- Writing promotional content
+- Developing messaging
+
+## Steps
+
+### Step 1: Research
+**Agent:** researcher
+**Command:** `/planning:research`
+**Duration:** 30-60 minutes
+
+Research phase:
+- Target audience
+- Competitor analysis
+- Market positioning
+- Key messages
+
+**Output:** Research findings
+
+### Step 2: Ideation
+**Agent:** brainstormer
+**Command:** `/planning:brainstorm`
+**Duration:** 30-60 minutes
+
+Generate ideas:
+- Messaging angles
+- Headlines options
+- Value propositions
+- Call-to-actions
+
+**Output:** Content ideas
+
+### Step 3: Copy Writing
+**Agent:** copywriter
+**Duration:** 1-2 hours
+
+Write copy:
+- Headlines
+- Body copy
+- Features/benefits
+- CTAs
+
+**Output:** Marketing copy
+
+### Step 4: Review
+**Agent:** copywriter
+**Duration:** 30-60 minutes
+
+Review and refine:
+- Tone consistency
+- Clarity
+- Persuasiveness
+- Grammar
+
+**Output:** Refined copy
+
+## Quality Gates
+
+- [ ] Audience researched
+- [ ] Ideas generated
+- [ ] Copy written
+- [ ] Copy reviewed
+
+## Copy Frameworks
+
+```
+Marketing Copy Frameworks
+=========================
+AIDA:
+- Attention: Hook
+- Interest: Benefits
+- Desire: Value
+- Action: CTA
+
+PAS:
+- Problem: Pain point
+- Agitate: Emphasize
+- Solution: Your product
+```
+
+## Example Usage
+
+```bash
+/workflow:marketing "product launch landing page"
+/workflow:marketing "feature announcement email"
+```
+
+## Related Workflows
+
+- `technical-docs` - For documentation

package/plugin/workflows/content/technical-docs.md

@@ -0,0 +1,146 @@
+---
+name: technical-docs
+description: Create comprehensive technical documentation
+category: content
+complexity: medium
+estimated-time: 2-8 hours
+agents:
+  - docs-manager
+  - architect
+  - copywriter
+  - code-reviewer
+skills:
+  - writing-plans
+commands:
+  - /planning:doc
+  - /dev:review
+prerequisites:
+  - Codebase accessible
+  - Documentation scope defined
+---
+
+# Technical Documentation Workflow
+
+## Overview
+
+The Technical Documentation workflow helps create comprehensive, well-structured documentation including API references, architecture guides, and tutorials.
+
+## When to Use
+
+- Documenting new features
+- Creating API references
+- Writing architecture guides
+- Building tutorials
+
+## Steps
+
+### Step 1: Documentation Planning
+**Agent:** docs-manager
+**Duration:** 30-60 minutes
+
+Plan documentation:
+- Define scope
+- Identify audiences
+- Create outline
+- Set standards
+
+**Output:** Documentation plan
+
+### Step 2: API Documentation
+**Agent:** docs-manager
+**Duration:** 1-2 hours
+
+Generate API docs:
+- Extract from code
+- Add descriptions
+- Include examples
+- Document errors
+
+**Output:** API reference
+
+### Step 3: Architecture Guide
+**Agent:** architect
+**Duration:** 1-2 hours
+
+Write architecture:
+- System overview
+- Component diagrams
+- Design decisions
+- Integration points
+
+**Output:** Architecture guide
+
+### Step 4: Tutorials
+**Agent:** docs-manager
+**Duration:** 1-2 hours
+
+Create tutorials:
+- Getting started
+- Step-by-step guides
+- Code examples
+- Common patterns
+
+**Output:** Tutorial content
+
+### Step 5: Review
+**Agent:** code-reviewer
+**Command:** `/dev:review`
+**Duration:** 30-60 minutes
+
+Review documentation:
+- Technical accuracy
+- Completeness
+- Working examples
+- Clarity
+
+**Output:** Review feedback
+
+### Step 6: Publishing
+**Agent:** docs-manager
+**Duration:** 30-60 minutes
+
+Publish docs:
+- Format for platform
+- Add navigation
+- Configure search
+- Deploy
+
+**Output:** Published docs
+
+## Quality Gates
+
+- [ ] Documentation planned
+- [ ] API documented
+- [ ] Architecture explained
+- [ ] Tutorials complete
+- [ ] Review passed
+- [ ] Docs published
+
+## Documentation Structure
+
+```
+Documentation Structure
+=======================
+docs/
+├── getting-started/
+│   ├── installation.md
+│   └── quickstart.md
+├── guides/
+│   ├── architecture.md
+│   └── tutorials/
+├── api/
+│   └── reference.md
+└── changelog.md
+```
+
+## Example Usage
+
+```bash
+/workflow:technical-docs "API documentation for v2"
+/workflow:technical-docs "developer onboarding guide"
+```
+
+## Related Workflows
+
+- `api-design` - For API specs
+- `marketing` - For marketing content

package/plugin/workflows/database/migration.md

@@ -0,0 +1,153 @@
+---
+name: migration
+description: Safe database migrations with rollback
+category: database
+complexity: high
+estimated-time: 1-4 hours
+agents:
+  - database-admin
+  - planner
+  - tester
+skills:
+  - database-migration
+commands:
+  - /planning:plan
+  - /dev:test
+prerequisites:
+  - Schema changes defined
+  - Backup strategy ready
+---
+
+# Database Migration Workflow
+
+## Overview
+
+The Database Migration workflow ensures safe, zero-downtime database migrations with proper rollback capabilities.
+
+## When to Use
+
+- Schema changes required
+- Data transformations
+- Index modifications
+- Constraint updates
+
+## Steps
+
+### Step 1: Migration Planning
+**Agent:** planner
+**Command:** `/planning:plan "migration"`
+**Duration:** 30-60 minutes
+
+Plan migration:
+- Identify changes
+- Assess impact
+- Plan rollback
+- Schedule execution
+
+**Output:** Migration plan
+
+### Step 2: Backup
+**Agent:** database-admin
+**Duration:** 15-30 minutes
+
+Create backup:
+- Full backup
+- Verify backup
+- Document state
+- Test restore
+
+**Output:** Backup completed
+
+### Step 3: Migration Script
+**Agent:** database-admin
+**Duration:** 30-60 minutes
+
+Write migration:
+- Create migration file
+- Write up migration
+- Write down migration
+- Add validation
+
+**Output:** Migration script
+
+### Step 4: Staging Test
+**Agent:** tester
+**Duration:** 30-60 minutes
+
+Test in staging:
+- Run migration
+- Test application
+- Verify data
+- Test rollback
+
+**Output:** Staging verified
+
+### Step 5: Production Migration
+**Agent:** database-admin
+**Duration:** 15-60 minutes
+
+Execute migration:
+- Run migration
+- Monitor progress
+- Verify completion
+- Update status
+
+**Output:** Migration complete
+
+### Step 6: Verification
+**Agent:** tester
+**Command:** `/dev:test`
+**Duration:** 30-60 minutes
+
+Verify migration:
+- Application testing
+- Data integrity
+- Performance check
+- Document completion
+
+**Output:** Verification report
+
+## Quality Gates
+
+- [ ] Migration planned
+- [ ] Backup verified
+- [ ] Rollback tested
+- [ ] Staging validated
+- [ ] Production migrated
+- [ ] Verification passed
+
+## Migration Checklist
+
+```
+Migration Checklist
+===================
+PRE-MIGRATION:
+[ ] Backup created and verified
+[ ] Rollback script ready
+[ ] Stakeholders notified
+[ ] Maintenance window scheduled
+
+MIGRATION:
+[ ] Migration executed
+[ ] Progress monitored
+[ ] Errors handled
+[ ] Completion verified
+
+POST-MIGRATION:
+[ ] Application tested
+[ ] Data verified
+[ ] Performance checked
+[ ] Documentation updated
+```
+
+## Example Usage
+
+```bash
+/workflow:migration "add user preferences table"
+/workflow:migration "split orders table for sharding"
+```
+
+## Related Workflows
+
+- `schema-design` - For initial design
+- `database-optimization` - For performance

package/plugin/workflows/database/optimization.md

@@ -0,0 +1,136 @@
+---
+name: database-optimization
+description: Optimize database performance
+category: database
+complexity: medium
+estimated-time: 2-6 hours
+agents:
+  - database-admin
+  - tester
+skills:
+  - database-optimization
+commands:
+  - /quality:optimize
+  - /dev:test
+prerequisites:
+  - Database accessible
+  - Performance metrics available
+---
+
+# Database Optimization Workflow
+
+## Overview
+
+The Database Optimization workflow systematically improves database performance through query optimization, indexing, and configuration tuning.
+
+## When to Use
+
+- Slow query complaints
+- Performance degradation
+- Scaling preparation
+- Regular maintenance
+
+## Steps
+
+### Step 1: Performance Profiling
+**Agent:** database-admin
+**Duration:** 30-60 minutes
+
+Profile performance:
+- Identify slow queries
+- Analyze query patterns
+- Check resource usage
+- Review current indexes
+
+**Output:** Performance profile
+
+### Step 2: Query Analysis
+**Agent:** database-admin
+**Duration:** 30-60 minutes
+
+Analyze queries:
+- EXPLAIN plans
+- Index usage
+- Full table scans
+- N+1 queries
+
+**Output:** Query analysis
+
+### Step 3: Index Optimization
+**Agent:** database-admin
+**Duration:** 30-60 minutes
+
+Optimize indexes:
+- Add missing indexes
+- Remove unused indexes
+- Composite indexes
+- Covering indexes
+
+**Output:** Index changes
+
+### Step 4: Query Optimization
+**Agent:** database-admin
+**Duration:** 1-2 hours
+
+Optimize queries:
+- Rewrite slow queries
+- Add query hints
+- Batch operations
+- Caching strategies
+
+**Output:** Optimized queries
+
+### Step 5: Configuration Tuning
+**Agent:** database-admin
+**Duration:** 30-60 minutes
+
+Tune configuration:
+- Memory allocation
+- Connection pooling
+- Cache sizes
+- Timeout settings
+
+**Output:** Configuration updates
+
+### Step 6: Verification
+**Agent:** tester
+**Command:** `/dev:test`
+**Duration:** 30-60 minutes
+
+Verify improvements:
+- Re-run benchmarks
+- Compare metrics
+- Validate behavior
+- Document results
+
+**Output:** Optimization report
+
+## Quality Gates
+
+- [ ] Slow queries identified
+- [ ] Query plans analyzed
+- [ ] Indexes optimized
+- [ ] Queries improved
+- [ ] Configuration tuned
+- [ ] Improvements verified
+
+## Optimization Targets
+
+| Metric | Target | Action |
+|--------|--------|--------|
+| Query time | <100ms | Index/rewrite |
+| Connection pool | <80% | Scale up |
+| Cache hit rate | >95% | Increase cache |
+| I/O wait | <10% | Index/query |
+
+## Example Usage
+
+```bash
+/workflow:database-optimization "orders table slow queries"
+/workflow:database-optimization "overall database performance"
+```
+
+## Related Workflows
+
+- `schema-design` - For structural changes
+- `migration` - For schema updates

package/plugin/workflows/database/schema-design.md

@@ -0,0 +1,148 @@
+---
+name: schema-design
+description: Design production-grade database schemas
+category: database
+complexity: medium
+estimated-time: 2-8 hours
+agents:
+  - database-admin
+  - planner
+  - tester
+skills:
+  - database-schema-design
+  - postgresql
+  - mongodb
+commands:
+  - /planning:plan
+  - /dev:feature
+  - /dev:test
+prerequisites:
+  - Data requirements defined
+  - Database type selected
+---
+
+# Schema Design Workflow
+
+## Overview
+
+The Schema Design workflow helps create well-structured, normalized, and performant database schemas with proper indexing and relationships.
+
+## When to Use
+
+- Starting new projects
+- Adding new data models
+- Redesigning data structures
+- Optimizing existing schemas
+
+## Steps
+
+### Step 1: Requirements Gathering
+**Agent:** planner
+**Duration:** 30-60 minutes
+
+Gather requirements:
+- Entity identification
+- Relationship mapping
+- Data volume estimates
+- Access patterns
+
+**Output:** Data requirements
+
+### Step 2: Entity-Relationship Design
+**Agent:** database-admin
+**Duration:** 1-2 hours
+
+Design ER model:
+- Entity definitions
+- Relationships
+- Cardinality
+- Constraints
+
+**Output:** ER diagram
+
+### Step 3: Normalization
+**Agent:** database-admin
+**Duration:** 30-60 minutes
+
+Normalize schema:
+- Apply normal forms
+- Eliminate redundancy
+- Ensure data integrity
+- Balance normalization vs performance
+
+**Output:** Normalized schema
+
+### Step 4: Index Design
+**Agent:** database-admin
+**Duration:** 30-60 minutes
+
+Design indexes:
+- Primary keys
+- Foreign keys
+- Query-based indexes
+- Composite indexes
+
+**Output:** Index strategy
+
+### Step 5: Migration Creation
+**Agent:** database-admin
+**Duration:** 30-60 minutes
+
+Create migrations:
+- Write migration files
+- Include rollback
+- Test migrations
+- Document changes
+
+**Output:** Migration files
+
+### Step 6: Validation
+**Agent:** tester
+**Command:** `/dev:test`
+**Duration:** 30-60 minutes
+
+Validate schema:
+- Test migrations
+- Verify constraints
+- Check relationships
+- Performance baseline
+
+**Output:** Validation report
+
+## Quality Gates
+
+- [ ] Requirements documented
+- [ ] ER diagram complete
+- [ ] Schema normalized
+- [ ] Indexes designed
+- [ ] Migrations created
+- [ ] Validation passed
+
+## Schema Design Principles
+
+```
+Database Schema Principles
+==========================
+1. Single source of truth
+2. Appropriate normalization
+3. Proper data types
+4. Meaningful naming
+5. Consistent conventions
+6. Performance-aware indexing
+7. Referential integrity
+8. Soft delete consideration
+9. Audit trail support
+10. Future extensibility
+```
+
+## Example Usage
+
+```bash
+/workflow:schema-design "e-commerce with users, products, orders"
+/workflow:schema-design "multi-tenant SaaS application"
+```
+
+## Related Workflows
+
+- `migration` - For schema changes
+- `database-optimization` - For performance