ai-devx 1.0.0 → 1.0.1

package/templates/.agent/workflows/plan.md

@@ -1,153 +1,89 @@
 ---
-command: /plan
-description: Create comprehensive task breakdown and implementation plan
-agent: project-planner
-skills:
-  - brainstorming
-  - plan-writing
-  - architecture
-  - estimation
+description: Create project plan using project-planner agent. No code writing - only plan file generation.
 ---
 
-# /plan Workflow
-
-## Purpose
-Break down complex requirements into actionable tasks with estimates, dependencies, and milestones.
-
-## Trigger
-User types: `/plan <description>`
-
-## Execution Steps
-
-### Step 1: Requirements Clarification
-Ask 3-5 strategic questions:
-1. What is the core problem you're solving?
-2. Who are the users and what do they need?
-3. What does success look like?
-4. What are the constraints (time, budget, tech)?
-5. Are there any dependencies or blockers?
-
-### Step 2: Analysis
-- Parse user request
-- Identify ambiguous requirements
-- Determine scope and complexity
-- Identify technical constraints
-
-### Step 3: Task Decomposition
-Break down into:
-- High-level objectives
-- Technical tasks
-- Dependencies between tasks
-- Risks and mitigations
-
-### Step 4: Estimation
-Categorize tasks:
-- **Quick wins**: < 2 hours
-- **Small**: 2-4 hours
-- **Medium**: 4-8 hours
-- **Large**: 1-2 days
-- **Epic**: 3-5 days (break down further)
-
-Apply uncertainty multipliers:
-- Well-understood: 1.0x
-- Some uncertainty: 1.5x
-- High uncertainty: 2.0x
-- Research needed: 3.0x
-
-### Step 5: Output Format
-
-Generate structured markdown plan:
-
-```markdown
-## Plan: [Feature Name]
-
-### Overview
-[High-level description of what will be built]
-
-### Goals
-- [Goal 1]
-- [Goal 2]
-- [Goal 3]
-
-### Technical Architecture
-[Architecture decisions and tech stack]
-
-### Tasks
-
-#### Phase 1: Foundation
-| ID | Task | Estimate | Dependencies | Priority |
-|----|------|----------|--------------|----------|
-| T1 | [Task description] | 2h | None | P0 |
-| T2 | [Task description] | 4h | T1 | P0 |
-
-#### Phase 2: Implementation
-| ID | Task | Estimate | Dependencies | Priority |
-|----|------|----------|--------------|----------|
-| T3 | [Task description] | 8h | T2 | P1 |
-
-### Milestones
-1. **Milestone 1** - [Date]: [Description]
-2. **Milestone 2** - [Date]: [Description]
-3. **Milestone 3** - [Date]: [Description]
-
-### Risks
-| Risk | Probability | Impact | Mitigation |
-|------|-------------|--------|------------|
-| [Risk 1] | High/Med/Low | High/Med/Low | [Strategy] |
-
-### Resources Needed
-- [Role 1]: [Number needed]
-- [Role 2]: [Number needed]
-
-### Definition of Done
-- [ ] All P0 tasks complete
-- [ ] Code reviewed
-- [ ] Tests passing
-- [ ] Documentation updated
-- [ ] Deployed to staging
-
-### Next Steps
-1. [Action item 1]
-2. [Action item 2]
-```
+# /plan - Project Planning Mode
+
+$ARGUMENTS
+
+---
+
+## 🔴 CRITICAL RULES
 
-## Example Usage
+1. **NO CODE WRITING** - This command creates plan file only
+2. **Use project-planner agent** - NOT Antigravity Agent's native Plan mode
+3. **Socratic Gate** - Ask clarifying questions before planning
+4. **Dynamic Naming** - Plan file named based on task
 
-**User**: `/plan Build a user authentication system with JWT`
+---
 
