prompt-suite 1.0.0 → 1.0.2

package/README.md

@@ -1,54 +1,66 @@
-# Prompt Suite - Development Workflow System
+# Prompt Suite - Development Workflow Automation
 
-DevFlow (Development Flow) is a comprehensive prompt system that automates the software development process from raw customer request → production-ready code + tests.
+**Prompt Suite** is a comprehensive prompt system that automates the software development process from raw customer request → production-ready code + tests.
 
 ## 📦 Installation
 
 To install Prompt Suite in your project:
 
 ```bash
-# Initialize in your project root
+# Install the package
 npm install prompt-suite -D
-npx prompt-suite publish
+
+# Initialize and setup
+npx prompt-suite init
 ```
 
-> **⚠️ Important:** Run this command on your **local machine** (where your IDE is installed), **NOT** inside a Docker container.
-> The setup script needs to modify your local IDE settings (VSCode snippets, Antigravity workflows) which are not accessible from inside a container.
+During initialization, you'll be prompted to select your IDE:
+
+- **VSCode / Cursor** - Prompts will be installed to `.github/prompts/`
+- **Antigravity** - Prompts will be installed to `.agent/workflows/`
+- **Skip** - Manual setup later
 
-This will create a `prompt-suite/` directory in your project with all necessary prompts, scripts, and rules.
+The installer will:
 
-Once installed, run the specific setup script for your IDE (see Quick Start below).
+1. Copy resources (rules, scripts, templates) to `prompt-suite/` folder
+2. Copy prompt files directly to your IDE's prompts directory
+3. Update IDE settings (VSCode only)
+
+> **⚠️ Important:** Run this command on your **local machine** (where your IDE is installed), **NOT** inside a Docker container.
 
 ---
 
 ## 🔄 Updating / Upgrading
 
-When you upgrade `prompt-suite` to a newer version and run `npx prompt-suite init`, the script will handle your existing files intelligently:
+When you upgrade `prompt-suite` to a newer version:
 
-1. **Safe Mode (Default)**:
-   It will **skip** any files that you have modified, ensuring your customizations are preserved.
+### Safe Mode (Default):
 
-   ```bash
-   npx prompt-suite publish
-   ```
+Preserves your customizations by skipping modified files:
 
-2. **Force Overwrite**:
-   Use `--force` if you want to **reset** everything to the latest defaults (warning: this will overwrite your changes).
+```bash
+npx prompt-suite init
+```
+
+### Force Overwrite:
 
-   ```bash
-   npx prompt-suite publish --force
-   ```
+Resets everything to latest defaults (⚠️ overwrites your changes):
 
-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.
+```bash
+npx prompt-suite init --force
+```
+
+### Conflict Resolution:
+
+If a file exists but differs from the new version, a `.new` file will be created (e.g., `README.md.new`) for manual comparison and merging.
 
 ---
 
 ## 📋 Overview
 
-**Prefix**: `/ps.` - Distinguishes from other workflow systems
+**Prefix**: `/ps.` - All Prompt Suite commands start with this prefix
 
-## 🎯 Complete Workflow (Step 0-6)
+## 🎯 Complete Workflow (6 Steps)
 
 ```
 [Step 0] Generate Coding Rules (One-time setup)
@@ -57,580 +69,222 @@ When you upgrade `prompt-suite` to a newer version and run `npx prompt-suite ini
     ↓
 [Step 2] Technical Design
     ↓
-[Step 3] Feature Code
+[Step 3] Feature Code (Patch)
     ↓
 [Step 4] Test Plan
     ↓
-[Step 5] Test Code
+[Step 5] Test Code (Patch)
     ↓
 [Step 6] Validate & Analyze
 ```
 
-## 🚀 Quick Start Guide
-
-### Prerequisites
+---
 
-### Setup for your IDE
+## 🚀 Quick Start
 
-Run the corresponding setup script to install prompts into your IDE:
+### 1. Install and Initialize
 
 ```bash
