xXx

Hexid M1n1 5h3ll MobiLe

home/emberdemos/corehr_app/current/docs/_[ Writable ]

File:/home/emberdemos/corehr_app/current/docs/PROMPTING_STRATEGY.md

### **Phase & Feature Document Mapping**

| Phase | Phase Title | Associated Feature Design Document(s) |
| :--- | :--- | :--- |
| **Phase 1** | Foundation & Org Structure | **None.** The tasks in this phase are foundational (installing packages, simple CRUD) and their requirements are fully described within the `PHASE_01.md` tracker itself. |
| **Phase 2** | Core Employee Management | `docs/features/employee_lifecycle.md` |
| **Phase 3** | Attendance & Leave Mgmt | `docs/features/02_shifts_and_attendance.md`<br>`docs/features/03_leave_management.md` |
| **Phase 4** | Advanced Payroll Platform | `docs/features/06_advanced_payroll.md`<br>`docs/features/07_payroll_tax_and_reports.md` |
| **Phase 5** | Financial & Supporting HR | `docs/features/04_expense_and_advance_management.md`<br>*(Note: We haven't created a separate doc for Loans as the tracker was very detailed, but its logic is part of this phase).* |
| **Phase 6** | Advanced Reporting & Launch | This phase is an **integrator**. It doesn't introduce new core features but builds upon all previous ones. For its reporting tasks, you will reference the design docs of the modules you're reporting on (e.g., reference the Leave Management doc when building the Leave Ledger report). |
| **Phase 7** | Recruitment & Onboarding | `docs/features/01_recruitment_module.md` |
| **Phase 8** | Performance Management | `docs/features/05_performance_management.md` |

---

### **How to Use This Information (Your Prompting Strategy)**

This mapping directly informs how you should prompt me for help with development. When you are ready to work on a specific task, you will provide me with both the **task itself** and the **context from its feature document**.

Here is a perfect example of how you would prompt me for a task in Phase 3:

**Example Prompt:**

> Okay, I am now starting **Task P3.2.7** from `PHASE_03.md`:
>
> **`P3.2.7 [ADDED] Frontend: Create Pages/Admin/Shifts/Roster.vue with a visual, drag-and-drop interface for shift planning.`**
>
> Here is the relevant context from the feature design document, `docs/features/02_shifts_and_attendance.md`:
>
> ```markdown
> ### C. Frontend Architecture (Vue.js / Inertia.js)
>
> *   **Shift Roster (Image 3):**
>     *   This is a major UI feature. We will create a new page, `Pages/Admin/Shifts/Roster.vue`.
>     *   It will use a calendar-based or grid-based layout. To achieve the **drag-and-drop** functionality for assigning and swapping shifts, we will use a library like `vue-draggable-next`.
> ```
>
> Based on this, please provide the complete, production-ready code for the `Pages/Admin/Shifts/Roster.vue` component. Make sure it adheres to all our coding standards and design guidelines, using `shadcn-vue` for all UI elements where possible.

By providing both the "what" (the task) and the "how" (the design document), you give me the precise context needed to generate the most accurate and high-quality response.

---

Your Access Expired	Date. in : 13-12-2025
Regist : 09-12-2024	Expired : 01-12-2027