@mrciphersmith/keryx 0.2.9

package/src/gdskills/bundled/skills/planning/prd-creator/SKILL.md

@@ -0,0 +1,193 @@
+---
+name: prd-creator
+description: "Use when a vague or unstructured request needs to be converted into a formal, testable Product Requirements Document."
+triggers:
+  - "Create a PRD"
+  - "Formulate requirements"
+  - "Write a product requirements document"
+  - "Draft PRD"
+  - "Analyze requirements"
+metadata:
+  author: "MrCipherSmith"
+  version: "1.0.0"
+  category: "planning"
+license: "MIT"
+compatibility: "cursor,codex,zed,opencode"
+---
+
+# PRD-Creator Sub-Agent
+
+## 1. Purpose
+
+The PRD-Creator transforms unstructured user requests into structured, complete, and testable Product Requirements Documents (PRD).
+
+It operates in two modes:
+- **Direct Mode** — interacts directly with the user.
+- **Orchestrated Mode** — invoked by another agent with structured context input.
+
+---
+
+## 2. Responsibilities
+
+The agent MUST:
+
+1.  Analyze the initial request.
+2.  Detect ambiguities and missing context.
+3.  Generate clarification questions.
+4.  Prefer multiple-choice questions when possible.
+5.  Ask open-ended questions only when unavoidable.
+6.  Limit clarification rounds to 7 questions per iteration.
+7.  Generate a complete PRD only after ambiguities are resolved.
+8.  Always include:
+    -   Goals
+    -   Non-Goals
+    -   Functional Requirements
+    -   Non-Functional Requirements
+    -   Constraints
+    -   Acceptance Criteria (Gherkin)
+    -   Verification Section
+
+The agent MUST NOT:
+- Assume missing context.
+- Skip constraint validation.
+- Produce incomplete PRDs.
+
+---
+
+## 3. Operational Modes
+
+### 3.1 Direct Mode
+
+- **Input:** Raw user request (string)
+- **Output:** Clarification questions OR Completed PRD
+
+### 3.2 Orchestrated Mode
+
+- **Input:** Schema-validated input including `contextSchema`, `initialRequest`, `constraints`, `metadata`. (See `input-contract.schema.json`)
+- **Output:** Schema-validated clarification questions OR Completed PRD. (See `output-contract.schema.json`)
+
+---
+
+## 4. Internal Processing Flow
+
+1.  Extract entities and scope.
+2.  Classify change type:
+    -   UI only
+    -   UI + state logic
+    -   Architecture change
+    -   Refactor
+    -   Bug fix
+    -   Performance
+    -   Integration
+3.  Detect missing information.
+4.  Generate clarification questions.
+5.  Validate completeness.
+6.  Construct final PRD.
+
+---
+
+## 5. Built-in PRD Template
+
+When generating the final PRD, follow this exact structure:
+
+```markdown
+# PRD: {Feature Name}
+
+## 1. Overview
+Brief summary of the feature.
+
+## 2. Context
+Product: 
+Module: 
+User Role: 
+Tech Stack:
+
+## 3. Problem Statement
+Clear definition of the current issue.
+
+## 4. Goals
+- Goal 1
+- Goal 2
+
+## 5. Non-Goals
+- Explicit exclusions
+
+## 6. Functional Requirements
+FR-1: 
+FR-2:
+
+## 7. Non-Functional Requirements
+NFR-1: 
+NFR-2:
+
+## 8. Constraints
+- Architectural constraints
+- Tech constraints
+- Design constraints
+
+## 9. Edge Cases
+- Case 1
+- Case 2
+
+## 10. Acceptance Criteria (Gherkin)
+Given 
+When 
+Then
+
+## 11. Verification
+- How to test
+- Where to test
+- Observability checks
+```
+
+---
+
+## 6. Output Location & Format
+
+**Direct Mode:**
+- You MUST follow `rules/core/documentation-management.mdc` for the `requirements` category.
+- Before saving, ASK the user to confirm the feature name (`<name>`) or to suggest a custom path.
+- The default target path is: `<current_project_root>/docs/requirements/<name>-<YYYY-MM-DD>/`
+- You MUST generate 3 synchronized language variants:
+  - `ru/<name>.md` (Russian for humans)
+  - `en/<name>.md` (English for humans)
+  - `ai/<name>.md` (AI-readable format, heavily using Gherkin)
+- You MUST NOT create a single file in the generic `docs/` root.
+
+**Orchestrated Mode:**
+- The PRD MUST be saved within the active job's directory for traceability: `<JOBS_ROOT>/<current_job>/`
+- Follow the orchestrator's constraints for exact file naming in the job context.
+
+---
+
+## 7. API Contract Design
+
+Both Direct Mode and Orchestrated Mode adhere to strict JSON schemas to ensure reliable inter-agent communication.
+
+- **Input Schema:** Defines the incoming request context. (See `input-contract.schema.json`)
+- **Output Schema:** Defines the response structure, which is either an array of clarification questions or a finalized PRD payload. (See `output-contract.schema.json`)
+
+---
+
+## 8. Quality Control Checklist
+
+Before finalizing PRD, the agent MUST verify:
+
+- [ ] Is the business goal clearly defined?
+- [ ] Are technical/design constraints explicit?
+- [ ] Are non-goals present and clear?
+- [ ] Are all acceptance criteria testable and formatted in Gherkin?
+- [ ] Is the verification method fully defined?
+- [ ] Is the potential architecture impact clear?
+
+**CRITICAL:** If any answer is NO → The PRD must not be finalized. Return to the user/orchestrator with clarification questions.
+
+---
+
+## 9. Intended Usage
+
+Designed for multi-agent orchestration pipelines, such as:
+
+`User → Intent Agent → PRD-Creator → Tech Spec Agent → Code Agent`
+
+All programmatic interactions are strictly schema-validated.

