devhive 0.1.28__tar.gz → 0.1.29__tar.gz

{devhive-0.1.28/devhive.egg-info → devhive-0.1.29}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: devhive
-Version: 0.1.28
+Version: 0.1.29
 Summary: CLI to manage DevHive skills and autonomous AI agents for OpenCode.
 Home-page: https://github.com/ramBlanco/devhive
 Author: ramBlanco
@@ -31,8 +31,9 @@ It replaces complex background servers and in-memory states with a transparent,
 
 DevHive is composed of specialized Agent Skills that work sequentially:
 
-1. **`devhive-explorer`**: Analyzes the request and writes `.devhive/specs/01-exploration.md`
-2. **`devhive-proposal`**: Creates acceptance criteria in `02-proposal.md`
+0. **`devhive-prd`**: Acts as a Product Manager. Writes or updates a Master `docs/PRODUCT_REQUIREMENTS.md` and generates a feature-specific `.devhive/specs/00-prd.md` before any technical work begins.
+1. **`devhive-explorer`**: Analyzes the PRD and codebase, then writes `.devhive/specs/01-exploration.md`
+2. **`devhive-proposal`**: Creates technical acceptance criteria in `02-proposal.md`
 3. **`devhive-architect`**: Designs the system architecture, DB schemas, and UX/UI design system in `03-architecture.md`
 4. **`devhive-taskplanner`**: Breaks the architecture into actionable items across 8 different domains in `04-tasks.md`
 5. **`devhive-designer`**: Implements the base UI/UX configuration (CSS vars, Tailwind configs) under `## Design Tasks`
@@ -81,7 +82,7 @@ Instead of using OpenCode as a general assistant, invoke the dedicated `@devhive
 @devhive Build a script that converts CSV to JSON running on AWS Lambda.
 ```
 
-The agent will automatically load the orchestrator skill and start the 10-phase pipeline!
+The agent will automatically load the orchestrator skill and start the 11-phase pipeline!
 
 ### Continuous Mode
 By default, the orchestrator will pause and ask for your approval after writing each specification file (e.g., after writing the architecture design). If you want it to run entirely autonomously without stopping, you can add the "continuous mode" flag to your prompt:

{devhive-0.1.28 → devhive-0.1.29}/README.md

@@ -8,8 +8,9 @@ It replaces complex background servers and in-memory states with a transparent,
 
 DevHive is composed of specialized Agent Skills that work sequentially:
 
-1. **`devhive-explorer`**: Analyzes the request and writes `.devhive/specs/01-exploration.md`
-2. **`devhive-proposal`**: Creates acceptance criteria in `02-proposal.md`
+0. **`devhive-prd`**: Acts as a Product Manager. Writes or updates a Master `docs/PRODUCT_REQUIREMENTS.md` and generates a feature-specific `.devhive/specs/00-prd.md` before any technical work begins.
+1. **`devhive-explorer`**: Analyzes the PRD and codebase, then writes `.devhive/specs/01-exploration.md`
+2. **`devhive-proposal`**: Creates technical acceptance criteria in `02-proposal.md`
 3. **`devhive-architect`**: Designs the system architecture, DB schemas, and UX/UI design system in `03-architecture.md`
 4. **`devhive-taskplanner`**: Breaks the architecture into actionable items across 8 different domains in `04-tasks.md`
 5. **`devhive-designer`**: Implements the base UI/UX configuration (CSS vars, Tailwind configs) under `## Design Tasks`
@@ -58,7 +59,7 @@ Instead of using OpenCode as a general assistant, invoke the dedicated `@devhive
 @devhive Build a script that converts CSV to JSON running on AWS Lambda.
 ```
 
-The agent will automatically load the orchestrator skill and start the 10-phase pipeline!
+The agent will automatically load the orchestrator skill and start the 11-phase pipeline!
 
 ### Continuous Mode
 By default, the orchestrator will pause and ask for your approval after writing each specification file (e.g., after writing the architecture design). If you want it to run entirely autonomously without stopping, you can add the "continuous mode" flag to your prompt:

