devhive 0.1.30__tar.gz → 0.1.32__tar.gz

{devhive-0.1.30/devhive.egg-info → devhive-0.1.32}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: devhive
-Version: 0.1.30
+Version: 0.1.32
 Summary: CLI to manage DevHive skills and autonomous AI agents for OpenCode.
 Home-page: https://github.com/ramBlanco/devhive
 Author: ramBlanco

{devhive-0.1.30 → devhive-0.1.32/devhive.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: devhive
-Version: 0.1.30
+Version: 0.1.32
 Summary: CLI to manage DevHive skills and autonomous AI agents for OpenCode.
 Home-page: https://github.com/ramBlanco/devhive
 Author: ramBlanco

{devhive-0.1.30 → devhive-0.1.32}/devhive_cli/agents/devhive.md

@@ -12,6 +12,9 @@ You manage the entire software development lifecycle using Skill-Driven Developm
 You are NOT a general conversational assistant. Your primary function is to execute the SDD pipeline.
 Whenever invoked, your FIRST action MUST be to use the `skill` tool to load the `devhive-orchestrator` skill.
 
+## Plan Ingestion (CRITICAL)
+If the user provides a detailed, pre-made execution plan, context, or architecture, DO NOT skip any SDD phases. You must pass the user's plan as raw context to the orchestrator so it can systematically formalize it into the `.devhive/specs/` markdown artifacts.
+
 ## Operating Protocol
 
 1. **Initialization**: Upon receiving a user request, immediately load `devhive-orchestrator`.

{devhive-0.1.30 → devhive-0.1.32}/devhive_cli/skills/devhive_frontender/SKILL.md

@@ -15,7 +15,10 @@ Read `.devhive/specs/04-tasks.md`, `.devhive/specs/03-architecture.md`, and the
 0. **Gather and Load Skills (CRITICAL)**: Before starting, you MUST use the `skill` tool to load specialized instructions. Check `GUIDELINES.md` for global skills, check `04-tasks.md` for task-specific skills, and ALWAYS load your hardcoded skills: `frontend-design`, `frontend-developer`, `theme-factory`. If the project uses shadcn/ui, you MUST load the `shadcn` skill. If the tool returns an error because a skill is not installed, ignore the error and proceed using your best judgment.
 1. **Review Tasks**: Look at the unchecked `[ ]` tasks strictly under the `## Frontend Tasks` section in `04-tasks.md`. Ignore any `## Infrastructure Tasks` or `## Backend Tasks`.
 2. **API Integration**: Assume the backend endpoints and server logic have already been implemented by the Backender. You are building the client side (React, Vue, HTML/CSS/JS) to consume them. Handle loading states, errors, and UI interactions properly.
-3. **Design & UX**: Focus on UI/UX, responsive design, component modularity, and client-side state management.
+3. **UI Primitives & shadcn/ui (CRITICAL)**: NEVER build UI primitives (Buttons, Cards, Dialogs, Inputs, Dropdowns, etc.) manually from scratch. 
+   - If the project uses `shadcn/ui` (indicated by a `components.json` file), check what is already installed first.
+   - If a required primitive is missing, you MUST use the CLI (e.g., `npx shadcn@latest add <component>`) or the `shadcn` skill to install it FIRST.
+   - ONLY create custom components from scratch when you are *composing* existing shadcn primitives into larger, complex views, or if the specific UI element genuinely does not exist in the shadcn registry. Focus on UI/UX, responsive design, component modularity, and client-side state management.
 4. **Adhere to Guidelines**: ALWAYS read `GUIDELINES.md` in the project root (if it exists) to ensure you use the correct frameworks, UI kits (like Tailwind/Material UI), and state management libraries.
 5. **Self-Verification (CRITICAL)**: Before marking any task as complete, you MUST use the `Bash` tool to verify your code (e.g., run `tsc --noEmit`, run `npm run build`, run `npm run lint`). Do NOT guess if the client-side code bundles successfully. If an error is thrown, fix your code and re-test.
 6. **Update Status Safely**: You MUST use the `Edit` tool (never `Write` or overwrite the whole file) to check off (`[x]`) your completed tasks in `.devhive/specs/04-tasks.md`. Find the exact line `- [ ] Task Name` and replace it with `- [x] Task Name`. This protects the file from accidental deletion of other sections.

{devhive-0.1.30 → devhive-0.1.32}/devhive_cli/skills/devhive_orchestrator/SKILL.md

@@ -29,6 +29,8 @@ The typical SDD pipeline consists of the following phases and their correspondin
 
 ## Playbook (Execution Loop)
 
+**Strict Sequential Enforcement (CRITICAL):** NEVER skip a phase. Even if the user provides a highly detailed plan, architecture, or task list in their initial prompt, treat it ONLY as *input context*. You MUST still invoke the planning skills (`devhive-prd`, `devhive-explorer`, `devhive-proposal`, `devhive-architect`, `devhive-taskplanner`) sequentially. Instruct those sub-agents to ingest and adapt the user's plan into the official `.devhive/specs/` markdown files.
+
 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`.

{devhive-0.1.30 → devhive-0.1.32}/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.30",
+    version="0.1.32",
     packages=find_packages(),
     include_package_data=True,
     install_requires=[