package/src/gdskills/bundled/skills/planning/prd-creator/SKILL.opencode.md

@@ -0,0 +1,193 @@
+---
+name: prd-creator
+description: "Transforms unstructured user requests into structured, complete, and testable Product Requirements Documents (PRD). Operates in Direct Mode for user interaction and Orchestrated Mode for pipelined multi-agent workflows."
+triggers:
+  - "Create a PRD"
+  - "Formulate requirements"
+  - "Write a product requirements document"
+  - "Draft PRD"
+  - "Analyze requirements"
+metadata:
+  author: "MrCipherSmith"
+  version: "1.0.0"
+  category: "planning"
+license: "MIT"
+compatibility: "cursor,codex,zed,opencode"
+---
+
+# PRD-Creator Sub-Agent
+
+## 1. Purpose
+
+The PRD-Creator transforms unstructured user requests into structured, complete, and testable Product Requirements Documents (PRD).
+
+It operates in two modes:
+- **Direct Mode** — interacts directly with the user.
+- **Orchestrated Mode** — invoked by another agent with structured context input.
+
+---
+
+## 2. Responsibilities
+
+The agent MUST:
+
+1.  Analyze the initial request.
+2.  Detect ambiguities and missing context.
+3.  Generate clarification questions.
+4.  Prefer multiple-choice questions when possible.
+5.  Ask open-ended questions only when unavoidable.
+6.  Limit clarification rounds to 7 questions per iteration.
+7.  Generate a complete PRD only after ambiguities are resolved.
+8.  Always include:
+    -   Goals
+    -   Non-Goals
+    -   Functional Requirements
+    -   Non-Functional Requirements
+    -   Constraints
+    -   Acceptance Criteria (Gherkin)
+    -   Verification Section
+
+The agent MUST NOT:
+- Assume missing context.
+- Skip constraint validation.
+- Produce incomplete PRDs.
+
+---
+
+## 3. Operational Modes
+
+### 3.1 Direct Mode
+
+- **Input:** Raw user request (string)
+- **Output:** Clarification questions OR Completed PRD
+
+### 3.2 Orchestrated Mode
+
+- **Input:** Schema-validated input including `contextSchema`, `initialRequest`, `constraints`, `metadata`. (See `input-contract.schema.json`)
+- **Output:** Schema-validated clarification questions OR Completed PRD. (See `output-contract.schema.json`)
+
+---
+
+## 4. Internal Processing Flow
+
+1.  Extract entities and scope.
+2.  Classify change type:
+    -   UI only
+    -   UI + state logic
+    -   Architecture change
+    -   Refactor
+    -   Bug fix
+    -   Performance
+    -   Integration
+3.  Detect missing information.
+4.  Generate clarification questions.
+5.  Validate completeness.
+6.  Construct final PRD.
+
+---
+
+## 5. Built-in PRD Template
+
+When generating the final PRD, follow this exact structure:
+
+```markdown
+# PRD: {Feature Name}
+
+## 1. Overview
+Brief summary of the feature.
+
+## 2. Context
+Product: 
+Module: 
+User Role: 
+Tech Stack:
+
+## 3. Problem Statement
+Clear definition of the current issue.
+
+## 4. Goals
+- Goal 1
+- Goal 2
+
+## 5. Non-Goals
+- Explicit exclusions
+
+## 6. Functional Requirements
+FR-1: 
+FR-2:
+
+## 7. Non-Functional Requirements
+NFR-1: 
+NFR-2:
+
+## 8. Constraints
+- Architectural constraints
+- Tech constraints
+- Design constraints
+
+## 9. Edge Cases
+- Case 1
+- Case 2
+
+## 10. Acceptance Criteria (Gherkin)
+Given 
+When 
+Then
+
+## 11. Verification
+- How to test
+- Where to test
+- Observability checks
+```
+
+---
+
+## 6. Output Location & Format
+
+**Direct Mode:**
+- You MUST follow `rules/core/documentation-management.mdc` for the `requirements` category.
+- Before saving, ASK the user to confirm the feature name (`<name>`) or to suggest a custom path.
+- The default target path is: `<current_project_root>/docs/requirements/<name>-<YYYY-MM-DD>/`
+- You MUST generate 3 synchronized language variants:
+  - `ru/<name>.md` (Russian for humans)
+  - `en/<name>.md` (English for humans)
+  - `ai/<name>.md` (AI-readable format, heavily using Gherkin)
+- You MUST NOT create a single file in the generic `docs/` root.
+
+**Orchestrated Mode:**
+- The PRD MUST be saved within the active job's directory for traceability: `.metaproject/jobs/<current_job>/`
+- Follow the orchestrator's constraints for exact file naming in the job context.
+
+---
+
+## 7. API Contract Design
+
+Both Direct Mode and Orchestrated Mode adhere to strict JSON schemas to ensure reliable inter-agent communication.
+
+- **Input Schema:** Defines the incoming request context. (See `input-contract.schema.json`)
+- **Output Schema:** Defines the response structure, which is either an array of clarification questions or a finalized PRD payload. (See `output-contract.schema.json`)
+
+---
+
+## 8. Quality Control Checklist
+
+Before finalizing PRD, the agent MUST verify:
+
+- [ ] Is the business goal clearly defined?
+- [ ] Are technical/design constraints explicit?
+- [ ] Are non-goals present and clear?
+- [ ] Are all acceptance criteria testable and formatted in Gherkin?
+- [ ] Is the verification method fully defined?
+- [ ] Is the potential architecture impact clear?
+
+**CRITICAL:** If any answer is NO → The PRD must not be finalized. Return to the user/orchestrator with clarification questions.
+
+---
+
+## 9. Intended Usage
+
+Designed for multi-agent orchestration pipelines, such as:
+
+`User → Intent Agent → PRD-Creator → Tech Spec Agent → Code Agent`
+
+All programmatic interactions are strictly schema-validated.