-# For Antigravity
-./prompt-suite/scripts/setup-ps-chat-antigravity.sh
-
-# For VSCode / Cursor
-./prompt-suite/scripts/setup-ps-chat-vscode.sh
+npm install prompt-suite -D
+npx prompt-suite init
 ```
 
-This will install all DevFlow prompts and enable autocomplete for `/ps.*` commands.
-
----
-
-## 📦 Output Summary - What Each Step Produces
-
-### Step 0: Generate Rules (One-time)
-
-**Output:** 10 markdown files
-**Location:** `/prompt-suite/rules/`
-**Action:** ✅ AI auto-creates files
-**Manual step:** ❌ None
-
----
-
-### Step 1: Requirement
+Select your IDE when prompted. Prompts will be automatically installed.
 
-**Output:** 1 markdown file (`{task-id}-requirement.md`)
-**Location:** `/prompt-suite/specs/{task-id}/`
-**Action:** ✅ AI auto-creates file
-**Manual step:** ❌ None
+### 2. Generate Coding Rules (One-time)
 
----
+```bash
+# Copy template
+cp prompt-suite/templates/gen-rule-template.txt my-rules.txt
 
-### Step 2: Design
+# Edit my-rules.txt with your stack info
+# Then generate rules:
+/ps.0-gen-rules my-rules.txt
+```
 
-**Output:** 1 markdown file (`{task-id}-design.md`)
-**Location:** `/prompt-suite/specs/{task-id}/`
-**Action:** ✅ AI auto-creates file
-**Manual step:** ❌ None
+### 3. Start Your First Feature
 
----
+```bash
+# Copy template
+cp prompt-suite/templates/gen-requirement-template.txt FEAT-001-request.txt
 
-### Step 3: Code ⚠️ (Manual Action Required)
+# Edit FEAT-001-request.txt with your feature request
+# Then generate requirement:
+/ps.1-gen-requirement FEAT-001-request.txt
 
-**Output:** 1 git patch file (`{task-id}-feature.patch`)
-**Location:** `/prompt-suite/specs/{task-id}/`
-**Action:** ⚠️ AI generates patch
-**Manual step:** ✅ **YOU must apply patch**
+# Generate design:
+/ps.2-gen-design prompt-suite/specs/FEAT-001/FEAT-001-requirement.md
 
-**⚠️ Warning:** AI only creates the patch file. You must manually run `git apply` to create the actual source code files in your project.
+# Generate code:
+/ps.3-gen-code prompt-suite/specs/FEAT-001/FEAT-001-design.md
 
-```bash
-cd /path/to/your/project
-git apply --check prompt-suite/specs/FEAT-001/FEAT-001-feature.patch
+# Apply the patch:
 git apply prompt-suite/specs/FEAT-001/FEAT-001-feature.patch
-git status
 ```
 
 ---
 
-### Step 4: Test Plan
+## 📦 What Gets Installed
 
-**Output:** 1 markdown file (`{task-id}-test.md`)
-**Location:** `/prompt-suite/specs/{task-id}/`
-**Action:** ✅ AI auto-creates file
-**Manual step:** ❌ None
+### In `prompt-suite/` folder:
 
----
-
-### Step 5: Test Code ⚠️ (Manual Action Required)
-
-**Output:** 1 git patch file (`{task-id}-test.patch`)
-**Location:** `/prompt-suite/specs/{task-id}/`
-**Action:** ⚠️ AI generates patch
-**Manual step:** ✅ **YOU must apply patch**
+- `rules/` - Generated coding rules (from Step 0)
+- `scripts/` - Setup scripts for manual IDE configuration
+- `templates/` - Input templates for commands
+- `specs/` - Generated specifications and patches
+- `README.md` - This documentation
 
-**⚠️ Warning:** AI only creates the patch file. You must manually run `git apply` to create the actual test files in your project.
+### In your IDE:
 
-```bash
-cd /path/to/your/project
-git apply --check prompt-suite/specs/FEAT-001/FEAT-001-test.patch
-git apply prompt-suite/specs/FEAT-001/FEAT-001-test.patch
-./vendor/bin/phpunit  # Run tests
-```
+- **VSCode/Cursor**: `.github/prompts/*.md` - All prompt files
+- **Antigravity**: `.agent/workflows/*.md` - All prompt files
 
 ---
 
-### Step 6: Analyze
-
-**Output:** Analysis report (inline text)
-**Location:** Inline in AI response
-**Action:** ℹ️ AI displays report
-**Manual step:** ❌ None (read only)
-
----
+## 📚 Available Commands
 
-## 📚 Step-by-Step Guide
+### Step 0: Coding Rules (One-time Setup)
 
