proagents 1.5.0 → 1.6.0

package/{proagents → .proagents}/.cursorrules

@@ -16,16 +16,16 @@ This project uses ProAgents workflow framework.
 
 ## Full Command Reference
 
-For complete command list, see: `./proagents/AI_INSTRUCTIONS.md`
+For complete command list, see: `./.proagents/AI_INSTRUCTIONS.md`
 
 ## On `pa:` Command
 
-1. Read the corresponding file from `./proagents/prompts/` or `./proagents/workflow-modes/`
+1. Read the corresponding file from `./.proagents/prompts/` or `./.proagents/workflow-modes/`
 2. Follow the workflow instructions
-3. Use project config from `./proagents/proagents.config.yaml`
+3. Use project config from `./.proagents/proagents.config.yaml`
 
 ## Key Files
 
-- `./proagents/AI_INSTRUCTIONS.md` - Complete command reference
-- `./proagents/WORKFLOW.md` - Full 10-phase workflow
-- `./proagents/prompts/` - Phase-specific prompts
+- `./.proagents/AI_INSTRUCTIONS.md` - Complete command reference
+- `./.proagents/WORKFLOW.md` - Full 10-phase workflow
+- `./.proagents/prompts/` - Phase-specific prompts

package/{proagents → .proagents}/.github/copilot-instructions.md

@@ -16,16 +16,16 @@ This project uses ProAgents workflow framework.
 
 ## Full Command Reference
 
-For complete command list, see: `./proagents/AI_INSTRUCTIONS.md`
+For complete command list, see: `./.proagents/AI_INSTRUCTIONS.md`
 
 ## On `pa:` Command
 
-1. Read the corresponding file from `./proagents/prompts/` or `./proagents/workflow-modes/`
+1. Read the corresponding file from `./.proagents/prompts/` or `./.proagents/workflow-modes/`
 2. Follow the workflow instructions
-3. Use project config from `./proagents/proagents.config.yaml`
+3. Use project config from `./.proagents/proagents.config.yaml`
 
 ## Key Files
 
-- `./proagents/AI_INSTRUCTIONS.md` - Complete command reference
-- `./proagents/WORKFLOW.md` - Full 10-phase workflow
-- `./proagents/prompts/` - Phase-specific prompts
+- `./.proagents/AI_INSTRUCTIONS.md` - Complete command reference
+- `./.proagents/WORKFLOW.md` - Full 10-phase workflow
+- `./.proagents/prompts/` - Phase-specific prompts

package/{proagents → .proagents}/.windsurfrules

@@ -16,16 +16,16 @@ This project uses ProAgents - an AI-agnostic development workflow framework.
 
 ## Full Command Reference
 
-For complete command list, see: `./proagents/AI_INSTRUCTIONS.md`
+For complete command list, see: `./.proagents/AI_INSTRUCTIONS.md`
 
 ## On `pa:` Command
 
-1. Read the corresponding file from `./proagents/prompts/` or `./proagents/workflow-modes/`
+1. Read the corresponding file from `./.proagents/prompts/` or `./.proagents/workflow-modes/`
 2. Follow the workflow instructions
-3. Use project config from `./proagents/proagents.config.yaml`
+3. Use project config from `./.proagents/proagents.config.yaml`
 
 ## Key Files
 
-- `./proagents/AI_INSTRUCTIONS.md` - Complete command reference
-- `./proagents/WORKFLOW.md` - Full 10-phase workflow
-- `./proagents/prompts/` - Phase-specific prompts
+- `./.proagents/AI_INSTRUCTIONS.md` - Complete command reference
+- `./.proagents/WORKFLOW.md` - Full 10-phase workflow
+- `./.proagents/prompts/` - Phase-specific prompts

package/{proagents → .proagents}/AI_INSTRUCTIONS.md

