omgkit 2.10.0 → 2.11.0

package/plugin/commands/auto/next.md

@@ -0,0 +1,278 @@
+---
+description: Preview and execute the next autonomous action
+allowed-tools: Task, Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion
+argument-hint: "[--preview | --execute | --skip]"
+---
+
+# Next Autonomous Action
+
+Preview or execute the next action in the autonomous workflow.
+
+## Modes
+
+### Preview Mode (Default)
+Show what the next action will be without executing:
+```bash
+/auto:next
+/auto:next --preview
+```
+
+### Execute Mode
+Execute the next single action:
+```bash
+/auto:next --execute
+```
+
+### Skip Mode
+Skip the next action and move forward:
+```bash
+/auto:next --skip
+```
+
+## Action Determination
+
+### 1. Load Current State
+
+```yaml
+phase: "backend"
+status: "in_progress"
+progress:
+  current_feature: "user_authentication"
+  current_step: "implement_password_hashing"
+  steps_completed: ["create_user_model", "add_validation"]
+```
+
+### 2. Determine Next Action
+
+From archetype and feature list:
+1. If current step incomplete → Complete current step
+2. If current step complete → Next step in feature
+3. If feature complete → Next feature in phase
+4. If phase complete → Check quality gates
+5. If gates pass → Next phase (or checkpoint)
+
+### 3. Calculate Action Details
+
+```yaml
+next_action:
+  type: "implement"  # implement | test | review | checkpoint | quality_gate
+  target: "password hashing utility"
+  phase: "backend"
+  feature: "user_authentication"
+  step: "implement_password_hashing"
+
+  details:
+    files_to_create:
+      - "src/utils/password.ts"
+    files_to_modify:
+      - "src/services/user.service.ts"
+    tests_to_run:
+      - "password.test.ts"
+
+  autonomy_level: 1
+  estimated_complexity: "low"
+```
+
+## Preview Output
+
+```
+## Next Action Preview
+
+### Action: Implement Password Hashing
+
+**Type:** Implementation
+**Phase:** Backend > User Authentication
+**Step:** 3 of 7
+**Autonomy Level:** 1 (Execute with notification)
+
+### What Will Be Done
+
+1. **Create** `src/utils/password.ts`
+   - hashPassword(plain: string): Promise<string>
+   - verifyPassword(plain: string, hash: string): Promise<boolean>
+   - Using bcrypt with cost factor 12
+
+2. **Modify** `src/services/user.service.ts`
+   - Import password utilities
+   - Hash password in create() method
+   - Add password verification in login()
+
+3. **Create Tests** `src/utils/password.test.ts`
+   - Test password hashing
+   - Test password verification
+   - Test invalid inputs
+
+### Dependencies
+- bcrypt: Already installed ✓
+- @types/bcrypt: Already installed ✓
+
+### After This Step
+- Next: Implement login endpoint
+- Remaining in feature: 4 steps
+- Quality gate: npm test (required)
+
+---
+
+**Commands:**
+- `/auto:next --execute` - Execute this action
+- `/auto:next --skip` - Skip this action
+- `/auto:start` - Continue autonomous execution
+```
+
+## Execute Output
+
+```
+## Executing: Implement Password Hashing
+
+### Progress
+
+[1/3] Creating src/utils/password.ts...
+      ✓ Created with hashPassword and verifyPassword functions
+
+[2/3] Modifying src/services/user.service.ts...
+      ✓ Added password hashing in create()
+      ✓ Added password verification in login()
+
+[3/3] Creating tests...
+      ✓ Created src/utils/password.test.ts
+
+### Running Quality Gate
+
+```
+npm test -- password.test.ts
+
+  Password Utilities
+    ✓ should hash password (45ms)
+    ✓ should verify correct password (42ms)
+    ✓ should reject incorrect password (41ms)
+    ✓ should handle empty input (2ms)
+
+  4 passing (130ms)
+```
+
+### Action Complete ✓
+
+**Files Created:** 2
+**Files Modified:** 1
+**Tests Passing:** 4/4
+
+### Next Action
+Implement login endpoint
+
+**Commands:**
+- `/auto:next` - Preview next action
+- `/auto:next --execute` - Execute next action
+- `/auto:start` - Continue autonomous execution
+```
+
+## Skip Output
+
+```
+## Skipping: Implement Password Hashing
+
+**Reason:** User requested skip
+
+### Impact
+- Step marked as SKIPPED
+- May cause issues in dependent steps
+- Manual completion required later
+
+### State Updated
+```yaml
+progress:
+  skipped_steps:
+    - step: "implement_password_hashing"
+      reason: "user_skip"
+      timestamp: "2024-01-15T10:30:00Z"
+```
+
+### Warning
+The following steps may be affected:
+- implement_login_endpoint (depends on password verification)
+- implement_password_reset (depends on password hashing)
+
+### Next Action
+Implement login endpoint
+
+---
+
+**Note:** Skipped steps are tracked and must be completed before deployment.
+```
+
+## Special Cases
+
+### At Checkpoint
+```
+## Next Action: Checkpoint
+
+**Phase Complete:** Planning
+
+Before continuing, review is required:
+
+### Generated Artifacts
+- `.omgkit/generated/schema.sql`
+- `.omgkit/generated/api-spec.md`
+
+### Quality Gates Passed
+- ✓ Schema validation
+- ✓ API spec validation
+
+---
+
+**Commands:**
+- `/auto:approve` - Approve and continue
+- `/auto:reject "feedback"` - Request changes
+```
+
+### At Phase Boundary
+```
+## Next Action: Start New Phase
+
+**Completed:** Planning Phase
+**Starting:** Foundation Phase
+
+### Phase Overview: Foundation
+1. Project scaffolding (auto)
+2. Database setup (auto)
+3. UI foundation (auto)
+
+**Estimated:** 3 automated steps
+
+---
+
+**Commands:**
+- `/auto:next --execute` - Start foundation phase
+- `/auto:checkpoint` - Pause for review first
+```
+
+### No More Actions
+```
+## Project Complete! 🎉
+
+All phases have been completed.
+
+### Summary
+- **Phases Completed:** 8/8
+- **Features Implemented:** 12
+- **Tests Passing:** 47/47
+- **Coverage:** 84%
+
+### Final Quality Gates
+- ✓ All tests pass
+- ✓ Build succeeds
+- ✓ Coverage > 80%
+- ✓ No security issues
+
+### Generated Project
+[Project structure and key files]
+
+### Next Steps
+1. Review the complete implementation
+2. Deploy to staging environment
+3. Conduct user testing
+
+---
+
+**Commands:**
+- `/auto:status --verbose` - Full project report
+```

