@jakkrichm/create-nexus-devflow 2.0.0 → 2.0.1

package/template/.agents/skills/prp-dev-php/SKILL.md

@@ -1,63 +1,63 @@
----
-name: prp-dev-php
-description: Comprehensive skill for PHP development following the PRP Pure Agentic workflow. Supports CodeIgniter 3 and Yii 2, with MVC patterns and automated validation loops in a Zero-Script environment.
----
-
-# 🐘 PRP Dev – PHP (Pure Agentic)
-
-This Skill empowers feature development on **PHP** conforming to the PRP Framework standards, focusing principally on CodeIgniter 3 (Legacy) and Yii Framework 2 (Modern). It fully addresses MVC operations alongside fundamental security fortifications.
-
-## 🎯 Scope of Work
-Apply this Skill when:
-- **Framework Dev**: Constructing or mending Controllers, Models, and Views.
-- **Legacy Support**: Improving CodeIgniter 3 codebases for better security and structure.
-- **Modern PHP**: Advancing Yii 2 exploiting ActiveRecord and Dependency Injection.
-- **Workflow**: Doing Task-related work pertinent to PHP Apps.
-
----
-
-## 1. 🔍 Framework Detection
-Probe the environment prior to starting work:
-1. **CodeIgniter 3**: Probe for `application/config/config.php` or `system/`.
-2. **Yii 2**: Probe for `vendor/yiisoft/yii2` or `config/web.php`.
-3. **Composer**: Look over `composer.json` for PHP versions and Dependencies.
-
----
-
-## 2. 🏛️ Implementation Patterns
-
-### CodeIgniter 3 (The Singleton Pattern)
-- **Namespacing**: Frequently lacks namespaces (Global usage).
-- **Loading**: Implements `$this->load->model('...')` or `$this->load->view('...')`.
-- **Security**: Compulsory check: `defined('BASEPATH') OR exit('...');` required universally at the top of files.
-
-### Yii Framework 2 (The Component Pattern)
-- **ActiveRecord**: Fulfills Querying through Model Classes (e.g., `User::find()`).
-- **Namespacing**: Extensively integrates PSR-4 Namespacing.
-- **Views**: Incorporates `Html::encode()` alongside `$this->render()`.
-
----
-
-## 🛡️ Security Best Practices
-- **Prepared Statements**: Mandate using the Query Builder or ORM. Raw SQL accepting direct Variables is strictly forbidden.
-- **Input Validation**: Abide by Framework Validation (CI Form Validation / Yii Rules).
-- **Output Escaping**: Obviate XSS attacks by Encoding data before displaying it on HTML.
-
----
-
-## 🔄 PRP Workflow Integration (Zero-Script)
-For each Task, the Agent must adhere to these principles:
-
-### Phase: Planning (/30-Plan)
-- Designate the files for modification and outline Validation procedures (e.g., executing `phpunit`).
-
-### Phase: Implement (/40-Implement)
-- Proceed with subtasks sequentially and capture real progress in `implement.md`.
-- Chronicle implementation and verification-relevant notes in `implement.md` and `verify.md` first.
-
----
-
-## 🧪 Testing & Validation
-- **Unit Testing**: Employ `PHPUnit` or any pre-installed testing framework within the project.
-- **Command Line**: Tests typically run via `./vendor/bin/phpunit` or specialized framework commands.
-- **Manual Check**: Specify manual verification steps in `verify.md`.
+---
+name: prp-dev-php
+description: Comprehensive skill for PHP development following the PRP Pure Agentic workflow. Supports CodeIgniter 3 and Yii 2, with MVC patterns and automated validation loops in a Zero-Script environment.
+---
+
+# 🐘 PRP Dev – PHP (Pure Agentic)
+
+This Skill empowers feature development on **PHP** conforming to the PRP Framework standards, focusing principally on CodeIgniter 3 (Legacy) and Yii Framework 2 (Modern). It fully addresses MVC operations alongside fundamental security fortifications.
+
+## 🎯 Scope of Work
+Apply this Skill when:
+- **Framework Dev**: Constructing or mending Controllers, Models, and Views.
+- **Legacy Support**: Improving CodeIgniter 3 codebases for better security and structure.
+- **Modern PHP**: Advancing Yii 2 exploiting ActiveRecord and Dependency Injection.
+- **Workflow**: Doing Task-related work pertinent to PHP Apps.
+
+---
+
+## 1. 🔍 Framework Detection
+Probe the environment prior to starting work:
+1. **CodeIgniter 3**: Probe for `application/config/config.php` or `system/`.
+2. **Yii 2**: Probe for `vendor/yiisoft/yii2` or `config/web.php`.
+3. **Composer**: Look over `composer.json` for PHP versions and Dependencies.
+
+---
+
+## 2. 🏛️ Implementation Patterns
+
+### CodeIgniter 3 (The Singleton Pattern)
+- **Namespacing**: Frequently lacks namespaces (Global usage).
+- **Loading**: Implements `$this->load->model('...')` or `$this->load->view('...')`.
+- **Security**: Compulsory check: `defined('BASEPATH') OR exit('...');` required universally at the top of files.
+
+### Yii Framework 2 (The Component Pattern)
+- **ActiveRecord**: Fulfills Querying through Model Classes (e.g., `User::find()`).
+- **Namespacing**: Extensively integrates PSR-4 Namespacing.
+- **Views**: Incorporates `Html::encode()` alongside `$this->render()`.
+
+---
+
+## 🛡️ Security Best Practices
+- **Prepared Statements**: Mandate using the Query Builder or ORM. Raw SQL accepting direct Variables is strictly forbidden.
+- **Input Validation**: Abide by Framework Validation (CI Form Validation / Yii Rules).
+- **Output Escaping**: Obviate XSS attacks by Encoding data before displaying it on HTML.
+
+---
+
+## 🔄 PRP Workflow Integration (Zero-Script)
+For each Task, the Agent must adhere to these principles:
+
+### Phase: Planning (/30-Plan)
+- Designate the files for modification and outline Validation procedures (e.g., executing `phpunit`).
+
+### Phase: Implement (/40-Implement)
+- Proceed with subtasks sequentially and capture real progress in `implement.md`.
+- Chronicle implementation and verification-relevant notes in `implement.md` and `verify.md` first.
+
+---
+
+## 🧪 Testing & Validation
+- **Unit Testing**: Employ `PHPUnit` or any pre-installed testing framework within the project.
+- **Command Line**: Tests typically run via `./vendor/bin/phpunit` or specialized framework commands.
+- **Manual Check**: Specify manual verification steps in `verify.md`.

