devflow-prompts 1.0.0

package/README.md

@@ -0,0 +1,914 @@
+# DevFlow Prompts - Development Workflow System
+
+DevFlow (Development Flow) is a comprehensive prompt system that automates the software development process from raw customer request → production-ready code + tests.
+
+## 📦 Installation
+
+To install DevFlow Prompts in your project:
+
+```bash
+# Initialize in your project root
+npm install devflow-prompts
+npx devflow-prompts init
+```
+
+This will create a `devflow-prompts/` directory in your project with all necessary prompts, scripts, and rules.
+
+Once installed, run the setup script to configure your IDE:
+
+```bash
+./devflow-prompts/gen-chat.sh
+```
+
+---
+
+## 🔄 Updating / Upgrading
+
+When you upgrade `devflow-prompts` to a newer version and run `npx devflow-prompts init`, the script will handle your existing files intelligently:
+
+1.  **Safe Mode (Default)**:
+    It will **skip** any files that you have modified, ensuring your customizations are preserved.
+
+    ```bash
+    npx devflow-prompts init
+    ```
+
+2.  **Force Overwrite**:
+    Use `--force` if you want to **reset** everything to the latest defaults (warning: this will overwrite your changes).
+
+    ```bash
+    npx devflow-prompts init --force
+    ```
+
+3.  **Conflict Resolution**:
+    If a file exists but is different from the new version, the script will create a `.new` file (e.g., `README.md.new`) instead of overwriting. You can then compare and merge the changes manually.
+
+---
+
+## 📋 Overview
+
+**Prefix**: `/devflow.` - Distinguishes from other workflow systems
+
+## 🎯 Complete Workflow (Step 0-6)
+
+```
+[Step 0] Generate Coding Rules (One-time setup)
+    ↓
+[Step 1] Requirement Document
+    ↓
+[Step 2] Technical Design
+    ↓
+[Step 3] Feature Code
+    ↓
+[Step 4] Test Plan
+    ↓
+[Step 5] Test Code
+    ↓
+[Step 6] Validate & Analyze
+```
+
+## 🚀 Quick Start Guide
+
+### Prerequisites
+
+Run the setup script for your IDE:
+
+```bash
+# For Antigravity
+./devflow-prompts/gen-chat.sh antigravity
+
+# For VSCode
+./devflow-prompts/gen-chat.sh vscode
+
+# For Cursor
+./devflow-prompts/gen-chat.sh cursor
+
+# Auto-detect IDE (if supported)
+./devflow-prompts/gen-chat.sh
+```
+
+This will install all DevFlow prompts and enable autocomplete for `/devflow.*` commands.
+
+---
+
+## 📦 Output Summary - What Each Step Produces
+
+### Step 0: Generate Rules (One-time)
+
+**Output:** 10 markdown files  
+**Location:** `/devflow-prompts/rules/`  
+**Action:** ✅ AI auto-creates files  
+**Manual step:** ❌ None
+
+---
+
+### Step 1: Requirement
+
+**Output:** 1 markdown file (`{task-id}-requirement.md`)  
+**Location:** `/devflow-prompts/specs/{task-id}/`  
+**Action:** ✅ AI auto-creates file  
+**Manual step:** ❌ None
+
+---
+
+### Step 2: Design
+
+**Output:** 1 markdown file (`{task-id}-design.md`)  
+**Location:** `/devflow-prompts/specs/{task-id}/`  
+**Action:** ✅ AI auto-creates file  
+**Manual step:** ❌ None
+
+---
+
+### Step 3: Code ⚠️ (Manual Action Required)
+
+**Output:** 1 git patch file (`{task-id}-feature.patch`)  
+**Location:** `/devflow-prompts/specs/{task-id}/`  
+**Action:** ⚠️ AI generates patch  
+**Manual step:** ✅ **YOU must apply patch**
+
+**⚠️ Warning:** AI only creates the patch file. You must manually run `git apply` to create the actual source code files in your project.
+
+```bash
+cd /path/to/your/project
+git apply --check devflow-prompts/specs/FEAT-001/FEAT-001-feature.patch
+git apply devflow-prompts/specs/FEAT-001/FEAT-001-feature.patch
+git status
+```
+
+---
+
+### Step 4: Test Plan
+
+**Output:** 1 markdown file (`{task-id}-test.md`)  
+**Location:** `/devflow-prompts/specs/{task-id}/`  
+**Action:** ✅ AI auto-creates file  
+**Manual step:** ❌ None
+
+---
+
+### Step 5: Test Code ⚠️ (Manual Action Required)
+
+**Output:** 1 git patch file (`{task-id}-test.patch`)  
+**Location:** `/devflow-prompts/specs/{task-id}/`  
+**Action:** ⚠️ AI generates patch  
+**Manual step:** ✅ **YOU must apply patch**
+
+**⚠️ Warning:** AI only creates the patch file. You must manually run `git apply` to create the actual test files in your project.
+
+```bash
+cd /path/to/your/project
+git apply --check devflow-prompts/specs/FEAT-001/FEAT-001-test.patch
+git apply devflow-prompts/specs/FEAT-001/FEAT-001-test.patch
+./vendor/bin/phpunit  # Run tests
+```
+
+---
+
+### Step 6: Analyze
+
+**Output:** Analysis report (inline text)  
+**Location:** Inline in AI response  
+**Action:** ℹ️ AI displays report  
+**Manual step:** ❌ None (read only)
+
+---
+
+## 📚 Step-by-Step Guide
+
+### Step 0: Generate Coding Rules (One-time Setup)
+
+**Purpose**: Create project-specific coding standards and quality checklists.
+
+#### Commands:
+
+| Command                | Purpose                                  |
+| ---------------------- | ---------------------------------------- |
+| `/devflow.0-gen-rules` | Generate coding rules for specific steps |
+| `/devflow.0-rev-rules` | Review and improve generated rules       |
+
+#### Usage Example:
+
+**Input Type: File Path (Required)**
+
+1. Copy template file:
+
+```bash
+cp devflow-prompts/templates/gen-rule-template.txt my-rules-input.txt
+```
+
+2. Edit `my-rules-input.txt`:
+
+```text
+Step: all
+Stack: Laravel (Backend) + Vue.js (Frontend)
+Architecture: Clean Architecture
+Team: 5 developers, mid-level experience
+Constraints: Must support 10k concurrent users, PCI-DSS compliance required
+Language: en
+```
+
+3. Run command:
+
+```bash
+/devflow.0-gen-rules my-rules-input.txt
+```
+
+**Output**: 10 rule files in `/devflow-prompts/rules/`:
+
+**Output**: 10 rule files in `/devflow-prompts/rules/`:
+
+```
+/devflow-prompts/rules/
+├── devflow.1-gen-requirement.rule.md
+├── devflow.1-rev-requirement.rule.md
+├── devflow.2-gen-design.rule.md
+├── devflow.2-rev-design.rule.md
+├── devflow.3-gen-code.rule.md
+├── devflow.3-rev-code.rule.md
+├── devflow.4-gen-test-plan.rule.md
+├── devflow.4-rev-test-plan.rule.md
+├── devflow.5-gen-test-code.rule.md
+└── devflow.5-rev-test-code.rule.md
+```
+
+#### Generate Rules for Specific Step:
+
+```bash
+# Generate both gen + rev rules for Step 1 (Requirement)
+/devflow.0-gen-rules
+
+Step: 1
+Stack: Laravel + Vue.js
+Architecture: Clean Architecture
+
+# → Generates: devflow.1-gen-requirement.rule.md, devflow.1-rev-requirement.rule.md
+```
+
+#### Generate Individual Rule File (Granular):
+
+**Use cases:**
+
+- Fix/iterate on a specific rule file
+- Regenerate only gen-rule or rev-rule
+
+```bash
+# Generate ONLY gen-rule for Step 3 (Code)
+/devflow.0-gen-rules
+
+Step: 3-gen
+Stack: Laravel + Vue.js
+Architecture: Clean Architecture
+
+# → Generates: devflow.3-gen-code.rule.md (only)
+
+# Generate ONLY rev-rule for Step 2 (Design)
+/devflow.0-gen-rules
+
+Step: 2-rev
+Stack: Laravel + Vue.js
+Architecture: Clean Architecture
+
+# → Generates: devflow.2-rev-design.rule.md (only)
+```
+
+**Available options:**
+
+- `1`, `2`, `3`, `4`, `5` - Generate both gen + rev for that step
+- `1-gen`, `2-gen`, etc. - Generate only gen-rule
+- `1-rev`, `2-rev`, etc. - Generate only rev-rule
+- `all` - Generate all 10 files
+
+#### Review Generated Rules:
+
+```bash
+# Option 1: Review all rules in directory (Recommended)
+/devflow.0-rev-rules /devflow-prompts/rules/
+
+# Option 2: Review specific file
+/devflow.0-rev-rules /devflow-prompts/rules/devflow.1-gen-requirement.rule.md
+```
+
+**Review specific step or individual file:**
+
+```bash
+# Review both gen + rev for Step 3 (Code)
+/devflow.0-rev-rules /devflow-prompts/rules/devflow.3-gen-code.rule.md /devflow-prompts/rules/devflow.3-rev-code.rule.md
+
+# Review ONLY gen-rule for Step 2 (Design)
+/devflow.0-rev-rules /devflow-prompts/rules/devflow.2-gen-design.rule.md
+```
+
+**Available options:**
+
+- `1`, `2`, `3`, `4`, `5` - Review both gen + rev for that step
+- `1-gen`, `2-gen`, etc. - Review only gen-rule
+- `1-rev`, `2-rev`, etc. - Review only rev-rule
+- `all` - Review all 10 files
+
+---
+
+### Step 1: Requirement Document
+
+**Purpose**: Convert raw customer request into structured, testable requirement document.
+
+#### Commands:
+
+| Command                      | Purpose                               |
+| ---------------------------- | ------------------------------------- |
+| `/devflow.1-gen-requirement` | Convert raw request → requirement doc |
+| `/devflow.1-rev-requirement` | Review requirement for completeness   |
+
+#### Usage Example:
+
+**Input Type: File Path (Required)**
+
+1. Copy template:
+
+```bash
+cp devflow-prompts/templates/gen-requirement-template.txt FEAT-001-request.txt
+```
+
+2. Edit `FEAT-001-request.txt`:
+
+```text
+Task ID: FEAT-001
+Language: en
+Raw Request: I want users to login with email/password. If they enter wrong password too many times, lock the account temporarily for 15 minutes.
+```
+
+3. Run command:
+
+```bash
+/devflow.1-gen-requirement FEAT-001-request.txt
+```
+
+**Output**: `/devflow-prompts/specs/FEAT-001/FEAT-001-requirement.md`
+
+#### Review Requirement:
+
+```bash
+/devflow.1-rev-requirement /devflow-prompts/specs/FEAT-001/FEAT-001-requirement.md
+```
+
+---
+
+### Step 2: Technical Design
+
+**Purpose**: Create implementable technical design from requirement.
+
+#### Commands:
+
+| Command                 | Purpose                             |
+| ----------------------- | ----------------------------------- |
+| `/devflow.2-gen-design` | Create tech design from requirement |
+| `/devflow.2-rev-design` | Review design for implementability  |
+
+#### Usage Example:
+
+```bash
+/devflow.2-gen-design /devflow-prompts/specs/FEAT-001/FEAT-001-requirement.md
+```
+
+**Note**: AI will auto-detect `Task Mode` (New/Update) from the requirement file.
+
+- If `UPDATE` mode: AI inspects existing code via **Coding Rules**, enforcing strict **Impact Analysis** and **Backward Compatibility**.
+
+````
+
+**Output**: `/devflow-prompts/specs/FEAT-001/FEAT-001-design.md` containing:
+- Architecture approach
+- API endpoints (request/response/errors)
+- Data model with migrations
+- Business logic step-by-step
+- Security measures
+- Observability (logs, metrics)
+- Rollout plan
+
+#### Review Design:
+
+```bash
+/devflow.2-rev-design /devflow-prompts/specs/FEAT-001/FEAT-001-design.md
+````
+
+---
+
+### Step 3: Feature Code
+
+**Purpose**: Generate production-ready code from technical design.
+
+#### Commands:
+
+| Command               | Purpose                           |
+| --------------------- | --------------------------------- |
+| `/devflow.3-gen-code` | Generate code from tech design    |
+| `/devflow.3-rev-code` | Review code quality & correctness |
+
+#### Usage Example:
+
+```bash
+/devflow.3-gen-code /devflow-prompts/specs/FEAT-001/FEAT-001-design.md
+```
+
+**Note**: In `UPDATE` mode, AI will:
+
+- Read existing files to match style.
+- Only generate minimal diffs to implementing the change.
+- Protect legacy behavior.
+
+````
+
+**Output**: Git unified diff (patch) - `/devflow-prompts/specs/FEAT-001/FEAT-001-feature.patch`
+
+#### ⚠️ Apply Patch (Manual Step Required):
+
+**AI generates the patch, but YOU must manually apply it:**
+
+```bash
+# Step 1: Navigate to project root
+cd /path/to/your/project
+
+# Step 2: Check if patch can be applied (dry run - no changes made)
+git apply --check devflow-prompts/specs/FEAT-001/FEAT-001-feature.patch
+
+# Step 3: If no errors, apply the patch
+git apply devflow-prompts/specs/FEAT-001/FEAT-001-feature.patch
+
+# Step 4: Verify what files were created/modified
+git status
+git diff
+
+# Step 5: Review changes and commit
+git add .
+git commit -m "feat: implement user login with rate limiting (FEAT-001)"
+````
+
+**Troubleshooting:**
+
+- If `git apply --check` fails → patch conflicts with existing code
+- Solution: Manually review patch file and apply changes
+- Or: Run `/devflow.3-rev-code` to get corrected patch
+
+---
+
+### Step 4: Test Plan
+
+**Purpose**: Create comprehensive test plan covering unit/integration/E2E tests.
+
+#### Commands:
+
+| Command                    | Purpose                             |
+| -------------------------- | ----------------------------------- |
+| `/devflow.4-gen-test-plan` | Create test plan from tech design   |
+| `/devflow.4-rev-test-plan` | Review test coverage & traceability |
+
+#### Usage Example:
+
+```bash
+/devflow.4-gen-test-plan /devflow-prompts/specs/FEAT-001/FEAT-001-design.md
+```
+
+**Output**: `/devflow-prompts/specs/FEAT-001/FEAT-001-test.md` containing:
+
+- Test level strategy (unit/integration/E2E)
+- Detailed test cases
+- Negative & edge cases
+- Mock/stub strategy
+- Test data requirements
+
+#### Review Test Plan:
+
+```bash
+/devflow.4-rev-test-plan /devflow-prompts/specs/FEAT-001/FEAT-001-design.md /devflow-prompts/specs/FEAT-001/FEAT-001-test.md
+```
+
+---
+
+### Step 5: Test Code
+
+**Purpose**: Generate test code from test plan.
+
+#### Commands:
+
+| Command                    | Purpose                           |
+| -------------------------- | --------------------------------- |
+| `/devflow.5-gen-test-code` | Generate test code from test plan |
+| `/devflow.5-rev-test-code` | Review test quality & reliability |
+
+#### Usage Example:
+
+```bash
+/devflow.5-gen-test-code /devflow-prompts/specs/FEAT-001/FEAT-001-test.md
+```
+
+**Output**: Git unified diff (patch) - `/devflow-prompts/specs/FEAT-001/FEAT-001-test.patch`
+
+#### ⚠️ Apply Test Patch (Manual Step Required):
+
+**AI generates the patch, but YOU must manually apply it:**
+
+```bash
+# Step 1: Navigate to project root
+cd /path/to/your/project
+
+# Step 2: Check if patch can be applied (dry run - no changes made)
+git apply --check devflow-prompts/specs/FEAT-001/FEAT-001-test.patch
+
+# Step 3: If no errors, apply the patch
+git apply devflow-prompts/specs/FEAT-001/FEAT-001-test.patch
+
+# Step 4: Verify test files were created
+git status
+
+# Step 5: Run tests to verify they work
+./vendor/bin/phpunit tests/Feature/UserLoginTest.php
+# Or run all tests:
+./vendor/bin/phpunit
+
+# Step 6: If all tests pass, commit
+git add .
+git commit -m "test: add tests for user login with rate limiting (FEAT-001)"
+```
+
+**Troubleshooting:**
+
+- If `git apply --check` fails → patch conflicts with existing test files
+- If tests fail → Review test code or run `/devflow.5-rev-test-code`
+- Solution: Manually review patch file and apply changes
+
+---
+
+### Step 6: Validate & Analyze
+
+**Purpose**: Validate entire flow from requirement → design → code → test, find inconsistencies.
+
+#### Command:
+
+| Command              | Purpose                         |
+| -------------------- | ------------------------------- |
+| `/devflow.6-analyze` | Validate entire flow, find gaps |
+
+#### Usage Example:
+
+```bash
+/devflow.6-analyze \
+  /devflow-prompts/specs/FEAT-001/FEAT-001-requirement.md \
+  /devflow-prompts/specs/FEAT-001/FEAT-001-design.md \
+  /devflow-prompts/specs/FEAT-001/FEAT-001-test.md
+```
+
+**Output**: Analysis report with:
+
+- Alignment check (Requirement ↔ Design ↔ Code ↔ Test)
+- Inconsistencies found (P0/P1/P2)
+- Coverage gaps
+- Recommendations (prioritized)
+
+---
+
+## 📁 File Structure
+
+```
+project/
+├── devflow-prompts/
+│   ├── README.md                    # This file
+│   ├── gen-chat.sh           # Main setup script
+│   │
+│   ├── scripts/                     # IDE-specific setup scripts
+│   │   ├── setup-devflow-chat-antigravity.sh
+│   │   ├── setup-devflow-chat-cursor.sh
+│   │   └── setup-devflow-chat-vscode.sh
+│   │
+│   ├── flows/                       # Prompt definitions
+│   │   ├── devflow.0-gen-rules.prompt.md
+│   │   ├── devflow.1-gen-requirement.prompt.md
+│   │   └── ...
+│   │
+│   ├── templates/                   # Template files for input
+│   │   ├── gen-rule-template.txt       # Template for /devflow.0-gen-rules
+│   │   └── gen-requirement-template.txt # Template for /devflow.1-gen-requirement
+│   │
+│   ├── rules/                       # Coding rules (generated by Step 0)
+│   │   ├── devflow.1-gen-requirement.rule.md
+│   │   ├── devflow.1-rev-requirement.rule.md
+│   │   ├── devflow.2-gen-design.rule.md
+│   │   └── ...
+│   │
+│   └── specs/                       # Feature specifications
+│       └── FEAT-001/
+│           ├── FEAT-001-requirement.md
+│           ├── FEAT-001-design.md
+│           ├── FEAT-001-test.md
+│           ├── FEAT-001-feature.patch
+│           └── FEAT-001-test.patch
+│
+├── .agent/
+│   └── workflows/                   # Installed prompts (after setup)
+│       ├── devflow.0-gen-rules.prompt.md
+│       ├── devflow.1-gen-requirement.prompt.md
+│       └── ...
+│
+└── src/                             # Source code (after applying patches)
+```
+
+---
+
+## 🌍 Multi-Language Support
+
+DevFlow supports multiple languages. Technical terms (API, HTTP, JWT, etc.) always stay in English.
+
+### Supported Languages:
+
+- `en` - English (default)
+- `vi` - Vietnamese
+- `ja` - Japanese
+- `ko` - Korean
+
+### Usage:
+
+**For Rules:**
+
+```text
+Step: all
+Stack: Laravel + Vue.js
+Architecture: Clean Architecture
+Language: vi
+```
+
+**For Requirements:**
+
+```text
+Task ID: FEAT-001
+Language: vi
+Raw Request: Tôi muốn user đăng nhập bằng email/password...
+```
+
+---
+
+## 💡 Tips & Best Practices
+
+### When to Use Which Command?
+
+| Situation                   | Command                      |
+| --------------------------- | ---------------------------- |
+| Starting new project        | `/devflow.0-gen-rules`       |
+| Have raw customer request   | `/devflow.1-gen-requirement` |
+| Requirement unclear         | `/devflow.1-rev-requirement` |
+| Need technical design       | `/devflow.2-gen-design`      |
+| Design has issues           | `/devflow.2-rev-design`      |
+| Need to generate code       | `/devflow.3-gen-code`        |
+| Code has bugs               | `/devflow.3-rev-code`        |
+| Need test plan              | `/devflow.4-gen-test-plan`   |
+| Test coverage insufficient  | `/devflow.4-rev-test-plan`   |
+| Need to generate tests      | `/devflow.5-gen-test-code`   |
+| Tests have issues           | `/devflow.5-rev-test-code`   |
+| Need to validate everything | `/devflow.6-analyze`         |
+
+### Flexible Workflow
+
+Not required to run all commands. Adapt based on task complexity:
+
+**Small task (bug fix)**:
+
+```
+/devflow.1-gen-requirement → /devflow.2-gen-design → /devflow.3-gen-code
+```
+
+**Medium task (new feature)**:
+
+```
+/devflow.1-gen-requirement → /devflow.1-rev-requirement
+→ /devflow.2-gen-design → /devflow.2-rev-design
+→ /devflow.3-gen-code → /devflow.5-gen-test-code
+```
+
+**Large task (critical feature)**:
+
+```
+Full workflow (Step 0-6)
+```
+
+### Using Template Files
+
+**Benefits of using template files:**
+
+- ✅ Reusable for similar tasks
+- ✅ Version control friendly
+- ✅ Easy to share with team
+- ✅ Consistent format
+
+**Workflow:**
+
+1. Copy template from `/devflow-prompts/templates/gen-`
+2. Fill in your information
+3. Save with descriptive name
+4. Pass to command: `/devflow.X-xxx path/to/file.txt`
+
+### Strict File Path Input
+
+**All DevFlow prompts strictly require File Path Input.** "Direct Input" (analyzing pasted text) is NOT supported.
+
+**Requirements:**
+
+1. **Provide the Input Path** (File or Directory) to the command.
+   - **File Path**: Standard input for all commands.
+   - **Directory Path**: Supported by specific commands (e.g., `/devflow.0-rev-rules`) to mass-process files.
+2. **Filename MUST contain a Task ID** (e.g., `FEAT-001`, `TASK-123`).
+   - The AI uses this Task ID to correctly name output files.
+   - The Task ID can be anywhere in the filename.
+
+**Benefits:**
+
+- ✅ **Flexible location**: Files can be anywhere in filesystem (not limited to `/devflow-prompts`)
+- ✅ **Flexible naming**: File names can be anything **as long as they contain the Task ID**
+- ✅ **Faster**: No need to copy/paste content
+- ✅ **Version control**: Keep files in git for tracking
+- ✅ **Reusable**: Easy to iterate and rerun
+
+**Examples:**
+
+```bash
+# Single file input - filename MUST contain Task ID
+/devflow.1-gen-requirement ~/Desktop/FEAT-001-request.txt
+/devflow.2-gen-design /Users/phongle/Documents/FEAT-001-v2.md
+
+# Multiple files input
+/devflow.3-rev-code /path/to/FEAT-001-design.md /path/to/FEAT-001.patch
+/devflow.4-rev-test-plan /path/to/FEAT-001-design.md /path/to/FEAT-001-test.md
+
+# Directory input (e.g. for bulk rule review)
+/devflow.0-rev-rules /devflow-prompts/rules/
+```
+
+# Valid filenames (contain Task ID)
+
+/devflow.1-gen-requirement /path/to/customer-request-FEAT-001.txt
+/devflow.2-gen-design /path/to/FEAT-001-design-v2.md
+/devflow.3-gen-code /path/to/TASK-123-spec.md
+
+````
+
+
+
+##  Complete Example Walkthrough
+
+### Scenario: User Login with Rate Limiting
+
+#### Step 0: Setup (One-time)
+
+```bash
+# Copy template
+cp devflow-prompts/templates/gen-rule-template.txt my-project-rules.txt
+
+# Edit file
+# Step: all
+# Stack: Laravel (PHP 8.2) + Vue 3
+# Architecture: Clean Architecture
+# Team: 5 developers
+
+# Generate rules
+/devflow.0-gen-rules my-project-rules.txt
+````
+
+#### Step 1: Generate Requirement
+
+```bash
+# Copy template
+cp devflow-prompts/templates/gen-requirement-template.txt FEAT-001-request.txt
+
+# Edit file
+# Task ID: FEAT-001
+# Language: en
+# Task Mode: NEW
+# Raw Request: I want users to login with email/password. Lock account after 3 failed attempts for 15 minutes.
+
+
+# Generate requirement
+/devflow.1-gen-requirement FEAT-001-request.txt
+```
+
+**Review**:
+
+```bash
+/devflow.1-rev-requirement /devflow-prompts/specs/FEAT-001/FEAT-001-requirement.md
+```
+
+#### Step 2: Generate Design
+
+```bash
+/devflow.2-gen-design /devflow-prompts/specs/FEAT-001/FEAT-001-requirement.md
+```
+
+**Review**:
+
+```bash
+/devflow.2-rev-design /devflow-prompts/specs/FEAT-001/FEAT-001-design.md
+```
+
+#### Step 3: Generate Code
+
+```bash
+/devflow.3-gen-code /devflow-prompts/specs/FEAT-001/FEAT-001-design.md
+# Apply patch: git apply devflow-prompts/specs/FEAT-001/FEAT-001-feature.patch
+```
+
+#### Step 4: Generate Test Plan
+
+```bash
+/devflow.4-gen-test-plan /devflow-prompts/specs/FEAT-001/FEAT-001-design.md
+```
+
+#### Step 5: Generate Test Code
+
+```bash
+/devflow.5-gen-test-code /devflow-prompts/specs/FEAT-001/FEAT-001-test.md
+# Apply patch: git apply devflow-prompts/specs/FEAT-001/FEAT-001-test.patch
+```
+
+#### Step 6: Validate
+
+```bash
+/devflow.6-analyze \
+  /devflow-prompts/specs/FEAT-001/FEAT-001-requirement.md \
+  /devflow-prompts/specs/FEAT-001/FEAT-001-design.md \
+  /devflow-prompts/specs/FEAT-001/FEAT-001-test.md
+```
+
+---
+
+## 🎯 General Principles
+
+### ✅ DO
+
+- Use template files for consistency
+- Put unclear items in "Open Questions" (don't invent)
+- Make output implementable and testable
+- Follow coding rules
+- Keep changes minimal and cohesive
+
+### ❌ DON'T
+
+- Don't change requirements when doing design
+- Don't redesign when implementing code
+- Don't add features not in spec
+- Don't guess missing information
+
+---
+
+## 🔧 Troubleshooting
+
+### Autocomplete not working?
+
+1. **Reload IDE**:
+   - Antigravity: Restart
+   - VSCode/Cursor: `Cmd+Shift+P` → "Developer: Reload Window"
+
+2. **Re-run setup**:
+
+   ```bash
+   ./devflow-prompts/gen-chat.sh antigravity
+   ```
+
+3. **Check files**:
+   ```bash
+   ls .agent/workflows/devflow.*.md
+   ```
+
+### Commands not appearing?
+
+- Make sure you ran setup for correct IDE
+- Check that files are in correct location
+- Verify file format (must have `# /devflow.X-xxx` heading)
+
+---
+
+## 📞 Support
+
+For issues or questions:
+
+- Check rule files in `/devflow-prompts/rules/`
+- Review prompt files in `/devflow-prompts/flows/`
+- Use template files in `/devflow-prompts/templates/gen-`
+- Run `/devflow.0-rev-rules` to improve rules
+
+---
+
+**Version**: 4.0  
+**Last Updated**: 2026-01-17  
+**Status**: ✅ Production Ready
+
+### Changelog
+
+#### v4.0 (2026-01-17)
+
+- ✨ **NEW**: Enforced **Strict File Path Input** for all 13 prompts
+  - Removed "Direct Input" option to streamline workflow
+  - **Filename MUST contain Task ID** (e.g., `FEAT-001`) for correct output generation
+- 📝 Updated all documentation to reflect clean file-based workflow
+- 🎯 Consolidated usage patterns for better consistency
+
+#### v3.2 (Previous)
+
+- Initial DevFlow Kit release with 13 prompts
+- Template-based workflow system
+- Multi-language support