-### Step 0: Generate Coding Rules (One-time Setup)
-
-**Purpose**: Create project-specific coding standards and quality checklists.
-
-#### Commands:
-
-| Command           | Purpose                                  |
-| ----------------- | ---------------------------------------- |
-| `/ps.0-gen-rules` | Generate coding rules for specific steps |
-| `/ps.0-rev-rules` | Review and improve generated rules       |
-
-#### Usage Example:
-
-**Input Type: File Path (Required)**
-
-1. Copy template file:
-
-```bash
-cp prompt-suite/templates/gen-rule-template.txt my-rules-input.txt
-```
+| Command           | Purpose                                |
+| ----------------- | -------------------------------------- |
+| `/ps.0-gen-rules` | Generate coding rules for your project |
+| `/ps.0-rev-rules` | Review and improve generated rules     |
 
-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
-/ps.0-gen-rules my-rules-input.txt
-```
-
-**Output**: 10 rule files in `/prompt-suite/rules/`:
-
-**Output**: 10 rule files in `/prompt-suite/rules/`:
-
-```
-/prompt-suite/rules/
-├── df.1-gen-requirement.rule.md
-├── df.1-rev-requirement.rule.md
-├── df.2-gen-design.rule.md
-├── df.2-rev-design.rule.md
-├── df.3-gen-code.rule.md
-├── df.3-rev-code.rule.md
-├── df.4-gen-test-plan.rule.md
-├── df.4-rev-test-plan.rule.md
-├── df.5-gen-test-code.rule.md
-└── df.5-rev-test-code.rule.md
-```
-
-#### Generate Rules for Specific Step:
-
-```bash
-# Generate both gen + rev rules for Step 1 (Requirement)
-/ps.0-gen-rules
-
-Step: 1
-Stack: Laravel + Vue.js
-Architecture: Clean Architecture
-
-# → Generates: df.1-gen-requirement.rule.md, df.1-rev-requirement.rule.md
-```
+**Output**: 10 rule files in `prompt-suite/rules/`
 
-#### Generate Individual Rule File (Granular):
+### Step 1: Requirements
 
-**Use cases:**
+| Command                 | Purpose                                      |
+| ----------------------- | -------------------------------------------- |
+| `/ps.1-gen-requirement` | Convert raw request → structured requirement |
+| `/ps.1-rev-requirement` | Review requirement for completeness          |
 
-- Fix/iterate on a specific rule file
-- Regenerate only gen-rule or rev-rule
+**Output**: `{task-id}-requirement.md`
 
-```bash
-# Generate ONLY gen-rule for Step 3 (Code)
-/ps.0-gen-rules
+### Step 2: Technical Design
 
-Step: 3-gen
-Stack: Laravel + Vue.js
-Architecture: Clean Architecture
+| Command            | Purpose                                  |
+| ------------------ | ---------------------------------------- |
+| `/ps.2-gen-design` | Create technical design from requirement |
+| `/ps.2-rev-design` | Review design for implementability       |
 
-# → Generates: df.3-gen-code.rule.md (only)
+**Output**: `{task-id}-design.md`
 
-# Generate ONLY rev-rule for Step 2 (Design)
-/ps.0-gen-rules
+### Step 3: Feature Code ⚠️
 
-Step: 2-rev
-Stack: Laravel + Vue.js
-Architecture: Clean Architecture
+| Command          | Purpose                           |
+| ---------------- | --------------------------------- |
+| `/ps.3-gen-code` | Generate code patch from design   |
+| `/ps.3-rev-code` | Review code quality & correctness |
 
-# → Generates: df.2-rev-design.rule.md (only)
-```
+**Output**: `{task-id}-feature.patch` (⚠️ Manual `git apply` required)
 
-**Available options:**
+### Step 4: Test Plan
 
-- `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
+| Command               | Purpose                      |
+| --------------------- | ---------------------------- |
+| `/ps.4-gen-test-plan` | Create test plan from design |
+| `/ps.4-rev-test-plan` | Review test coverage         |
 
-#### Review Generated Rules:
+**Output**: `{task-id}-test.md`
 
-```bash
-# Option 1: Review all rules in directory (Recommended)
-/ps.0-rev-rules /prompt-suite/rules/
+### Step 5: Test Code ⚠️
 
-# Option 2: Review specific file
-/ps.0-rev-rules /prompt-suite/rules/ps.1-gen-requirement.rule.md
-```
+| Command               | Purpose                                 |
+| --------------------- | --------------------------------------- |
+| `/ps.5-gen-test-code` | Generate test code patch from test plan |
+| `/ps.5-rev-test-code` | Review test quality                     |
 