package/plugin/commands/auto/reject.md

@@ -0,0 +1,278 @@
+---
+description: Reject checkpoint or decision with feedback
+allowed-tools: Read, Write, Edit, AskUserQuestion
+argument-hint: "<reason> [--checkpoint | --decision <id>]"
+---
+
+# Reject Checkpoint or Decision
+
+Reject a pending checkpoint or decision and provide feedback for revision.
+
+## Usage
+
+### Reject with Reason
+```bash
+/auto:reject "The schema needs a soft delete column for users"
+```
+
+### Reject Specific Checkpoint
+```bash
+/auto:reject --checkpoint "API endpoints don't match PRD requirements"
+```
+
+### Reject Specific Decision
+```bash
+/auto:reject --decision db_index_strategy "Use separate indexes instead"
+```
+
+## Rejection Process
+
+### 1. Capture Feedback
+
+Parse the rejection reason and categorize:
+- **Scope change**: Requirements changed
+- **Quality issue**: Doesn't meet standards
+- **Design issue**: Approach needs revision
+- **Missing item**: Something was forgotten
+- **Other**: Custom feedback
+
+### 2. Update State
+
+```yaml
+# .omgkit/state.yaml
+checkpoint:
+  pending: true
+  rejected: true
+  rejection:
+    reason: "The schema needs a soft delete column for users"
+    category: "missing_item"
+    timestamp: "2024-01-15T10:30:00Z"
+
+status: "revision_needed"
+```
+
+### 3. Analyze Impact
+
+Determine what needs to change:
+```yaml
+impact_analysis:
+  files_to_revise:
+    - ".omgkit/generated/schema.sql"
+    - "prisma/schema.prisma"
+  decisions_affected:
+    - "user_model_design"
+  estimated_rework: "minor"  # minor | moderate | major
+```
+
+### 4. Generate Revision Plan
+
+Based on feedback, create revision tasks:
+```yaml
+revision_tasks:
+  - id: "add_soft_delete"
+    description: "Add deleted_at column to users table"
+    files:
+      - "schema.sql"
+      - "schema.prisma"
+  - id: "update_queries"
+    description: "Add soft delete filter to user queries"
+    files:
+      - "user.service.ts"
+```
+
+### 5. Record in Memory
+
+Save rejection for learning:
+```markdown
+# Rejection: Planning Phase
+
+**Date:** 2024-01-15
+**Phase:** Planning
+**Reason:** The schema needs a soft delete column for users
+
+## Original Approach
+Schema designed without soft delete capability.
+
+## Feedback
+User requires soft delete for data recovery and audit purposes.
+
+## Revision Plan
+1. Add deleted_at column to users table
+2. Update queries to filter deleted records
+3. Add restore functionality
+
+## Lessons
+- Always consider data retention requirements early
+- Include soft delete in standard entity patterns
+```
+
+## Output
+
+### Checkpoint Rejection
+```
+## Checkpoint Rejected
+
+**Phase:** Planning
+**Reason:** The schema needs a soft delete column for users
+
+### Impact Analysis
+
+**Severity:** Minor
+**Files Affected:** 2
+
+1. `.omgkit/generated/schema.sql`
+   - Add: `deleted_at TIMESTAMP NULL`
+
+2. `prisma/schema.prisma` (when created)
+   - Add: `deletedAt DateTime?`
+
+### Revision Plan
+
+I'll make the following changes:
+
+1. **Update Schema**
+   - Add `deleted_at` column to users table
+   - Add index on `deleted_at` for query performance
+
+2. **Update Queries** (during implementation)
+   - Filter `WHERE deleted_at IS NULL` by default
+   - Add methods for soft delete and restore
+
+### Proceeding with Revision
+
+Would you like me to:
+A. Revise the schema now and show you the updated version
+B. Note this for implementation phase
+C. Discuss the soft delete approach further
+
+---
+
+**Commands:**
+- `/auto:resume` - After approving revision
+- `/auto:status` - Check current state
+```
+
+### Decision Rejection
+```
+## Decision Rejected
+
+**Decision:** db_index_strategy
+**Original:** Add composite index on users(email, status)
+**Rejection:** Use separate indexes instead
+
+### Alternative Approach
+
+Based on your feedback, will use:
+```sql
+-- Instead of composite index
+CREATE INDEX idx_users_email ON users(email);
+CREATE INDEX idx_users_status ON users(status);
+```
+
+### Trade-offs
+
+| Approach | Pros | Cons |
+|----------|------|------|
+| Composite | Faster combined queries | Less flexible |
+| Separate | More query patterns | More storage |
+
+### Updated Decision
+
+Recorded your preference for separate indexes.
+
+---
+
+**Commands:**
+- `/auto:approve decision db_index_strategy` - If revised version is acceptable
+- `/auto:start` - Continue with new approach
+```
+
+## Rejection with Questions
+
+If feedback is unclear, ask clarifying questions:
+
+```
+## Clarification Needed
+
+**Your Feedback:** "The schema needs work"
+
+I'd like to understand better:
+
+1. **Which tables need changes?**
+   A. Users table
+   B. All tables
+   C. Specific tables: [specify]
+
+2. **What type of changes?**
+   A. Add columns
+   B. Change relationships
+   C. Performance optimization
+   D. Other: [specify]
+
+3. **Any specific requirements?**
+   [Open response]
+
+---
+
+Please provide more details so I can make the right revisions.
+```
+
+## Major Rejection
+
+For significant rejections that require major rework:
+
+```
+## Major Revision Required
+
+**Feedback:** "We need to switch from SQL to MongoDB"
+
+### Impact Assessment
+
+**Severity:** Major
+**Rework Required:** Significant
+
+### Affected Artifacts
+- ❌ `.omgkit/generated/schema.sql` - Will be replaced
+- ⚠️ `.omgkit/generated/prd.md` - Needs update
+- ⚠️ `.omgkit/generated/technical-spec.md` - Needs update
+
+### Recommended Action
+
+This is a fundamental architecture change. I recommend:
+
+1. **Return to Discovery** - Update technical requirements
+2. **Update PRD** - Reflect database change
+3. **New Technical Spec** - Design for MongoDB
+4. **Restart Planning** - New schema design
+
+### Alternative
+
+If you want to minimize rework:
+- Keep current phase artifacts
+- Add MongoDB migration as future task
+- Continue with SQL for MVP
+
+---
+
+**Which approach would you prefer?**
+
+A. Full revision (return to discovery)
+B. Partial revision (update planning only)
+C. Note for future (continue current path)
+D. Discuss further
+```
+
+## Rejection History
+
+Track rejections for pattern analysis:
+
+```yaml
+# .omgkit/state.yaml
+rejection_history:
+  - phase: "planning"
+    reason: "Missing soft delete"
+    category: "missing_item"
+    timestamp: "2024-01-15T10:30:00Z"
+    resolved: true
+    resolution: "Added deleted_at column"
+```