@@ -9,32 +9,32 @@ This project uses ProAgents - an AI-agnostic development workflow framework.
 ### Before executing ANY `pa:` command:
 
 1. **Read fresh state from files** - Never rely on previous knowledge
-2. **Read project context** - Read `./proagents/context.md` for persistent project knowledge
-3. **Check the activity log** - Read `./proagents/activity.log` to see recent AI actions
+2. **Read project context** - Read `./.proagents/context.md` for persistent project knowledge
+3. **Check the activity log** - Read `./.proagents/activity.log` to see recent AI actions
 4. **Key files to check:**
-   - `./proagents/context.md` - Persistent project context (READ FIRST!)
-   - `./proagents/activity.log` - Recent AI activity
-   - `./proagents/watchlist.yaml` - Files requiring confirmation before changes
-   - `./proagents/proagents.config.yaml` - Project and platform config
-   - `./proagents/active-features/` - Active feature status
+   - `./.proagents/context.md` - Persistent project context (READ FIRST!)
+   - `./.proagents/activity.log` - Recent AI activity
+   - `./.proagents/watchlist.yaml` - Files requiring confirmation before changes
+   - `./.proagents/proagents.config.yaml` - Project and platform config
+   - `./.proagents/active-features/` - Active feature status
    - `./CHANGELOG.md` - Recent changes
-   - `./proagents/feedback.md` - Past corrections and preferences (LEARN FROM THESE!)
+   - `./.proagents/feedback.md` - Past corrections and preferences (LEARN FROM THESE!)
 
 ### AI Feedback & Learning
 
-Before starting work, check `./proagents/feedback.md` for:
+Before starting work, check `./.proagents/feedback.md` for:
 - **Corrections**: Mistakes other AIs made - don't repeat them!
 - **Preferences**: How the user/team prefers things done
 - **Patterns**: What worked well in this project
 
 When you receive feedback or correction from the user:
-1. Log it in `./proagents/feedback.md` using `pa:feedback`
+1. Log it in `./.proagents/feedback.md` using `pa:feedback`
 2. Apply the learning to your current work
 3. Avoid making the same mistake again
 
 ### File Watch List
 
-Before modifying ANY file, check `./proagents/watchlist.yaml`:
+Before modifying ANY file, check `./.proagents/watchlist.yaml`:
 
 - **critical**: Ask user for confirmation before modifying
 - **review_required**: Warn user and explain changes before modifying
@@ -48,7 +48,7 @@ If a file matches a pattern, inform the user:
 
 ### After completing ANY `pa:` command:
 
-**ALWAYS log your activity** to `./proagents/activity.log`:
+**ALWAYS log your activity** to `./.proagents/activity.log`:
 
 ```
 [TIMESTAMP] [AI_PLATFORM:MODEL] [COMMAND] Description
@@ -68,7 +68,7 @@ Keep log entries concise (one line). Other AIs will read this to understand rece
 
 ### Command History
 
-Also log commands to `./proagents/history.log` with their results:
+Also log commands to `./.proagents/history.log` with their results:
 
 ```
 [TIMESTAMP] [AI:MODEL] COMMAND → RESULT
@@ -86,7 +86,7 @@ This helps track what commands were run and their outcomes.
 
 ### Lock File for Active Work
 
-When starting a major task (feature, large fix, refactoring), create a lock file at `./proagents/.lock`:
+When starting a major task (feature, large fix, refactoring), create a lock file at `./.proagents/.lock`:
 
 ```yaml
 locked_by: Claude        # Your AI platform
@@ -101,12 +101,12 @@ expires: 2024-03-06T17:10:00  # Auto-expires after 2 hours
 ```
 
 **Before starting major work:**
-1. Check if `./proagents/.lock` exists
+1. Check if `./.proagents/.lock` exists
 2. If locked by another AI, inform user: "Project is locked by [AI] working on [task]. Wait or ask user to override."
 3. If lock is expired (past `expires` time), you may delete it and proceed
 
 **After completing work:**