-**Review specific step or individual file:**
+**Output**: `{task-id}-test.patch` (⚠️ Manual `git apply` required)
 
-```bash
-# Review both gen + rev for Step 3 (Code)
-/ps.0-rev-rules /prompt-suite/rules/ps.3-gen-code.rule.md /prompt-suite/rules/ps.3-rev-code.rule.md
+### Step 6: Analysis
 
-# Review ONLY gen-rule for Step 2 (Design)
-/ps.0-rev-rules /prompt-suite/rules/ps.2-gen-design.rule.md
-```
-
-**Available options:**
+| Command         | Purpose                                    |
+| --------------- | ------------------------------------------ |
+| `/ps.6-analyze` | Validate entire flow, find inconsistencies |
 
-- `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
+**Output**: Analysis report (inline)
 
 ---
 
-### Step 1: Requirement Document
-
-**Purpose**: Convert raw customer request into structured, testable requirement document.
-
-#### Commands:
-
-| Command                 | Purpose                               |
-| ----------------------- | ------------------------------------- |
-| `/ps.1-gen-requirement` | Convert raw request → requirement doc |
-| `/ps.1-rev-requirement` | Review requirement for completeness   |
+## 💡 Usage Tips
 
-#### Usage Example:
+### Input Format
 
-**Input Type: File Path (Required)**
-
-1. Copy template:
-
-```bash
-cp prompt-suite/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:
+All commands require **file path input** (not direct text):
 
 ```bash
+# ✅ Correct - file path
 /ps.1-gen-requirement FEAT-001-request.txt
-```
-
-**Output**: `/prompt-suite/specs/FEAT-001/FEAT-001-requirement.md`
-
-#### Review Requirement:
-
-```bash
-/ps.1-rev-requirement /prompt-suite/specs/FEAT-001/FEAT-001-requirement.md
-```
-
----
-
-### Step 2: Technical Design
-
-**Purpose**: Create implementable technical design from requirement.
 
-#### Commands:
-
-| Command            | Purpose                             |
-| ------------------ | ----------------------------------- |
-| `/ps.2-gen-design` | Create tech design from requirement |
-| `/ps.2-rev-design` | Review design for implementability  |
-
-#### Usage Example:
-
-```bash
-/ps.2-gen-design /prompt-suite/specs/FEAT-001/FEAT-001-requirement.md
+# ❌ Wrong - direct text not supported
+/ps.1-gen-requirement "I want a login feature"
 ```
 
-**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**.
+### Task ID Requirement
 
-````
-
-**Output**: `/prompt-suite/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:
+Filenames **must contain a Task ID** (e.g., `FEAT-001`, `TASK-123`):
 
 ```bash
-/ps.2-rev-design /prompt-suite/specs/FEAT-001/FEAT-001-design.md
-````
-
----
-
-### Step 3: Feature Code
+# ✅ Valid filenames
+/ps.1-gen-requirement customer-request-FEAT-001.txt
+/ps.2-gen-design TASK-123-spec.md
 
-**Purpose**: Generate production-ready code from technical design.
-
-#### Commands:
-
-| Command          | Purpose                           |
-| ---------------- | --------------------------------- |
-| `/ps.3-gen-code` | Generate code from tech design    |
-| `/ps.3-rev-code` | Review code quality & correctness |
-
-#### Usage Example:
-
-```bash
-/ps.3-gen-code /prompt-suite/specs/FEAT-001/FEAT-001-design.md
+# ❌ Invalid - no Task ID
+/ps.1-gen-requirement request.txt
 ```
 
-**Note**: In `UPDATE` mode, AI will:
-
-- Read existing files to match style.
-- Only generate minimal diffs to implementing the change.
-- Protect legacy behavior.
+### Applying Patches
 