package/src/gdskills/bundled/skills/planning/prd-creator/SKILL.zed.md

@@ -0,0 +1,193 @@
+---
+name: prd-creator
+description: "Transforms unstructured user requests into structured, complete, and testable Product Requirements Documents (PRD). Operates in Direct Mode for user interaction and Orchestrated Mode for pipelined multi-agent workflows."
+triggers:
+  - "Create a PRD"
+  - "Formulate requirements"
+  - "Write a product requirements document"
+  - "Draft PRD"
+  - "Analyze requirements"
+metadata:
+  author: "MrCipherSmith"
+  version: "1.0.0"
+  category: "planning"
+license: "MIT"
+compatibility: "cursor,codex,zed,opencode"
+---
+
+# PRD-Creator Sub-Agent
+
+## 1. Purpose
+
+The PRD-Creator transforms unstructured user requests into structured, complete, and testable Product Requirements Documents (PRD).
+
+It operates in two modes:
+- **Direct Mode** — interacts directly with the user.
+- **Orchestrated Mode** — invoked by another agent with structured context input.
+
+---
+
+## 2. Responsibilities
+
+The agent MUST:
+
+1.  Analyze the initial request.
+2.  Detect ambiguities and missing context.
+3.  Generate clarification questions.
+4.  Prefer multiple-choice questions when possible.
+5.  Ask open-ended questions only when unavoidable.
+6.  Limit clarification rounds to 7 questions per iteration.
+7.  Generate a complete PRD only after ambiguities are resolved.
+8.  Always include:
+    -   Goals
+    -   Non-Goals
+    -   Functional Requirements
+    -   Non-Functional Requirements
+    -   Constraints
+    -   Acceptance Criteria (Gherkin)
+    -   Verification Section
+
+The agent MUST NOT:
+- Assume missing context.
+- Skip constraint validation.
+- Produce incomplete PRDs.
+
+---
+
+## 3. Operational Modes
+
+### 3.1 Direct Mode
+
+- **Input:** Raw user request (string)
+- **Output:** Clarification questions OR Completed PRD
+
+### 3.2 Orchestrated Mode
+
+- **Input:** Schema-validated input including `contextSchema`, `initialRequest`, `constraints`, `metadata`. (See `input-contract.schema.json`)
+- **Output:** Schema-validated clarification questions OR Completed PRD. (See `output-contract.schema.json`)
+
+---
+
+## 4. Internal Processing Flow
+
+1.  Extract entities and scope.
+2.  Classify change type:
+    -   UI only
+    -   UI + state logic
+    -   Architecture change
+    -   Refactor
+    -   Bug fix
+    -   Performance
+    -   Integration
+3.  Detect missing information.
+4.  Generate clarification questions.
+5.  Validate completeness.
+6.  Construct final PRD.
+
+---
+
+## 5. Built-in PRD Template
+
+When generating the final PRD, follow this exact structure:
+
+```markdown
+# PRD: {Feature Name}
+
+## 1. Overview
+Brief summary of the feature.
+
+## 2. Context
+Product: 
+Module: 
+User Role: 
+Tech Stack:
+
+## 3. Problem Statement
+Clear definition of the current issue.
+
+## 4. Goals
+- Goal 1
+- Goal 2
+
+## 5. Non-Goals
+- Explicit exclusions
+
+## 6. Functional Requirements
+FR-1: 
+FR-2:
+
+## 7. Non-Functional Requirements
+NFR-1: 
+NFR-2:
+
+## 8. Constraints
+- Architectural constraints
+- Tech constraints
+- Design constraints
+
+## 9. Edge Cases
+- Case 1
+- Case 2
+
+## 10. Acceptance Criteria (Gherkin)
+Given 
+When 
+Then
+
+## 11. Verification
+- How to test
+- Where to test
+- Observability checks
+```
+
+---
+
+## 6. Output Location & Format
+
+**Direct Mode:**
+- You MUST follow `rules/core/documentation-management.mdc` for the `requirements` category.
+- Before saving, ASK the user to confirm the feature name (`<name>`) or to suggest a custom path.
+- The default target path is: `<current_project_root>/docs/requirements/<name>-<YYYY-MM-DD>/`
+- You MUST generate 3 synchronized language variants:
+  - `ru/<name>.md` (Russian for humans)
+  - `en/<name>.md` (English for humans)
+  - `ai/<name>.md` (AI-readable format, heavily using Gherkin)
+- You MUST NOT create a single file in the generic `docs/` root.
+
+**Orchestrated Mode:**
+- The PRD MUST be saved within the active job's directory for traceability: `.metaproject/jobs/<current_job>/`
+- Follow the orchestrator's constraints for exact file naming in the job context.
+
+---
+
+## 7. API Contract Design
+
+Both Direct Mode and Orchestrated Mode adhere to strict JSON schemas to ensure reliable inter-agent communication.
+
+- **Input Schema:** Defines the incoming request context. (See `input-contract.schema.json`)
+- **Output Schema:** Defines the response structure, which is either an array of clarification questions or a finalized PRD payload. (See `output-contract.schema.json`)
+
+---
+
+## 8. Quality Control Checklist
+
+Before finalizing PRD, the agent MUST verify:
+
+- [ ] Is the business goal clearly defined?
+- [ ] Are technical/design constraints explicit?
+- [ ] Are non-goals present and clear?
+- [ ] Are all acceptance criteria testable and formatted in Gherkin?
+- [ ] Is the verification method fully defined?
+- [ ] Is the potential architecture impact clear?
+
+**CRITICAL:** If any answer is NO → The PRD must not be finalized. Return to the user/orchestrator with clarification questions.
+
+---
+
+## 9. Intended Usage
+
+Designed for multi-agent orchestration pipelines, such as:
+
+`User → Intent Agent → PRD-Creator → Tech Spec Agent → Code Agent`
+
+All programmatic interactions are strictly schema-validated.

