initial: bootstrap from BukidBountyApp base

.agents/workflows/commit-push-sync.md

@@ -0,0 +1,5 @@
+---
+description: After Completing a task commit and push
+---
+
+After Completing a task commit, push  and sync also make sure the commit message is clear about the features for the user not just code changes. also only commit those files that have been changed by this task. ensure the push are synced to all git servers

.agents/workflows/complete-provided-tasks-plans.md

@@ -0,0 +1,13 @@
+---
+description: complete the plans and tasks files provided
+---
+
+Complete the prd document and prompt document provided
+Update the prd documents for each task completed.
+
+Once all tasks are completed, Completed tasks (prompt-*.md && prd-*.md) files are moved to docs/completed
+
+the new names are 
+prompt-*.md = prt-{datetimenumber}.md
+prd-*.md = chklist-{datetimenumber}.md
+the {datetimenumber} must match be the same in both the files

.agents/workflows/feature-recommendations-update.md

@@ -0,0 +1,8 @@
+---
+description: Update ai-docs/features-recommendations.md
+---
+
+scan the whole system and update a document ai-docs/features-recommendations.md
+Recommend changes improvements, bug fixes and feature recommendations
+if a feature already exists as it is written in the file then remove them from the file
+make sure to truly verify if a feature truly exists the way it was specified before removing it in the file.

.agents/workflows/npm-build-docker-restart.md

@@ -0,0 +1,22 @@
+---
+description: Restarts the application container to apply changes, as per RULE[build-restart.md] and user preference.
+---
+
+// turbo-all
+# Simplify Build and Restart Workflow
+
+Use this workflow to quickly restart the application container. This follows the required `RULE[build-restart.md]`.
+
+## Execution Steps
+
+1. **Restart the application container**
+   - As per `RULE[build-restart.md]`, we restart the following container:
+   ```bash
+   npm run build
+   docker restart bukidbountyapp
+   ```
+
+2. **Verify the container is running**
+   ```bash
+   docker ps | grep bukidbountyapp
+   ```

.agents/workflows/ralph-loop-plan.md

@@ -0,0 +1,39 @@
+---
+description: Generates a high-level plan and granular todo-checklist for a given requirement, following the Ralph Loop methodology.
+---
+
+# Ralph Loop: Autonomous Planning Workflow
+
+Use this workflow to break down complex requirements into structured, verifiable plans and task lists without modifying the source code. This ensures a clean "Ralph Loop" iteration where the planning is decoupled from implementation.
+
+## 🚀 Execution Steps
+
+1. **Verify Baseline Stability**
+   - Run the existing test suite to ensure the application is in a stable state before planning.
+   ```bash
+   docker compose exec bukidbountyapp composer test
+   ```
+
+2. **Define the Requirement**
+   - Read the user's input requirement and search the codebase to identify affected models, controllers, views, and routes.
+   - Refer to `ai-docs/dictionary.md` for existing definitions and standard fields.
+
+3. **Generate High-Level Plan**
+   - Create a new plan file in `docs/tasks/prompt-[timestamp].md`.
+   - The timestamp format should be `YYYYMMDD-HHMMSS`.
+   - The plan should define the technical approach, architecture, and any new dependencies.
+
+4. **Generate Detailed Checklist (Ralph Task)**
+   - Create a task checklist in `docs/tasks/prd-[timestamp same as timestamp of plan file].md`.
+   - Use a short hash of the requirement or content for the filename.
+   - Format:
+     ```markdown
+     # Checklist: [Requirement Name]
+     - [ ] **[Component]**: Specific instruction (e.g., "Add 'status' column in 'shipments' table")
+     - [ ] **[File Path]**: Precise line-level instructions if possible
+     ```
+   - Ensure the instructions are specific enough for a "simpler AI" to execute.
+
+5. **Final Review**
+   - Summarize the generated documents for the user.
+   - **CRITICAL**: Do NOT modify any existing `.php`, `.vue`, or logic files during this step. Only write to `ai-docs/` and `docs/tasks/`.