-````
-
-**Output**: Git unified diff (patch) - `/prompt-suite/specs/FEAT-001/FEAT-001-feature.patch`
-
-#### ⚠️ Apply Patch (Manual Step Required):
-
-**AI generates the patch, but YOU must manually apply it:**
+Steps 3 and 5 generate patch files that you must manually apply:
 
 ```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)
+# Check if patch can be applied
 git apply --check prompt-suite/specs/FEAT-001/FEAT-001-feature.patch
 
-# Step 3: If no errors, apply the patch
+# Apply the patch
 git apply prompt-suite/specs/FEAT-001/FEAT-001-feature.patch
 
-# Step 4: Verify what files were created/modified
+# Review and commit
 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 `/ps.3-rev-code` to get corrected patch
-
----
-
-### Step 4: Test Plan
-
-**Purpose**: Create comprehensive test plan covering unit/integration/E2E tests.
-
-#### Commands:
-
-| Command               | Purpose                             |
-| --------------------- | ----------------------------------- |
-| `/ps.4-gen-test-plan` | Create test plan from tech design   |
-| `/ps.4-rev-test-plan` | Review test coverage & traceability |
-
-#### Usage Example:
-
-```bash
-/ps.4-gen-test-plan /prompt-suite/specs/FEAT-001/FEAT-001-design.md
+git commit -m "feat: implement feature FEAT-001"
 ```
 
-**Output**: `/prompt-suite/specs/FEAT-001/FEAT-001-test.md` containing:
+### Flexible Workflow
 
-- Test level strategy (unit/integration/E2E)
-- Detailed test cases
-- Negative & edge cases
-- Mock/stub strategy
-- Test data requirements
+You don't need to run all steps. Adapt based on complexity:
 
-#### Review Test Plan:
+**Small task (bug fix)**:
 
-```bash
-/ps.4-rev-test-plan /prompt-suite/specs/FEAT-001/FEAT-001-design.md /prompt-suite/specs/FEAT-001/FEAT-001-test.md
 ```
-
----
-
-### Step 5: Test Code
-
-**Purpose**: Generate test code from test plan.
-
-#### Commands:
-
-| Command               | Purpose                           |
-| --------------------- | --------------------------------- |
-| `/ps.5-gen-test-code` | Generate test code from test plan |
-| `/ps.5-rev-test-code` | Review test quality & reliability |
-
-#### Usage Example:
-
-```bash
-/ps.5-gen-test-code /prompt-suite/specs/FEAT-001/FEAT-001-test.md
+/ps.1-gen-requirement → /ps.2-gen-design → /ps.3-gen-code
 ```
 
-**Output**: Git unified diff (patch) - `/prompt-suite/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 prompt-suite/specs/FEAT-001/FEAT-001-test.patch
-
-# Step 3: If no errors, apply the patch
-git apply prompt-suite/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
+**Medium task (new feature)**:
 
-# 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 `/ps.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                         |
-| --------------- | ------------------------------- |
-| `/ps.6-analyze` | Validate entire flow, find gaps |
-
-#### Usage Example:
-
-```bash
-/ps.6-analyze \
-  /prompt-suite/specs/FEAT-001/FEAT-001-requirement.md \
-  /prompt-suite/specs/FEAT-001/FEAT-001-design.md \
-  /prompt-suite/specs/FEAT-001/FEAT-001-test.md
+/ps.1-gen-requirement → /ps.1-rev-requirement
+→ /ps.2-gen-design → /ps.2-rev-design
+→ /ps.3-gen-code → /ps.5-gen-test-code
 ```
 
-**Output**: Analysis report with:
-
-- Alignment check (Requirement ↔ Design ↔ Code ↔ Test)
-- Inconsistencies found (P0/P1/P2)
-- Coverage gaps
-- Recommendations (prioritized)
-
----
-
-## 📁 File Structure
+**Large task (critical feature)**:
 
 ```
-project/
-├── prompt-suite/
-│   ├── README.md                    # This file
-│   ├── gen-chat.sh           # Main setup script
-│   │
-│   ├── scripts/                     # IDE-specific setup scripts
-│   │   ├── setup-ps-chat-antigravity.sh
-│   │   ├── setup-ps-chat-cursor.sh
-│   │   └── setup-ps-chat-vscode.sh
-│   │
-│   ├── flows/                       # Prompt definitions
-│   │   ├── df.0-gen-rules.prompt.md
-│   │   ├── df.1-gen-requirement.prompt.md
-│   │   └── ...
-│   │
-│   ├── templates/                   # Template files for input
-│   │   ├── gen-rule-template.txt       # Template for /ps.0-gen-rules
-│   │   └── gen-requirement-template.txt # Template for /ps.1-gen-requirement
-│   │
-│   ├── rules/                       # Coding rules (generated by Step 0)
-│   │   ├── df.1-gen-requirement.rule.md
-│   │   ├── df.1-rev-requirement.rule.md
-│   │   ├── df.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)
-│       ├── df.0-gen-rules.prompt.md
-│       ├── df.1-gen-requirement.prompt.md
-│       └── ...
-│
-└── src/                             # Source code (after applying patches)
+Full workflow (Steps 0-6)
 ```
 
 ---
 
 ## 🌍 Multi-Language Support
 