{devhive-0.1.28 → devhive-0.1.29/devhive.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: devhive
-Version: 0.1.28
+Version: 0.1.29
 Summary: CLI to manage DevHive skills and autonomous AI agents for OpenCode.
 Home-page: https://github.com/ramBlanco/devhive
 Author: ramBlanco
@@ -31,8 +31,9 @@ It replaces complex background servers and in-memory states with a transparent,
 
 DevHive is composed of specialized Agent Skills that work sequentially:
 
-1. **`devhive-explorer`**: Analyzes the request and writes `.devhive/specs/01-exploration.md`
-2. **`devhive-proposal`**: Creates acceptance criteria in `02-proposal.md`
+0. **`devhive-prd`**: Acts as a Product Manager. Writes or updates a Master `docs/PRODUCT_REQUIREMENTS.md` and generates a feature-specific `.devhive/specs/00-prd.md` before any technical work begins.
+1. **`devhive-explorer`**: Analyzes the PRD and codebase, then writes `.devhive/specs/01-exploration.md`
+2. **`devhive-proposal`**: Creates technical acceptance criteria in `02-proposal.md`
 3. **`devhive-architect`**: Designs the system architecture, DB schemas, and UX/UI design system in `03-architecture.md`
 4. **`devhive-taskplanner`**: Breaks the architecture into actionable items across 8 different domains in `04-tasks.md`
 5. **`devhive-designer`**: Implements the base UI/UX configuration (CSS vars, Tailwind configs) under `## Design Tasks`
@@ -81,7 +82,7 @@ Instead of using OpenCode as a general assistant, invoke the dedicated `@devhive
 @devhive Build a script that converts CSV to JSON running on AWS Lambda.
 ```
 
-The agent will automatically load the orchestrator skill and start the 10-phase pipeline!
+The agent will automatically load the orchestrator skill and start the 11-phase pipeline!
 
 ### Continuous Mode
 By default, the orchestrator will pause and ask for your approval after writing each specification file (e.g., after writing the architecture design). If you want it to run entirely autonomously without stopping, you can add the "continuous mode" flag to your prompt:

{devhive-0.1.28 → devhive-0.1.29}/devhive.egg-info/SOURCES.txt

@@ -42,6 +42,7 @@ devhive_cli/skills/devhive_explorer/SKILL.md
 devhive_cli/skills/devhive_frontender/SKILL.md
 devhive_cli/skills/devhive_orchestrator/SKILL.md
 devhive_cli/skills/devhive_perf/SKILL.md
+devhive_cli/skills/devhive_prd/SKILL.md
 devhive_cli/skills/devhive_proposal/SKILL.md
 devhive_cli/skills/devhive_qa/SKILL.md
 devhive_cli/skills/devhive_releaser/SKILL.md

{devhive-0.1.28 → devhive-0.1.29}/devhive_cli/skills/devhive_explorer/SKILL.md

@@ -9,11 +9,11 @@ description: Analyzes requirements, constraints, and dependencies for a new feat
 When the orchestrator assigns you the exploration phase for a feature request.
 
 ## Input Context
-You will receive the user's feature request from the orchestrator.
+You will read `.devhive/specs/00-prd.md` and `docs/PRODUCT_REQUIREMENTS.md` (if they exist) to understand the product requirements. You may also receive the user's initial request.
 
 ## Playbook (What to Do)
 0. **Gather and Load Skills (CRITICAL)**: Before starting, you MUST use the `skill` tool to load specialized instructions. If the tool returns an error because a skill is not installed, ignore the error and proceed using your best judgment.
-1. **Understand the Request**: Determine if it is a new feature, a bug fix, or a refactor.
+1. **Understand the Requirements**: Read `.devhive/specs/00-prd.md` to understand the specific feature, and `docs/PRODUCT_REQUIREMENTS.md` to understand the broader product context. Determine if it is a new feature, a bug fix, or a refactor.
 2. **Project Guidelines (Hybrid Approach)**: Use your tools to check if a `GUIDELINES.md` or `AGENTS.md` file exists in the root of the project.
    - **If YES**: Read it to understand the enforced tech stack and architectural rules.
    - **If NO**: Deduce the best tech stack based on the prompt or existing files, and CREATE a `GUIDELINES.md` file in the project root using the `Write` tool to establish a standard for the rest of the agents. Ensure you include a `## OpenCode Skills` section with suggested global skills (e.g., `frontend-design`).

{devhive-0.1.28 → devhive-0.1.29}/devhive_cli/skills/devhive_orchestrator/SKILL.md

@@ -10,6 +10,7 @@ This skill is the CEO/Orchestrator for the DevHive Skill-Driven Development (SDD
 
 ## The Pipeline
 The typical SDD pipeline consists of the following phases and their corresponding output files:
+0. `devhive-prd` -> `00-prd.md` (and updates `docs/PRODUCT_REQUIREMENTS.md`)
 1. `devhive-explorer` -> `01-exploration.md`
 2. `devhive-proposal` -> `02-proposal.md`
 3. `devhive-architect` -> `03-architecture.md`
@@ -28,8 +29,13 @@ The typical SDD pipeline consists of the following phases and their correspondin
 
 ## Playbook (Execution Loop)
 
-1. **Check State**: Look at the files in `.devhive/specs/`. Determine what the next missing phase is. If no files exist, the next phase is `exploration`.
+1. **Check State**: Look at the files in `.devhive/specs/`. Determine what the next missing phase is. If no files exist, the next phase is `prd`.
 2. **Determine Sub-Skill**: Based on the missing phase, decide which skill to invoke.
+   - If `00-prd.md` does not exist -> Invoke `devhive-prd`.
+   - If `00-prd.md` exists but `01-exploration.md` does not -> Invoke `devhive-explorer`.
+   - If `01-exploration.md` exists but `02-proposal.md` does not -> Invoke `devhive-proposal`.
+   - If `02-proposal.md` exists but `03-architecture.md` does not -> Invoke `devhive-architect`.
+   - If `03-architecture.md` exists but `04-tasks.md` does not -> Invoke `devhive-taskplanner`.
    - If `04-tasks.md` exists but `05-sast-report.md` does not, check `04-tasks.md` sequentially:
      - Are there unchecked tasks `[ ]` under `## Design Tasks`? -> Invoke `devhive-designer`.
      - Else, are there unchecked tasks `[ ]` under `## Infrastructure Tasks`? -> Invoke `devhive-devops`.

devhive-0.1.29/devhive_cli/skills/devhive_prd/SKILL.md

@@ -0,0 +1,55 @@
+---
+name: devhive-prd
+description: Analyzes and documents Product Requirements (Master PRD & Feature PRD) before starting technical exploration.
+---
+
+# Skill: devhive-prd
+
+## Overview
+You are the DevHive Product Manager. Your role is to understand the user's request and document it as a formal Product Requirements Document (PRD). You act as the bridge between business/user needs and technical implementation.
+
+You must handle a **Hybrid PRD Approach**:
+1. A **Master PRD** (`docs/PRODUCT_REQUIREMENTS.md`) that describes the entire application.
+2. A **Feature PRD** (`.devhive/specs/00-prd.md`) that focuses solely on the current iteration/feature being requested.
+
+## Execution Flow
+
+1. **Check for the Master PRD (`docs/PRODUCT_REQUIREMENTS.md`)**
+   - If the file DOES NOT exist:
+     - You must perform "Reverse Engineering". Use tools like `glob` and `read` to scan the current codebase (package.json, main application entry points, database schemas, etc.) to understand what the project is.
+     - Create `docs/PRODUCT_REQUIREMENTS.md` documenting the current state of the application. Include: Project Vision, Target Audience, Core Features, and Key User Flows.
+   - If the file DOES exist:
+     - Read it to gain full context of the application.
+
+2. **Generate the Feature PRD (`.devhive/specs/00-prd.md`)**
+   - Based on the user's specific request for this cycle, create the feature-level PRD.
+   - Use the following structure based on the awesome-copilot PRD template:
+     ```markdown
+     # Feature PRD: [Feature Name]
+
+     ## 1. Problem Statement
+     What problem are we solving for the user? Why is this feature necessary?
+
+     ## 2. Target Audience
+     Who will use this feature?
+
+     ## 3. Goals & Success Metrics
+     What does success look like? (e.g., "Reduce login time", "Increase conversion by X%").
+
+     ## 4. Non-Goals (Out of Scope)
+     What are we explicitly NOT doing in this iteration to avoid scope creep?
+
+     ## 5. User Experience & Flows
+     Step-by-step description of how the user interacts with this feature.
+     Include edge cases (e.g., "What happens if the user enters wrong credentials 3 times?").
+
+     ## 6. Acceptance Criteria
+     A list of boolean (Yes/No) criteria that must be met for this feature to be considered "Done".
+     ```
+
+3. **Update the Master PRD**
+   - Finally, update `docs/PRODUCT_REQUIREMENTS.md` by appending or integrating the new feature's summary into the "Core Features" section, ensuring the Master PRD is always up-to-date with the latest product increments.
+
+## Deliverables
+- `docs/PRODUCT_REQUIREMENTS.md` (Created or Updated)
+- `.devhive/specs/00-prd.md` (Created for the current sprint)

{devhive-0.1.28 → devhive-0.1.29}/setup.py

@@ -8,7 +8,7 @@ with open(os.path.join(this_directory, 'README.md'), encoding='utf-8') as f:
 
 setup(
     name="devhive",
-    version="0.1.28",
+    version="0.1.29",
     packages=find_packages(),
     include_package_data=True,
     install_requires=[