-**Response**:
+## Task
+
+Use the `project-planner` agent with this context:
+
+```
+CONTEXT:
+- User Request: $ARGUMENTS
+- Mode: PLANNING ONLY (no code)
+- Output: docs/PLAN-{task-slug}.md (dynamic naming)
+
+NAMING RULES:
+1. Extract 2-3 key words from request
+2. Lowercase, hyphen-separated
+3. Max 30 characters
+4. Example: "e-commerce cart" → PLAN-ecommerce-cart.md
+
+RULES:
+1. Follow project-planner.md Phase -1 (Context Check)
+2. Follow project-planner.md Phase 0 (Socratic Gate)
+3. Create PLAN-{slug}.md with task breakdown
+4. DO NOT write any code files
+5. REPORT the exact file name created
 ```
-⚡ Executing /plan
 
-## Plan: User Authentication System with JWT
+---
+
+## Expected Output
 
-### Overview
-Implement secure user authentication using JWT tokens with login, signup, and protected routes.
+| Deliverable | Location |
+|-------------|----------|
+| Project Plan | `docs/PLAN-{task-slug}.md` |
+| Task Breakdown | Inside plan file |
+| Agent Assignments | Inside plan file |
+| Verification Checklist | Phase X in plan file |
 
-### Tasks
+---
 
-#### Phase 1: Backend (2 days)
-| ID | Task | Estimate | Dependencies |
-|----|------|----------|--------------|
-| T1 | Design user schema | 2h | None |
-| T2 | Implement password hashing | 2h | T1 |
-| T3 | Create signup endpoint | 4h | T2 |
-| T4 | Create login endpoint | 4h | T2 |
-| T5 | Implement JWT middleware | 4h | T4 |
+## After Planning
 
-#### Phase 2: Frontend (1.5 days)
-| ID | Task | Estimate | Dependencies |
-|----|------|----------|--------------|
-| T6 | Create login form | 4h | None |
-| T7 | Create signup form | 4h | None |
-| T8 | Implement auth context | 4h | T6, T7 |
+Tell user:
+```
+[OK] Plan created: docs/PLAN-{slug}.md
 
-Total: 3.5 days
+Next steps:
+- Review the plan
+- Run `/create` to start implementation
+- Or modify plan manually
 ```
 
-## Success Criteria
-- Clear task breakdown with estimates
-- Identified dependencies
-- Risk assessment
-- Realistic timeline
-- Actionable next steps
+---
+
+## Naming Examples
+
+| Request | Plan File |
+|---------|-----------|
+| `/plan e-commerce site with cart` | `docs/PLAN-ecommerce-cart.md` |
+| `/plan mobile app for fitness` | `docs/PLAN-fitness-app.md` |
+| `/plan add dark mode feature` | `docs/PLAN-dark-mode.md` |
+| `/plan fix authentication bug` | `docs/PLAN-auth-fix.md` |
+| `/plan SaaS dashboard` | `docs/PLAN-saas-dashboard.md` |
+
+---
+
+## Usage
+
+```
+/plan e-commerce site with cart
+/plan mobile app for fitness tracking
+/plan SaaS dashboard with analytics
+```

package/templates/.agent/workflows/preview.md

@@ -0,0 +1,81 @@
+---
+description: Preview server start, stop, and status check. Local development server management.
+---
+
+# /preview - Preview Management
+
+$ARGUMENTS
+
+---
+
+## Task
+
+Manage preview server: start, stop, status check.
+
+### Commands
+
+```
+/preview           - Show current status
+/preview start     - Start server
+/preview stop      - Stop server
+/preview restart   - Restart
+/preview check     - Health check
+```
+
+---
+
+## Usage Examples
+
+### Start Server
+```
+/preview start
+
+Response:
+🚀 Starting preview...
+   Port: 3000
+   Type: Next.js
+
+✅ Preview ready!
+   URL: http://localhost:3000
+```
+
+### Status Check
+```
+/preview
+
+Response:
+=== Preview Status ===
+
+🌐 URL: http://localhost:3000
+📁 Project: C:/projects/my-app
+🏷️ Type: nextjs
+💚 Health: OK
+```
+
+### Port Conflict
+```
+/preview start
+
+Response:
+⚠️ Port 3000 is in use.
+
+Options:
+1. Start on port 3001
+2. Close app on 3000
+3. Specify different port
+
+Which one? (default: 1)
+```
+
+---
+
+## Technical
+
+Auto preview uses `auto_preview.py` script:
+
+```bash
+python .agent/scripts/auto_preview.py start [port]
+python .agent/scripts/auto_preview.py stop
+python .agent/scripts/auto_preview.py status
+```
+