-DevFlow supports multiple languages. Technical terms (API, HTTP, JWT, etc.) always stay in English.
+Supported languages: `en` (English), `vi` (Vietnamese), `ja` (Japanese), `ko` (Korean)
 
-### Supported Languages:
+Technical terms (API, HTTP, JWT, etc.) always stay in English.
 
-- `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:**
+**Example**:
 
 ```text
 Task ID: FEAT-001
@@ -640,271 +294,138 @@ 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        | `/ps.0-gen-rules`       |
-| Have raw customer request   | `/ps.1-gen-requirement` |
-| Requirement unclear         | `/ps.1-rev-requirement` |
-| Need technical design       | `/ps.2-gen-design`      |
-| Design has issues           | `/ps.2-rev-design`      |
-| Need to generate code       | `/ps.3-gen-code`        |
-| Code has bugs               | `/ps.3-rev-code`        |
-| Need test plan              | `/ps.4-gen-test-plan`   |
-| Test coverage insufficient  | `/ps.4-rev-test-plan`   |
-| Need to generate tests      | `/ps.5-gen-test-code`   |
-| Tests have issues           | `/ps.5-rev-test-code`   |
-| Need to validate everything | `/ps.6-analyze`         |
-
-### Flexible Workflow
-
-Not required to run all commands. Adapt based on task complexity:
-
-**Small task (bug fix)**:
-
-```
-/ps.1-gen-requirement → /ps.2-gen-design → /ps.3-gen-code
-```
-
-**Medium task (new feature)**:
-
-```
-/ps.1-gen-requirement → /ps.1-rev-requirement
-→ /ps.2-gen-design → /ps.2-rev-design
-→ /ps.3-gen-code → /ps.5-gen-test-code
-```
-
-**Large task (critical feature)**:
+## 📁 File Structure
 
 ```
-Full workflow (Step 0-6)
+project/
+├── prompt-suite/                    # Installed resources
+│   ├── rules/                       # Generated coding rules
+│   │   ├── ps.1-gen-requirement.rule.md
+│   │   ├── ps.1-rev-requirement.rule.md
+│   │   └── ...
+│   ├── scripts/                     # Manual setup scripts
+│   │   ├── setup-ps-chat-vscode.sh
+│   │   └── setup-ps-chat-antigravity.sh
+│   ├── templates/                   # Input templates
+│   │   ├── gen-rule-template.txt
+│   │   └── gen-requirement-template.txt
+│   ├── specs/                       # Generated specs & patches
+│   │   └── FEAT-001/
+│   │       ├── FEAT-001-requirement.md
+│   │       ├── FEAT-001-design.md
+│   │       ├── FEAT-001-test.md
+│   │       ├── FEAT-001-feature.patch
+│   │       └── FEAT-001-test.patch
+│   └── README.md
+│
+├── .github/prompts/                 # VSCode prompts (auto-installed)
+│   ├── ps.0-gen-rules.prompt.md
+│   ├── ps.1-gen-requirement.prompt.md
+│   └── ...
+│
+├── .agent/workflows/                # Antigravity prompts (auto-installed)
+│   ├── ps.0-gen-rules.prompt.md
+│   ├── ps.1-gen-requirement.prompt.md
+│   └── ...
+│
+└── src/                             # Your source code
 ```
 
-### 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 `/prompt-suite/templates/gen-`
-2. Fill in your information
-3. Save with descriptive name
-4. Pass to command: `/ps.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., `/ps.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 `/prompt-suite`)
-- ✅ **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
+## 🔧 Manual IDE Setup
 