-1. Delete the `./proagents/.lock` file
+1. Delete the `./.proagents/.lock` file
 2. Log completion in activity.log
 
 ### Conflict Detection
@@ -145,7 +145,7 @@ This helps other AIs detect conflicts.
 
 ### Handoff Notes
 
-When ending a session or switching to another AI, create handoff notes at `./proagents/handoff.md`:
+When ending a session or switching to another AI, create handoff notes at `./.proagents/handoff.md`:
 
 **For `pa:handoff`** - Create/update handoff notes:
 ```markdown
@@ -190,7 +190,7 @@ Updated: 2024-03-06 15:30 by Claude (opus-4)
 
 ### Session Summary
 
-**For `pa:session-end`** - Generate and save a session summary to `./proagents/sessions/`:
+**For `pa:session-end`** - Generate and save a session summary to `./.proagents/sessions/`:
 
 ```markdown
 # Session Summary
@@ -222,7 +222,7 @@ AI: Claude (opus-4)
 3. Write integration tests
 ```
 
-Save to: `./proagents/sessions/YYYY-MM-DD-HHMMSS.md`
+Save to: `./.proagents/sessions/YYYY-MM-DD-HHMMSS.md`
 
 ## Command Recognition
 
@@ -280,31 +280,31 @@ Run individual phases of the development workflow:
 **How to execute Workflow Phase commands:**
 
 For `pa:analyze`:
-1. Read `./proagents/prompts/01-analysis.md` for analysis workflow
+1. Read `./.proagents/prompts/01-analysis.md` for analysis workflow
 2. Scan project structure, dependencies, patterns
-3. Cache results in `./proagents/cache/`
+3. Cache results in `./.proagents/cache/`
 4. Output analysis report
 
 For `pa:requirements`:
-1. Read `./proagents/prompts/02-requirements.md`
-2. If feature name provided, create `./proagents/active-features/feature-{name}/requirements.md`
+1. Read `./.proagents/prompts/02-requirements.md`
+2. If feature name provided, create `./.proagents/active-features/feature-{name}/requirements.md`
 3. Gather user stories, acceptance criteria, constraints
 4. Output requirements document
 
 For `pa:design`:
-1. Read `./proagents/prompts/03-ui-design.md`
+1. Read `./.proagents/prompts/03-ui-design.md`
 2. Check for design inputs (Figma, sketches, exports)
 3. Create component specifications
 4. Output design document
 
 For `pa:plan`:
-1. Read `./proagents/prompts/04-planning.md`
+1. Read `./.proagents/prompts/04-planning.md`
 2. Create implementation plan with task breakdown
 3. Identify dependencies and risks
-4. Save to `./proagents/active-features/feature-{name}/implementation-plan.md`
+4. Save to `./.proagents/active-features/feature-{name}/implementation-plan.md`
 
 For `pa:implement`:
-1. Read `./proagents/prompts/05-implementation.md`
+1. Read `./.proagents/prompts/05-implementation.md`
 2. Follow existing project patterns
 3. Implement code changes
 4. Log progress to activity.log
@@ -349,15 +349,15 @@ For `pa:implement`:
 **How to execute Navigation commands:**
 
 For `pa:next`:
-1. Read `./proagents/active-features/*/status.json` to find current feature
+1. Read `./.proagents/active-features/*/status.json` to find current feature
 2. Identify current phase from status
 3. Show what the next step/phase is
 4. Provide guidance for the next action
 
 For `pa:resume`:
-1. Read `./proagents/active-features/` to find paused features
+1. Read `./.proagents/active-features/` to find paused features
 2. Read feature's `status.json` for last phase and progress
-3. Read `./proagents/handoff.md` for context
+3. Read `./.proagents/handoff.md` for context
 4. Continue from where it was left off
 
 For `pa:skip`:
@@ -374,7 +374,7 @@ For `pa:back`:
 4. Reload context from previous phase
 
 For `pa:progress`:
-1. Read `./proagents/active-features/*/status.json`
+1. Read `./.proagents/active-features/*/status.json`
 2. Calculate percentage complete (current_phase / total_phases)
 3. Display visual progress bar:
    ```