package/templates/.agent/workflows/status.md

@@ -0,0 +1,86 @@
+---
+description: Display agent and project status. Progress tracking and status board.
+---
+
+# /status - Show Status
+
+$ARGUMENTS
+
+---
+
+## Task
+
+Show current project and agent status.
+
+### What It Shows
+
+1. **Project Info**
+   - Project name and path
+   - Tech stack
+   - Current features
+
+2. **Agent Status Board**
+   - Which agents are running
+   - Which tasks are completed
+   - Pending work
+
+3. **File Statistics**
+   - Files created count
+   - Files modified count
+
+4. **Preview Status**
+   - Is server running
+   - URL
+   - Health check
+
+---
+
+## Example Output
+
+```
+=== Project Status ===
+
+📁 Project: my-ecommerce
+📂 Path: C:/projects/my-ecommerce
+🏷️ Type: nextjs-ecommerce
+📊 Status: active
+
+🔧 Tech Stack:
+   Framework: next.js
+   Database: postgresql
+   Auth: clerk
+   Payment: stripe
+
+✅ Features (5):
+   • product-listing
+   • cart
+   • checkout
+   • user-auth
+   • order-history
+
+⏳ Pending (2):
+   • admin-panel
+   • email-notifications
+
+📄 Files: 73 created, 12 modified
+
+=== Agent Status ===
+
+✅ database-architect → Completed
+✅ backend-specialist → Completed
+🔄 frontend-specialist → Dashboard components (60%)
+⏳ test-engineer → Waiting
+
+=== Preview ===
+
+🌐 URL: http://localhost:3000
+💚 Health: OK
+```
+
+---
+
+## Technical
+
+Status uses these scripts:
+- `python .agent/scripts/session_manager.py status`
+- `python .agent/scripts/auto_preview.py status`

package/templates/.agent/workflows/test.md

@@ -1,165 +1,144 @@
 ---
-command: /test
-description: Generate and run tests for code coverage and quality assurance
-agent: test-engineer
-skills:
-  - testing-patterns
-  - webapp-testing
-  - tdd-workflow
-mode: thorough
+description: Test generation and test running command. Creates and executes tests for code.
 ---
 
-# /test Workflow
+# /test - Test Generation and Execution
 
-## Purpose
-Generate comprehensive tests, run test suites, and improve code coverage.
+$ARGUMENTS
 
-## Trigger
-User types: `/test <target>` or `/test all`
+---
 
-## Execution Steps
+## Purpose
 
-### Step 1: Test Discovery
-Identify what needs testing:
-- Untested files/functions
-- Critical business logic
-- API endpoints
-- UI components
-- Edge cases
+This command generates tests, runs existing tests, or checks test coverage.
 
-### Step 2: Test Generation
+---
 
-**Unit Tests:**
-```typescript
-- Test happy paths
-- Test error cases
-- Test edge cases
-- Test boundary conditions
-- Mock external dependencies
-```
+## Sub-commands
 
-**Integration Tests:**
-```typescript
-- Test API endpoints
-- Test database interactions
-- Test service integrations
-- Test authentication flows
 ```
-
-**E2E Tests:**
-```typescript
-- Test critical user flows
-- Test form submissions
-- Test navigation
-- Test error handling
+/test                - Run all tests
+/test [file/feature] - Generate tests for specific target
+/test coverage       - Show test coverage report
+/test watch          - Run tests in watch mode
 ```
 
-### Step 3: Test Implementation
-Follow AAA pattern:
-```typescript
-describe('functionName', () => {
-  it('should [expected behavior] when [condition]', () => {
-    // Arrange
-    const input = ...;
-    
-    // Act
-    const result = functionName(input);
-    
-    // Assert
-    expect(result).toBe(expected);
-  });
-});
-```
+---
 
-### Step 4: Test Execution
-Run tests and report:
-- Total tests
-- Passed/Failed
-- Coverage percentage
-- Duration
+## Behavior
 