-**Examples:**
+If you skipped IDE selection during `init`, you can run setup scripts manually:
 
 ```bash
-# Single file input - filename MUST contain Task ID
-/ps.1-gen-requirement ~/Desktop/FEAT-001-request.txt
-/ps.2-gen-design /Users/phongle/Documents/FEAT-001-v2.md
-
-# Multiple files input
-/ps.3-rev-code /path/to/FEAT-001-design.md /path/to/FEAT-001.patch
-/ps.4-rev-test-plan /path/to/FEAT-001-design.md /path/to/FEAT-001-test.md
+# For VSCode/Cursor
+bash prompt-suite/scripts/setup-ps-chat-vscode.sh
 
-# Directory input (e.g. for bulk rule review)
-/ps.0-rev-rules /prompt-suite/rules/
+# For Antigravity
+bash prompt-suite/scripts/setup-ps-chat-antigravity.sh
 ```
 
-# Valid filenames (contain Task ID)
-
-/ps.1-gen-requirement /path/to/customer-request-FEAT-001.txt
-/ps.2-gen-design /path/to/FEAT-001-design-v2.md
-/ps.3-gen-code /path/to/TASK-123-spec.md
-
-````
-
-
+---
 
-##  Complete Example Walkthrough
+## 📖 Complete Example
 
 ### Scenario: User Login with Rate Limiting
 
-#### Step 0: Setup (One-time)
+#### Step 0: Generate Rules (One-time)
 
 ```bash
-# Copy template
-cp prompt-suite/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
-/ps.0-gen-rules my-project-rules.txt
-````
+cp prompt-suite/templates/gen-rule-template.txt my-rules.txt
+# Edit: Step: all, Stack: Laravel + Vue.js, Architecture: Clean Architecture
+/ps.0-gen-rules my-rules.txt
+```
 
 #### Step 1: Generate Requirement
 
 ```bash
-# Copy template
 cp prompt-suite/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
+# Edit: Task ID: FEAT-001, Raw Request: User login with email/password...
 /ps.1-gen-requirement FEAT-001-request.txt
-```
-
-**Review**:
-
-```bash
-/ps.1-rev-requirement /prompt-suite/specs/FEAT-001/FEAT-001-requirement.md
+/ps.1-rev-requirement prompt-suite/specs/FEAT-001/FEAT-001-requirement.md
 ```
 
 #### Step 2: Generate Design
 
 ```bash
-/ps.2-gen-design /prompt-suite/specs/FEAT-001/FEAT-001-requirement.md
-```
-
-**Review**:
-
-```bash
-/ps.2-rev-design /prompt-suite/specs/FEAT-001/FEAT-001-design.md
+/ps.2-gen-design prompt-suite/specs/FEAT-001/FEAT-001-requirement.md
+/ps.2-rev-design prompt-suite/specs/FEAT-001/FEAT-001-design.md
 ```
 
 #### Step 3: Generate Code
 
 ```bash
-/ps.3-gen-code /prompt-suite/specs/FEAT-001/FEAT-001-design.md
-# Apply patch: git apply prompt-suite/specs/FEAT-001/FEAT-001-feature.patch
+/ps.3-gen-code prompt-suite/specs/FEAT-001/FEAT-001-design.md
+
+# Apply patch
+git apply --check prompt-suite/specs/FEAT-001/FEAT-001-feature.patch
+git apply prompt-suite/specs/FEAT-001/FEAT-001-feature.patch
+git add .
+git commit -m "feat: user login with rate limiting (FEAT-001)"
 ```
 
 #### Step 4: Generate Test Plan
 
 ```bash
-/ps.4-gen-test-plan /prompt-suite/specs/FEAT-001/FEAT-001-design.md
+/ps.4-gen-test-plan prompt-suite/specs/FEAT-001/FEAT-001-design.md
+/ps.4-rev-test-plan prompt-suite/specs/FEAT-001/FEAT-001-design.md prompt-suite/specs/FEAT-001/FEAT-001-test.md
 ```
 
 #### Step 5: Generate Test Code
 
 ```bash
-/ps.5-gen-test-code /prompt-suite/specs/FEAT-001/FEAT-001-test.md
-# Apply patch: git apply prompt-suite/specs/FEAT-001/FEAT-001-test.patch
+/ps.5-gen-test-code prompt-suite/specs/FEAT-001/FEAT-001-test.md
+
+# Apply test patch
+git apply --check prompt-suite/specs/FEAT-001/FEAT-001-test.patch
+git apply prompt-suite/specs/FEAT-001/FEAT-001-test.patch
+./vendor/bin/phpunit
+git add .
+git commit -m "test: add tests for login feature (FEAT-001)"
 ```
 
 #### Step 6: Validate
 
 ```bash
 /ps.6-analyze \
-  /prompt-suite/specs/FEAT-001/FEAT-001-requirement.md \
-  /prompt-suite/specs/FEAT-001/FEAT-001-design.md \
-  /prompt-suite/specs/FEAT-001/FEAT-001-test.md
+  prompt-suite/specs/FEAT-001/FEAT-001-requirement.md \
+  prompt-suite/specs/FEAT-001/FEAT-001-design.md \
+  prompt-suite/specs/FEAT-001/FEAT-001-test.md
 ```
 
 ---
 