package/template/.agents/skills/prp-sa-ba/SKILL.md

@@ -1,52 +1,52 @@
----
-name: prp-sa-ba
-description: Assist SA/BA in this PRP-based Pure Agentic project with requirement analysis, spec refinement, and maintaining INITIAL.md. Use whenever the user is acting as SA/BA, defining tasks, or discussing project overview.
----
-
-# 📋 PRP SA/BA Workflow (Pure Agentic)
-
-This Skill is tailored to assist users playing the role of an **SA/BA/PO** by collecting requirements and setting up specs so that the AI can work precisely thereafter in accordance with Pure Agentic Framework standards.
-
-## 🎯 Scope of Work
-Apply this Skill when:
-- **Requirement Analysis**: Transcribing Raw requirements into an actionable plan.
-- **Spec Refinement**: Formatting or fine-tuning `spec.md` located in the task folder.
-- **Project Indexing**: Operating and updating `INITIAL.md` ensuring it acts as an up-to-date index.
-- **Flow Coordination**: Recommending ensuing actions within the Workflow (Issue -> Spec -> Plan -> Code -> Verify).
-
----
-
-## 1. 📂 Staging to Spec (Phase: New Task)
-Commencing a new task:
-1. **Pickup from Staging**: Monitor for specific files localized inside `devflow/issues/` (Staging Area).
-2. **Standardize**: Exploit Issue data to instigate a task directory under `devflow/runs/{ID}-{slug}/`.
-3. **Core Files**: Lay down standard requisite AI files:
-   - `spec.md`: Elaborate technical nuances coupled with Acceptance Criteria.
-   - `define.md` / `spec.md` metadata sections: informative context relating to categories, priority, and complexity.
-
----
-
-## 2. 🧠 Requirement Refining
-Aid the SA/BA in finalizing needs thoroughly prior to writing any Code:
-- **Dimension 360**: Question elements about Edge Cases, UX, Security, and Technical Impacts.
-- **Measurable Goals**: Tweak Acceptance Criteria causing them to be quantitatively tangible (averting phrases like "make it good").
-- **Metadata Tuning**: Harmonize Complexity and Priority to resonate closely alongside the veritable effort needed.
-
----
-
-## 3. 📑 Maintaining INITIAL.md
-Act as custodian of the "Home Page of Project" warranting it persists as the quintessential Source of Truth invariably:
-- **Indexing**: During the inception or completion of a Task, append a link right into the `Active Specs & Tasks` division.
-- **Stack Status**: Maintain the pertinent Technical Stack information actively updated if modifications transpire.
-- **Allowed Commands**: Audit alongside updating explicit lists highlighting commands currently actionable by the AI.
-
----
-
-## 🔄 Workflow Guidance (Next Steps)
-Advocate relevant commands following the DevFlow 2.0 hierarchy:
-1. **Planning**: Once a spec matures sufficiently, advise executing `/30-Plan {ID}`.
-2. **Implementation**: After the plan is ready, endorse launching `/40-Implement {ID}`.
-3. **Review**: After implementation evidence exists, point the user to `/50-Verify {ID}`, then `/60-Report {ID}`, and finally `/70-Release {ID}` when release execution is still needed.
-
----
-*Note: This skill synergizes most efficiently running alongside the Agent Persona `requirements-engineer`.*
+---
+name: prp-sa-ba
+description: Assist SA/BA in this PRP-based Pure Agentic project with requirement analysis, spec refinement, and maintaining INITIAL.md. Use whenever the user is acting as SA/BA, defining tasks, or discussing project overview.
+---
+
+# 📋 PRP SA/BA Workflow (Pure Agentic)
+
+This Skill is tailored to assist users playing the role of an **SA/BA/PO** by collecting requirements and setting up specs so that the AI can work precisely thereafter in accordance with Pure Agentic Framework standards.
+
+## 🎯 Scope of Work
+Apply this Skill when:
+- **Requirement Analysis**: Transcribing Raw requirements into an actionable plan.
+- **Spec Refinement**: Formatting or fine-tuning `spec.md` located in the task folder.
+- **Project Indexing**: Operating and updating `INITIAL.md` ensuring it acts as an up-to-date index.
+- **Flow Coordination**: Recommending ensuing actions within the Workflow (Issue -> Spec -> Plan -> Code -> Verify).
+
+---
+
+## 1. 📂 Staging to Spec (Phase: New Task)
+Commencing a new task:
+1. **Pickup from Staging**: Monitor for specific files localized inside `devflow/issues/` (Staging Area).
+2. **Standardize**: Exploit Issue data to instigate a task directory under `devflow/runs/{ID}-{slug}/`.
+3. **Core Files**: Lay down standard requisite AI files:
+   - `spec.md`: Elaborate technical nuances coupled with Acceptance Criteria.
+   - `define.md` / `spec.md` metadata sections: informative context relating to categories, priority, and complexity.
+
+---
+
+## 2. 🧠 Requirement Refining
+Aid the SA/BA in finalizing needs thoroughly prior to writing any Code:
+- **Dimension 360**: Question elements about Edge Cases, UX, Security, and Technical Impacts.
+- **Measurable Goals**: Tweak Acceptance Criteria causing them to be quantitatively tangible (averting phrases like "make it good").
+- **Metadata Tuning**: Harmonize Complexity and Priority to resonate closely alongside the veritable effort needed.
+
+---
+
+## 3. 📑 Maintaining INITIAL.md
+Act as custodian of the "Home Page of Project" warranting it persists as the quintessential Source of Truth invariably:
+- **Indexing**: During the inception or completion of a Task, append a link right into the `Active Specs & Tasks` division.
+- **Stack Status**: Maintain the pertinent Technical Stack information actively updated if modifications transpire.
+- **Allowed Commands**: Audit alongside updating explicit lists highlighting commands currently actionable by the AI.
+
+---
+
+## 🔄 Workflow Guidance (Next Steps)
+Advocate relevant commands following the DevFlow 2.0 hierarchy:
+1. **Planning**: Once a spec matures sufficiently, advise executing `/30-Plan {ID}`.
+2. **Implementation**: After the plan is ready, endorse launching `/40-Implement {ID}`.
+3. **Review**: After implementation evidence exists, point the user to `/50-Verify {ID}`, then `/60-Report {ID}`, and finally `/70-Release {ID}` when release execution is still needed.
+
+---
+*Note: This skill synergizes most efficiently running alongside the Agent Persona `requirements-engineer`.*