omgkit 2.9.0 → 2.10.0

package/plugin/workflows/api/api-design.md

@@ -0,0 +1,152 @@
+---
+name: api-design
+description: Design RESTful or GraphQL APIs
+category: api
+complexity: medium
+estimated-time: 2-6 hours
+agents:
+  - api-designer
+  - planner
+  - docs-manager
+  - code-reviewer
+skills:
+  - api-architecture
+commands:
+  - /planning:plan
+  - /quality:api-gen
+  - /planning:doc
+  - /dev:review
+prerequisites:
+  - API requirements defined
+  - Technology stack selected
+---
+
+# API Design Workflow
+
+## Overview
+
+The API Design workflow guides you through designing well-structured, documented, and consistent APIs following REST or GraphQL best practices.
+
+## When to Use
+
+- Creating new APIs
+- Redesigning existing APIs
+- Adding API endpoints
+- Standardizing API patterns
+
+## Steps
+
+### Step 1: Requirements Analysis
+**Agent:** planner
+**Command:** `/planning:plan "API requirements"`
+**Duration:** 30-60 minutes
+
+Analyze requirements:
+- Identify resources
+- Define operations
+- Specify data models
+- Document constraints
+
+**Output:** API requirements
+
+### Step 2: API Design
+**Agent:** api-designer
+**Duration:** 1-2 hours
+
+Design API:
+- Resource design
+- Endpoint structure
+- Request/response formats
+- Error handling
+
+**Output:** API design document
+
+### Step 3: OpenAPI Specification
+**Agent:** api-designer
+**Command:** `/quality:api-gen`
+**Duration:** 30-60 minutes
+
+Create specification:
+- OpenAPI/Swagger spec
+- Schema definitions
+- Security schemes
+- Example payloads
+
+**Output:** OpenAPI spec
+
+### Step 4: Design Review
+**Agent:** code-reviewer
+**Command:** `/dev:review`
+**Duration:** 30-60 minutes
+
+Review design:
+- Consistency check
+- Best practices
+- Security review
+- Performance considerations
+
+**Output:** Review feedback
+
+### Step 5: Documentation
+**Agent:** docs-manager
+**Command:** `/planning:doc`
+**Duration:** 30-60 minutes
+
+Generate docs:
+- API reference
+- Authentication guide
+- Code examples
+- Rate limits
+
+**Output:** API documentation
+
+### Step 6: Implementation Guidance
+**Agent:** api-designer
+**Duration:** 30-60 minutes
+
+Create guidance:
+- Implementation notes
+- Testing strategy
+- Versioning plan
+- Deprecation policy
+
+**Output:** Implementation guide
+
+## Quality Gates
+
+- [ ] Requirements documented
+- [ ] API designed per standards
+- [ ] OpenAPI spec complete
+- [ ] Design reviewed
+- [ ] Documentation generated
+- [ ] Implementation guide ready
+
+## REST Design Principles
+
+```
+REST API Best Practices
+=======================
+- Use nouns for resources
+- HTTP verbs for actions
+- Consistent naming
+- Proper status codes
+- HATEOAS where applicable
+- Versioning strategy
+- Pagination for lists
+- Filtering and sorting
+- Rate limiting
+- Authentication/Authorization
+```
+
+## Example Usage
+
+```bash
+/workflow:api-design "user management API with CRUD and search"
+/workflow:api-design "payment processing API with webhooks"
+```
+
+## Related Workflows
+
+- `api-testing` - For testing APIs
+- `full-feature` - For implementation
+- `technical-docs` - For documentation

package/plugin/workflows/api/api-testing.md

@@ -0,0 +1,152 @@
+---
+name: api-testing
+description: Comprehensive API testing
+category: api
+complexity: medium
+estimated-time: 2-6 hours
+agents:
+  - tester
+  - security-auditor
+skills:
+  - api-architecture
+  - owasp
+commands:
+  - /dev:test
+  - /quality:security-scan
+prerequisites:
+  - API implemented
+  - Test environment ready
+---
+
+# API Testing Workflow
+
+## Overview
+
+The API Testing workflow ensures comprehensive testing of APIs including functional, security, and performance testing.
+
+## When to Use
+
+- After API implementation
+- Before releases
+- Regression testing
+- Performance validation
+
+## Steps
+
+### Step 1: Test Planning
+**Agent:** tester
+**Duration:** 30-60 minutes
+
+Plan testing:
+- Identify test cases
+- Define coverage
+- Setup test data
+- Configure environment
+
+**Output:** Test plan
+
+### Step 2: Unit Testing
+**Agent:** tester
+**Duration:** 1-2 hours
+
+Write unit tests:
+- Handler tests
+- Validation tests
+- Business logic tests
+- Error handling tests
+
+**Output:** Unit tests
+
+### Step 3: Integration Testing
+**Agent:** tester
+**Duration:** 1-2 hours
+
+Write integration tests:
+- End-to-end flows
+- Database interactions
+- External service mocks
+- Authentication flows
+
+**Output:** Integration tests
+
+### Step 4: Security Testing
+**Agent:** security-auditor
+**Command:** `/quality:security-scan`
+**Duration:** 30-60 minutes
+
+Security tests:
+- Authentication bypass
+- Authorization checks
+- Input validation
+- Injection attempts
+
+**Output:** Security test results
+
+### Step 5: Performance Testing
+**Agent:** tester
+**Duration:** 30-60 minutes
+
+Performance tests:
+- Load testing
+- Latency benchmarks
+- Throughput tests
+- Resource usage
+
+**Output:** Performance report
+
+### Step 6: Report Generation
+**Agent:** tester
+**Duration:** 30-60 minutes
+
+Generate report:
+- Coverage summary
+- Test results
+- Issues found
+- Recommendations
+
+**Output:** Test report
+
+## Quality Gates
+
+- [ ] Test plan complete
+- [ ] Unit tests passing
+- [ ] Integration tests passing
+- [ ] Security tests passed
+- [ ] Performance acceptable
+- [ ] Report generated
+
+## Test Coverage
+
+```
+API Test Coverage
+=================
+FUNCTIONAL:
+- Happy path scenarios
+- Error scenarios
+- Edge cases
+- Validation rules
+
+SECURITY:
+- Authentication
+- Authorization
+- Input validation
+- Rate limiting
+
+PERFORMANCE:
+- Response time
+- Throughput
+- Scalability
+- Resource usage
+```
+
+## Example Usage
+
+```bash
+/workflow:api-testing "user API endpoints"
+/workflow:api-testing "payment API with security focus"
+```
+
+## Related Workflows
+
+- `api-design` - For API design
+- `security-audit` - For security focus

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