-### Step 5: Coverage Analysis
-Check coverage gaps:
-- Branches not covered
-- Functions not tested
-- Lines not executed
-- Prioritize critical code
+### Generate Tests
 
-### Step 6: Coverage Improvement
-Add tests for uncovered code:
-- Edge cases
-- Error paths
-- Complex logic
+When asked to test a file or feature:
 
-## Response Format
+1. **Analyze the code**
+   - Identify functions and methods
+   - Find edge cases
+   - Detect dependencies to mock
 
-```
-⚡ Executing /test
+2. **Generate test cases**
+   - Happy path tests
+   - Error cases
+   - Edge cases
+   - Integration tests (if needed)
+
+3. **Write tests**
+   - Use project's test framework (Jest, Vitest, etc.)
+   - Follow existing test patterns
+   - Mock external dependencies
 
-🤖 Applying @test-engineer...
+---
+
+## Output Format
+
+### For Test Generation
 
-## Test Generation
+```markdown
+## 🧪 Tests: [Target]
 
-### Files to Test
-- [file1]: [reason]
-- [file2]: [reason]
+### Test Plan
+| Test Case | Type | Coverage |
+|-----------|------|----------|
+| Should create user | Unit | Happy path |
+| Should reject invalid email | Unit | Validation |
+| Should handle db error | Unit | Error case |
 
 ### Generated Tests
 
-#### Unit Tests
-```typescript
-[Code]
+`tests/[file].test.ts`
+
+[Code block with tests]
+
+---
+
+Run with: `npm test`
 ```
 
-#### Integration Tests  
-```typescript
-[Code]
+### For Test Execution
+
 ```
+🧪 Running tests...
+
+✅ auth.test.ts (5 passed)
+✅ user.test.ts (8 passed)
+❌ order.test.ts (2 passed, 1 failed)
+
+Failed:
+  ✗ should calculate total with discount
+    Expected: 90
+    Received: 100
+
+Total: 15 tests (14 passed, 1 failed)
+```
+
+---
+
+## Examples
 
-## Test Results
-
-### Summary
-- Total: 50 tests
-- Passed: 48 ✅
-- Failed: 2 ❌
-- Skipped: 0
-
-### Coverage
-| Metric | Before | After | Target |
-|--------|--------|-------|--------|
-| Statements | 60% | 85% | 80% ✅ |
-| Branches | 50% | 75% | 80% ⚠️ |
-| Functions | 70% | 90% | 80% ✅ |
-| Lines | 65% | 85% | 80% ✅ |
-
-### Failed Tests
-1. [Test name]: [Error]
-   - Fix: [Solution]
-
-## Recommendations
-- [Recommendation 1]
-- [Recommendation 2]
 ```
+/test src/services/auth.service.ts
+/test user registration flow
+/test coverage
+/test fix failed tests
+```
+
+---
 
-## Commands
+## Test Patterns
 
-**Test specific file:**
-`/test UserService.ts`
+### Unit Test Structure
 
-**Test all:**
-`/test all`
+```typescript
+describe('AuthService', () => {
+  describe('login', () => {
+    it('should return token for valid credentials', async () => {
+      // Arrange
+      const credentials = { email: 'test@test.com', password: 'pass123' };
+      
+      // Act
+      const result = await authService.login(credentials);
+      
+      // Assert
+      expect(result.token).toBeDefined();
+    });
+
+    it('should throw for invalid password', async () => {
+      // Arrange
+      const credentials = { email: 'test@test.com', password: 'wrong' };
+      
+      // Act & Assert
+      await expect(authService.login(credentials)).rejects.toThrow('Invalid credentials');
+    });
+  });
+});
+```
 
-**Test specific type:**
-`/test --unit`
-`/test --integration`
-`/test --e2e`
+---
 
-**Coverage report:**
-`/test --coverage`
+## Key Principles
 
-## Success Criteria
-- New tests generated
-- Coverage improved
-- Critical paths tested
-- All tests passing
-- Edge cases covered
+- **Test behavior not implementation**
+- **One assertion per test** (when practical)
+- **Descriptive test names**
+- **Arrange-Act-Assert pattern**
+- **Mock external dependencies**