Skip to main content

DevHive: Skill-Driven Development (SDD) for OpenCode

DevHive is a fully autonomous AI software development pipeline designed specifically as a set of Skills and a dedicated Agent for OpenCode.

It replaces complex background servers and in-memory states with a transparent, predictable, and local Skill-Driven Development (SDD) architecture. DevHive uses your file system (.devhive/specs/) as its database, generating readable Markdown files at each step of the software lifecycle.

The Pipeline

DevHive is composed of specialized Agent Skills that work sequentially:

  1. 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.
  2. devhive-explorer: Analyzes the PRD and codebase, then writes .devhive/specs/01-exploration.md
  3. devhive-proposal: Creates technical acceptance criteria in 02-proposal.md
  4. devhive-architect: Designs the system architecture, DB schemas, and UX/UI design system in 03-architecture.md
  5. devhive-taskplanner: Breaks the architecture into actionable items across 8 different domains in 04-tasks.md
  6. devhive-designer: Implements the base UI/UX configuration (CSS vars, Tailwind configs) under ## Design Tasks
  7. devhive-devops: Writes Infrastructure as Code (IaC) (Terraform, CDK, Docker) and checks off ## Infrastructure Tasks
  8. devhive-dba: Creates DB schemas, migrations, and seeders under ## Data Tasks
  9. devhive-backender: Initializes the project, writes APIs and server logic, and checks off ## Backend Tasks
  10. devhive-frontender: Writes UI components and client-side logic, and checks off ## Frontend Tasks
  11. devhive-perf: Writes load testing scripts (k6, artillery) under ## Performance Tasks
  12. devhive-techwriter: Writes API docs (Swagger) and updates README under ## Documentation Tasks
  13. devhive-releaser: Bumps package versions, writes CHANGELOG, and creates local git tags under ## Release Tasks
  14. devhive-sast: Performs a Static Application Security Testing (SAST) scan and writes 05-sast-report.md
  15. devhive-qa: Writes test cases and test plans in 06-qa-plan.md
  16. devhive-auditor: Performs a final check and writes 07-audit.md
  17. devhive-reflection: Extracts persistent memory (semantic, episodic, anti-patterns) to .devhive/memory/ and writes 08-reflection.md

All of this is managed by the devhive-orchestrator skill.

Installation

DevHive is available as a Python package via PyPI. You can install it globally to manage your OpenCode skills across all your environments.

pip install devhive

Once installed, you can use the CLI to setup or update your DevHive environment:

# Install all official and community skills into OpenCode
devhive install

# Update your existing skills to the latest versions
devhive update-skill

# Initialize a modern Next.js/React frontend AI guidelines file in your current project
devhive init-frontend

# Initialize a Hexagonal Architecture backend AI guidelines file (Interactive Prompt)
devhive init-backend

Usage (The @devhive Agent)

Instead of using OpenCode as a general assistant, invoke the dedicated @devhive agent. This agent is hardwired to immediately start the SDD pipeline.

@devhive Build a script that converts CSV to JSON running on AWS Lambda.

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 Build a React landing page. Run in continuous mode with no pauses.

Or permanently enable it for the project by creating a flag file:

mkdir -p .devhive
touch .devhive/continuous

Why SDD (Skill-Driven Development)?

  • Zero Setup: No Python servers, no MCP configuration, no background processes.
  • Local Memory: The entire state of the project is readable by humans in .devhive/specs/. You can edit 02-proposal.md manually, and the Architect will adapt to your changes.
  • Modular: Need a different architectural approach? You can just tweak the prompt inside skills/devhive_architect/SKILL.md.

License

MIT License.

Metadata

Release files for devhive 0.1.40

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for devhive 0.1.40
File Size Uploaded
devhive-0.1.40.tar.gz 177.9 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for devhive 0.1.40
File Interpreter ABI Platform
devhive-0.1.40-py3-none-any.whl Python 3 none any Details

Total release size: 379.1 kB

Release files / devhive-0.1.40.tar.gz

Download URL devhive-0.1.40.tar.gz
Size 177.9 kB
Tags Source
SHA-256 checksum
How to use checksums
bc6605b1958391898e64ce8126ddf501e4e7bad17dde461712f79a7c8fe9375b
BLAKE2b-256 checksum
How to use checksums
375ecb1e776b44ec8e041bc68ad9b22cc0dc1b12dfcab65a10489429281c8dc0
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Jun 6, 2026.

Transparency log

Release files / devhive-0.1.40-py3-none-any.whl

Download URL devhive-0.1.40-py3-none-any.whl
Size 201.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
a9ab1892d8ffe7b88a7d4d6dc51d4e9cf6c98790d3afdc31d441b24c1e7f56b8
BLAKE2b-256 checksum
How to use checksums
30cc3c8ba7cd5f4a2de4abe23561091516d12842a025fe377a03e06e0b030de6
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Jun 6, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.1.40 This release

2 release files

0.1.38

2 release files

0.1.37

2 release files

0.1.36

2 release files

0.1.35

2 release files

0.1.34

2 release files

0.1.30

2 release files

0.1.29

2 release files

0.1.28

2 release files

0.1.27

2 release files

0.1.26

2 release files

0.1.25

2 release files

0.1.24

2 release files

0.1.23

2 release files

0.1.22

2 release files

0.1.21

2 release files

0.1.18

2 release files

0.1.17

2 release files

0.1.16

2 release files

0.1.14

2 release files

0.1.13

2 release files

0.1.12

2 release files

0.1.11

2 release files

0.1.10

2 release files

0.1.9

2 release files

0.1.8

2 release files

0.1.7

2 release files

0.1.6

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page