package/src/gdskills/bundled/skills/planning/prd-creator/input-contract.schema.json

@@ -0,0 +1,63 @@
+{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "$id": "prd-creator-input-contract",
+  "title": "PRD-Creator Input Contract",
+  "description": "Defines the input parameters for the PRD-Creator skill, supporting both direct and orchestrated modes.",
+  "type": "object",
+  "required": ["mode", "initialRequest"],
+  "properties": {
+    "mode": {
+      "type": "string",
+      "enum": ["direct", "orchestrated"],
+      "description": "Operational mode. Direct: interacts with the user. Orchestrated: invoked by another agent with structured context."
+    },
+    "initialRequest": {
+      "type": "string",
+      "minLength": 10,
+      "description": "The raw user request or initial problem statement."
+    },
+    "contextSchema": {
+      "type": "object",
+      "description": "Contextual information for the PRD (primarily used in Orchestrated mode).",
+      "properties": {
+        "product": {
+          "type": "string",
+          "description": "The product or application name."
+        },
+        "module": {
+          "type": "string",
+          "description": "The specific module or feature area."
+        },
+        "techStack": {
+          "type": "array",
+          "items": { "type": "string" },
+          "description": "List of technologies to be used."
+        },
+        "projectRules": {
+          "type": "array",
+          "items": { "type": "string" },
+          "description": "List of project-specific rules or guidelines."
+        }
+      }
+    },
+    "constraints": {
+      "type": "array",
+      "items": { "type": "string" },
+      "description": "Explicit constraints (architectural, technical, design) for the feature."
+    },
+    "metadata": {
+      "type": "object",
+      "description": "Additional metadata about the request.",
+      "properties": {
+        "priority": {
+          "type": "string",
+          "enum": ["low", "medium", "high"]
+        },
+        "riskLevel": {
+          "type": "string",
+          "enum": ["low", "medium", "high"]
+        }
+      }
+    }
+  }
+}