-## 🎯 General Principles
+## 🤝 Contributing
 
-### ✅ DO
+Issues and pull requests are welcome!
 
-- 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
+## 📄 License
 
-### ❌ 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
+ISC
 
 ---
 
-## 🔧 Troubleshooting
-
-### Autocomplete not working?
-
-1. **Reload IDE**:
-   - Antigravity: Restart
-   - VSCode/Cursor: `Cmd+Shift+P` → "Developer: Reload Window"
-
-2. **Re-run setup**:
-
-   ```bash
-   ./prompt-suite/gen-chat.sh antigravity
-   ```
-
-3. **Check files**:
-
-   ```bash
-   ls .agent/workflows/ps.*.md
-   ```
-
-### Commands not appearing?
-
-- Make sure you ran setup for correct IDE
-- Check that files are in correct location
-- Verify file format (must have `# /ps.X-xxx` heading)
-
----
-
-## 📞 Support
-
-For issues or questions:
-
-- Check rule files in `/prompt-suite/rules/`
-- Review prompt files in `/prompt-suite/flows/`
-- Use template files in `/prompt-suite/templates/gen-`
-- Run `/ps.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
+**Made with ❤️ by Phong Le**

package/bin/cli.js

@@ -17,7 +17,7 @@ const sourceRoot = path.join(__dirname, '..');
 const targetRoot = path.join(process.cwd(), 'prompt-suite');
 
 // Exclude 'flows' - will be copied directly to IDE prompts folder
-const itemsToCopy = ['rules', 'scripts', 'templates', 'README.md'];
+const itemsToCopy = ['rules', 'scripts', 'specs', 'templates', 'README.md'];
 
 console.log(`\n🚀 Initializing Prompt Suite...`);
 console.log(`Source: ${sourceRoot}`);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "prompt-suite",
-  "version": "1.0.0",
+  "version": "1.0.2",
   "description": "Prompt Suite - Prompt Engineering & Workflow Automation",
   "main": "index.js",
   "bin": {

package/{templates/gen-requirement-template.txt → specs/FEAT-000/gen-requirement-template.md}

@@ -18,9 +18,9 @@ Example (Update Feature):
 Task ID: FEAT-002
 Language: vi
 Task Mode: UPDATE
-Existing Logic/Code: 
+Existing Logic/Code:
 function login(email, password) {
-  // checked password
-  return true;
+// checked password
+return true;
 }
 Raw Request: Cập nhật hàm login để thêm logic kiểm tra captcha trước khi check password. Nếu sai captcha trả về lỗi 400.

package/raws/changename.md

@@ -1,7 +0,0 @@
-# Yêu cầu thay đổi tên dự án và prefix
-
-Thực hiện các thay đổi sau cho hệ thống prompt:
-
-1.  **Đổi tên dự án**: Cập nhật tên thư mục hoặc tên gói thành `devflow-prompts`.
-2.  **Đổi Prefix Prompt**: Cập nhật tiền tố (prefix) cho các lệnh prompt từ tên cũ sang `devflow`.
-    - Ví dụ: đổi thành `df.1-gen-requirement`, `df.2-gen-design`, v.v.

package/raws/my-project-rules.txt

@@ -1,7 +0,0 @@
-Step: all
-Stack: Laravel (Backend) + Inertia & Vue.js (Frontend)
-Architecture: Read this source code to understand the architecture
-Coding Rules: Read this source code to understand the coding rules
-Team: 5 developers, mid-level experience
-Constraints: Must support 10k concurrent users
-Language: en