@@ -399,24 +399,24 @@ For `pa:progress`:
 **How to execute Context & History commands:**
 
 For `pa:context`:
-1. Read `./proagents/context.md`
+1. Read `./.proagents/context.md`
 2. Display current project context summary
 3. Show last updated timestamp
 
 For `pa:diff`:
-1. Read `./proagents/activity.log` for last session timestamp
+1. Read `./.proagents/activity.log` for last session timestamp
 2. Run `git diff` from that point
 3. Summarize changes by file/module
 4. Highlight significant changes
 
 For `pa:history`:
-1. Read `./proagents/history.log`
+1. Read `./.proagents/history.log`
 2. Show recent commands with their results
 3. Format: `[timestamp] command → result`
 
 For `pa:checkpoint`:
 1. Create git commit with message "checkpoint: [description]"
-2. Save checkpoint info to `./proagents/checkpoints.json`:
+2. Save checkpoint info to `./.proagents/checkpoints.json`:
    ```json
    {
      "checkpoints": [
@@ -434,7 +434,7 @@ For `pa:checkpoint`:
 3. Log to activity.log
 
 For `pa:undo`:
-1. Read last action from `./proagents/activity.log`
+1. Read last action from `./.proagents/activity.log`
 2. If file changes, run `git checkout` to revert
 3. If multiple files, offer selective undo
 4. Update activity.log with undo entry
@@ -452,7 +452,7 @@ For `pa:undo`:
 **How to execute Sprint commands:**
 
 For `pa:sprint-start`:
-1. Create `./proagents/sprints/sprint-{number}.json`:
+1. Create `./.proagents/sprints/sprint-{number}.json`:
    ```json
    {
      "sprint_number": 1,
@@ -469,7 +469,7 @@ For `pa:sprint-start`:
 For `pa:sprint-end`:
 1. Read current sprint file
 2. Calculate metrics (completed features, velocity)
-3. Generate sprint summary → `./proagents/sprints/sprint-{n}-summary.md`
+3. Generate sprint summary → `./.proagents/sprints/sprint-{n}-summary.md`
 4. Archive sprint
 
 For `pa:estimate`:
@@ -479,7 +479,7 @@ For `pa:estimate`:
 4. Save estimate to feature status.json
 
 For `pa:velocity`:
-1. Read completed sprints from `./proagents/sprints/`
+1. Read completed sprints from `./.proagents/sprints/`
 2. Calculate average story points per sprint
 3. Show velocity chart/trend
 
@@ -539,7 +539,7 @@ For `pa:metrics`:
    - Cyclomatic complexity
    - Code duplication
    - Function/file sizes
-2. Save to `./proagents/metrics/latest.json`
+2. Save to `./.proagents/metrics/latest.json`
 3. Display summary with warnings for issues
 
 For `pa:coverage`:
@@ -585,8 +585,8 @@ For `pa:deps-security`:
 **How to execute Code Generation commands:**
 
 For `pa:generate-component`:
-1. Read project type and patterns from `./proagents/cache/patterns.json`
-2. Use template from `./proagents/scaffolding/` matching project type
+1. Read project type and patterns from `./.proagents/cache/patterns.json`
+2. Use template from `./.proagents/scaffolding/` matching project type
 3. Apply project naming conventions
 4. Create component file with:
    - Component code
@@ -666,7 +666,7 @@ For `pa:cleanup`:
 **How to execute Time Tracking commands:**
 
 For `pa:time-start`:
-1. Create/update `./proagents/time-tracking.json`:
+1. Create/update `./.proagents/time-tracking.json`:
    ```json
    {
      "current": {
@@ -862,8 +862,8 @@ For `pa:import`:
 4. Report what was imported
 
 For `pa:backup`:
-1. Create timestamped backup of entire proagents/ folder
-2. Save to `./proagents/backups/` or specified location
+1. Create timestamped backup of entire .proagents/ folder
+2. Save to `./.proagents/backups/` or specified location
 3. Compress if large
 4. Maintain rolling backups (keep last N)
 
@@ -880,7 +880,7 @@ For `pa:backup`:
 
 For `pa:learn`:
 1. Parse the pattern description
-2. Add to `./proagents/.learning/`:
+2. Add to `./.proagents/.learning/`:
    ```json
    {
      "pattern": "Always use React Query for API calls",
@@ -2046,7 +2046,7 @@ For `pa:test-mobile`:
    Run `pa:test-auto-fix` to automatically fix these issues.
    ```
 
-2. Generate detailed test report at `./proagents/test-reports/mobile-{timestamp}.md`
+2. Generate detailed test report at `./.proagents/test-reports/mobile-{timestamp}.md`
 
 For `pa:test-visual`:
 1. Take screenshots of all screens/components
@@ -2081,7 +2081,7 @@ For `pa:test-visual`:
    │ Bottom Margin   │ 16px         │ 12px         │
    └─────────────────┴──────────────┴──────────────┘
 
-   Screenshot saved: ./proagents/test-reports/visual/signup-diff.png
+   Screenshot saved: ./.proagents/test-reports/visual/signup-diff.png
 
    Screen: ProfileScreen
    ─────────────────────
@@ -2211,7 +2211,7 @@ For `pa:test-loop`:
    • src/screens/SignupScreen.styles.ts
    • src/types/auth.ts
 
-   Test report: ./proagents/test-reports/test-loop-{timestamp}.md
+   Test report: ./.proagents/test-reports/test-loop-{timestamp}.md
 
    Ready for commit? (y/n)
    ```
@@ -2310,7 +2310,7 @@ For `pa:compare-image "path"`:
       • Corner radius: sharper in app
       • Shadow: missing in app
 
-   Diff image saved: ./proagents/test-reports/visual/login-diff-overlay.png
+   Diff image saved: ./.proagents/test-reports/visual/login-diff-overlay.png
 
    ┌─────────────────────────────────────────────┐
    │ [Reference]        │ [App]        │ [Diff] │
@@ -2333,22 +2333,22 @@ For `pa:screenshot`:
 
    Capturing screenshots...
 
-   ✓ LoginScreen → ./proagents/screenshots/LoginScreen.png
-   ✓ SignupScreen → ./proagents/screenshots/SignupScreen.png
-   ✓ HomeScreen → ./proagents/screenshots/HomeScreen.png
-   ✓ ProfileScreen → ./proagents/screenshots/ProfileScreen.png
-   ✓ SettingsScreen → ./proagents/screenshots/SettingsScreen.png
-   ✓ NotificationsScreen → ./proagents/screenshots/NotificationsScreen.png
+   ✓ LoginScreen → ./.proagents/screenshots/LoginScreen.png
+   ✓ SignupScreen → ./.proagents/screenshots/SignupScreen.png
+   ✓ HomeScreen → ./.proagents/screenshots/HomeScreen.png
+   ✓ ProfileScreen → ./.proagents/screenshots/ProfileScreen.png
+   ✓ SettingsScreen → ./.proagents/screenshots/SettingsScreen.png
+   ✓ NotificationsScreen → ./.proagents/screenshots/NotificationsScreen.png
    ... (6 more)
 
    Component screenshots:
-   ✓ Button variants → ./proagents/screenshots/components/Button.png
-   ✓ Input variants → ./proagents/screenshots/components/Input.png
-   ✓ Card variants → ./proagents/screenshots/components/Card.png
+   ✓ Button variants → ./.proagents/screenshots/components/Button.png
+   ✓ Input variants → ./.proagents/screenshots/components/Input.png
+   ✓ Card variants → ./.proagents/screenshots/components/Card.png
 
    ══════════════════════════════════════════
    Screenshots saved: 15 images
-   Location: ./proagents/screenshots/
+   Location: ./.proagents/screenshots/
    ══════════════════════════════════════════
 
    Use these for:
@@ -2380,7 +2380,7 @@ mobile_testing:
     require_approval: false  # true = ask before applying fixes
 
   screenshot:
-    output_dir: ./proagents/screenshots
+    output_dir: ./.proagents/screenshots
     devices:
       - iPhone 14 Pro
       - Pixel 7
@@ -2393,7 +2393,7 @@ mobile_testing:
 
 **Test Report Structure:**
 ```
-./proagents/test-reports/
+./.proagents/test-reports/
 ├── mobile-2024-03-06-1500.md      # Full test report
 ├── visual/
 │   ├── LoginScreen-diff.png       # Visual diff images
@@ -2415,7 +2415,7 @@ mobile_testing:
 **How to execute AI Platform commands:**
 
 For `pa:ai-list`:
-- Read `./proagents/proagents.config.yaml` and show the `platforms` array
+- Read `./.proagents/proagents.config.yaml` and show the `platforms` array
 - Show which AI instruction files exist in project root
 
 For `pa:ai-add`:
@@ -2437,7 +2437,7 @@ For `pa:ai-add`:
 
 2. Ask user which platforms to add
 3. For each selected platform:
-   - Copy content from `./proagents/{PLATFORM}.md` (e.g., `./proagents/CLAUDE.md`)
+   - Copy content from `./.proagents/{PLATFORM}.md` (e.g., `./.proagents/CLAUDE.md`)
    - If target file exists, wrap new content with markers and append:
      ```
      <!-- PROAGENTS:START -->
@@ -2445,10 +2445,10 @@ For `pa:ai-add`:
      <!-- PROAGENTS:END -->
      ```
    - If target file doesn't exist, create it with the content wrapped in markers
-4. Update `./proagents/proagents.config.yaml` to add platform to `platforms` array
+4. Update `./.proagents/proagents.config.yaml` to add platform to `platforms` array
 
 For `pa:ai-remove`:
-1. Read `./proagents/proagents.config.yaml` to get current platforms
+1. Read `./.proagents/proagents.config.yaml` to get current platforms
 2. Show list and ask which to remove
 3. For each selected:
    - Remove the PROAGENTS section (between markers) from the file, OR delete the file if it only contains ProAgents content
@@ -2456,7 +2456,7 @@ For `pa:ai-remove`:
 
 For `pa:ai-sync`:
 1. Scan project root for AI instruction files
-2. Read current config from `./proagents/proagents.config.yaml`
+2. Read current config from `./.proagents/proagents.config.yaml`
 3. Compare and show differences:
    - Files that exist but not in config
    - Config entries that don't have matching files
@@ -2492,7 +2492,7 @@ For `pa:ai-sync`:
 
 ### Custom Commands
 
-Check `./proagents/custom-commands.yaml` for project-specific commands.
+Check `./.proagents/custom-commands.yaml` for project-specific commands.
 
 Built-in custom commands:
 | Command | Action |
@@ -2531,26 +2531,26 @@ Users can add their own commands in `custom-commands.yaml`.
 
 When user types a `pa:` command:
 
-1. **Read the corresponding prompt file** from `./proagents/prompts/`
+1. **Read the corresponding prompt file** from `./.proagents/prompts/`
 2. **Follow the workflow** defined in that prompt
-3. **Use project context** from `./proagents/` folder
+3. **Use project context** from `./.proagents/` folder
 
 ### Prompt File Mapping
-- `pa:feature` → `./proagents/prompts/00-init.md` + workflow
-- `pa:fix` → `./proagents/workflow-modes/entry-modes.md` (Bug Fix section)
-- `pa:doc*` → `./proagents/prompts/07-documentation.md`
-- `pa:qa` → `./proagents/checklists/code-quality.md`
-- `pa:test` → `./proagents/prompts/06-testing.md`
-- `pa:deploy` → `./proagents/prompts/08-deployment.md`
-- `pa:release` → `./proagents/prompts/07-documentation.md` (Release Notes section)
+- `pa:feature` → `./.proagents/prompts/00-init.md` + workflow
+- `pa:fix` → `./.proagents/workflow-modes/entry-modes.md` (Bug Fix section)
+- `pa:doc*` → `./.proagents/prompts/07-documentation.md`
+- `pa:qa` → `./.proagents/checklists/code-quality.md`
+- `pa:test` → `./.proagents/prompts/06-testing.md`
+- `pa:deploy` → `./.proagents/prompts/08-deployment.md`
+- `pa:release` → `./.proagents/prompts/07-documentation.md` (Release Notes section)
 
 ## Workflow Reference
 
-Full workflow documentation: `./proagents/WORKFLOW.md`
-Quick command reference: `./proagents/PROAGENTS.md`
+Full workflow documentation: `./.proagents/WORKFLOW.md`
+Quick command reference: `./.proagents/PROAGENTS.md`
 
 ## Important
 
-- Always check `./proagents/` folder for project-specific configurations
+- Always check `./.proagents/` folder for project-specific configurations
 - Preserve user's `proagents.config.yaml` settings
 - Follow existing code patterns found in the project

package/{proagents → .proagents}/ANTIGRAVITY.md

@@ -16,19 +16,19 @@ This project uses ProAgents - an AI-agnostic development workflow framework.
 
 ## Full Command Reference
 
-For complete command list, see: `./proagents/AI_INSTRUCTIONS.md`
+For complete command list, see: `./.proagents/AI_INSTRUCTIONS.md`
 
 ## On `pa:` Command
 
-1. Read the corresponding file from `./proagents/prompts/` or `./proagents/workflow-modes/`
+1. Read the corresponding file from `./.proagents/prompts/` or `./.proagents/workflow-modes/`
 2. Follow the workflow instructions
-3. Use project config from `./proagents/proagents.config.yaml`
+3. Use project config from `./.proagents/proagents.config.yaml`
 
 ## Key Files
 
-- `./proagents/AI_INSTRUCTIONS.md` - Complete command reference
-- `./proagents/WORKFLOW.md` - Full 10-phase workflow
-- `./proagents/prompts/` - Phase-specific prompts
+- `./.proagents/AI_INSTRUCTIONS.md` - Complete command reference
+- `./.proagents/WORKFLOW.md` - Full 10-phase workflow
+- `./.proagents/prompts/` - Phase-specific prompts
 
 ## Note
 

package/{proagents → .proagents}/BOLT.md

@@ -16,16 +16,16 @@ This project uses ProAgents - an AI-agnostic development workflow framework.
 
 ## Full Command Reference
 
-For complete command list, see: `./proagents/AI_INSTRUCTIONS.md`
+For complete command list, see: `./.proagents/AI_INSTRUCTIONS.md`
 
 ## On `pa:` Command
 
-1. Read the corresponding file from `./proagents/prompts/` or `./proagents/workflow-modes/`
+1. Read the corresponding file from `./.proagents/prompts/` or `./.proagents/workflow-modes/`
 2. Follow the workflow instructions
-3. Use project config from `./proagents/proagents.config.yaml`
+3. Use project config from `./.proagents/proagents.config.yaml`
 
 ## Key Files
 
-- `./proagents/AI_INSTRUCTIONS.md` - Complete command reference
-- `./proagents/WORKFLOW.md` - Full 10-phase workflow
-- `./proagents/prompts/` - Phase-specific prompts
+- `./.proagents/AI_INSTRUCTIONS.md` - Complete command reference
+- `./.proagents/WORKFLOW.md` - Full 10-phase workflow
+- `./.proagents/prompts/` - Phase-specific prompts

package/{proagents → .proagents}/CHATGPT.md

@@ -16,16 +16,16 @@ This project uses ProAgents - an AI-agnostic development workflow framework.
 
 ## Full Command Reference
 
-For complete command list, see: `./proagents/AI_INSTRUCTIONS.md`
+For complete command list, see: `./.proagents/AI_INSTRUCTIONS.md`
 
 ## On `pa:` Command
 
-1. Read the corresponding file from `./proagents/prompts/` or `./proagents/workflow-modes/`
+1. Read the corresponding file from `./.proagents/prompts/` or `./.proagents/workflow-modes/`
 2. Follow the workflow instructions
-3. Use project config from `./proagents/proagents.config.yaml`
+3. Use project config from `./.proagents/proagents.config.yaml`
 
 ## Key Files
 
-- `./proagents/AI_INSTRUCTIONS.md` - Complete command reference
-- `./proagents/WORKFLOW.md` - Full 10-phase workflow
-- `./proagents/prompts/` - Phase-specific prompts
+- `./.proagents/AI_INSTRUCTIONS.md` - Complete command reference
+- `./.proagents/WORKFLOW.md` - Full 10-phase workflow
+- `./.proagents/prompts/` - Phase-specific prompts

package/{proagents → .proagents}/CLAUDE.md

@@ -16,16 +16,16 @@ This project uses ProAgents - an AI-agnostic development workflow framework.
 
 ## Full Command Reference
 
-For complete command list, see: `./proagents/AI_INSTRUCTIONS.md`
+For complete command list, see: `./.proagents/AI_INSTRUCTIONS.md`
 
 ## On `pa:` Command
 
-1. Read the corresponding file from `./proagents/prompts/` or `./proagents/workflow-modes/`
+1. Read the corresponding file from `./.proagents/prompts/` or `./.proagents/workflow-modes/`
 2. Follow the workflow instructions
-3. Use project config from `./proagents/proagents.config.yaml`
+3. Use project config from `./.proagents/proagents.config.yaml`
 
 ## Key Files
 
-- `./proagents/AI_INSTRUCTIONS.md` - Complete command reference
-- `./proagents/WORKFLOW.md` - Full 10-phase workflow
-- `./proagents/prompts/` - Phase-specific prompts
+- `./.proagents/AI_INSTRUCTIONS.md` - Complete command reference
+- `./.proagents/WORKFLOW.md` - Full 10-phase workflow
+- `./.proagents/prompts/` - Phase-specific prompts

package/{proagents → .proagents}/GEMINI.md

@@ -16,16 +16,16 @@ This project uses ProAgents - an AI-agnostic development workflow framework.
 
 ## Full Command Reference
 
-For complete command list, see: `./proagents/AI_INSTRUCTIONS.md`
+For complete command list, see: `./.proagents/AI_INSTRUCTIONS.md`
 
 ## On `pa:` Command
 
-1. Read the corresponding file from `./proagents/prompts/` or `./proagents/workflow-modes/`
+1. Read the corresponding file from `./.proagents/prompts/` or `./.proagents/workflow-modes/`
 2. Follow the workflow instructions
-3. Use project config from `./proagents/proagents.config.yaml`
+3. Use project config from `./.proagents/proagents.config.yaml`
 
 ## Key Files
 
-- `./proagents/AI_INSTRUCTIONS.md` - Complete command reference
-- `./proagents/WORKFLOW.md` - Full 10-phase workflow
-- `./proagents/prompts/` - Phase-specific prompts
+- `./.proagents/AI_INSTRUCTIONS.md` - Complete command reference
+- `./.proagents/WORKFLOW.md` - Full 10-phase workflow
+- `./.proagents/prompts/` - Phase-specific prompts