Droidz

🥈Silver

Droidz is an AI automation skill that enables spec-driven development for software teams. It provides structured workflows and standards, reducing context loss and ad-hoc prompting. Operations teams can integrate Droidz with Claude to streamline development processes and improve software quality.

93100Updated 1mo ago

Intermediate30min to implementautomation

Quick InstallView Source

git clone https://github.com/korallis/Droidz.git

Works with:

Claude

Overview

About This Skill

How to Use

1. **Initialize the spec**: Run `droidz init --project [PROJECT_NAME] --template [TEMPLATE_TYPE]` in your terminal to generate a base spec file. Replace placeholders with your actual requirements and tech stack. 2. **Validate the spec**: Use `droidz validate --spec spec.yaml` to check for completeness. Fix any missing fields or broken references before proceeding. 3. **Generate artifacts**: Run `droidz generate --spec spec.yaml --output ./src` to create code skeletons, test files, and documentation templates aligned with your spec. 4. **Integrate with CI/CD**: Add `droidz lint --spec spec.yaml` to your GitHub Actions workflow to enforce spec compliance on every PR. Configure auto-rollback triggers in your deployment pipeline. 5. **Iterate with feedback**: Use `droidz diff --spec spec.yaml --last-commit` to identify changes between spec versions. Update requirements based on stakeholder feedback and regenerate artifacts as needed. Tip: Use Droidz's `spec:trace` command to generate visual traceability diagrams for stakeholder reviews.

Setup & Installation

Quick Install

No install command available. Check the GitHub repository for manual installation instructions.

Alternative Install (Git Clone)

git clone https://github.com/korallis/Droidz

Requirements

Claude Code or compatible AI agent
Works with: Claude

Quick Start Guide

Install the Skill

Copy the install command above and run it in your terminal.

Open Your AI Agent

Launch Claude Code, Cursor, or your preferred AI coding agent.

Try It Out

Use the prompt template or examples below to test the skill.

Customize

Adapt the skill to your specific use case and workflow.

Usage Examples

Prompt Template

Generate a spec-driven development plan for [PROJECT_NAME] using Droidz standards. Include: 1) A clear project scope with [REQUIREMENTS_LIST], 2) A modular architecture breakdown with [TECH_STACK] components, 3) Implementation milestones with [DEADLINES], 4) Testing strategy with [TEST_TYPES], and 5) Rollback/backup procedures. Ensure all outputs follow Droidz spec format and include traceability links between requirements and code artifacts.

Example Output

## Droidz Spec-Driven Development Plan: **Customer Portal Redesign**

### 1. Project Scope
**Primary Objective**: Redesign the customer portal to reduce support tickets by 30% while improving load times by 40%. 
**Requirements**: 
- R1: Implement single-sign-on (SSO) with existing identity provider (Okta) by Q3
- R2: Reduce average page load time from 4.2s to <2.5s
- R3: Add dark mode toggle with persistent user preference
- R4: Integrate real-time chat widget with response time <30s

### 2. Modular Architecture
**Frontend**: React 18 + TypeScript + TailwindCSS (modular component library)
**Backend**: Node.js (Express) + PostgreSQL (read replicas for analytics)
**Infrastructure**: Kubernetes cluster with GitOps (ArgoCD) for deployments

**Module Breakdown**:
- auth-service (handles SSO flows)
- analytics-service (tracks performance metrics)
- ui-components (shared design system)
- chat-service (WebSocket integration)

### 3. Implementation Milestones
| Milestone | Date | Dependencies | Acceptance Criteria |
|-----------|------|--------------|---------------------|
| M1: SSO Integration | 2024-07-15 | Okta API access | Successful token exchange in staging |
| M2: Performance Baseline | 2024-07-22 | M1 complete | Lighthouse score ≥90 on core pages |
| M3: Dark Mode UI | 2024-08-05 | M2 complete | Theme persistence across sessions |
| M4: Chat Widget | 2024-08-19 | M3 complete | Avg response time <30s in load testing |

### 4. Testing Strategy
**Unit Tests**: Jest covering 90%+ of business logic (enforced via CI)
**Integration Tests**: Cypress for E2E flows (login, payment checkout)
**Performance Tests**: k6 for load testing (simulate 1000 concurrent users)
**Security Tests**: OWASP ZAP scans before each release

### 5. Rollback Procedures
**Automated Rollback**: If error rate >1% in production for >5min, trigger ArgoCD sync to previous stable version
**Manual Rollback**: Maintain last 3 Git tags in GitHub for emergency rollbacks
**Communication Plan**: Slack #alerts channel + PagerDuty for critical issues

**Traceability Matrix**:
| Requirement | Code Artifact | Test Case | Deployment |
|-------------|---------------|-----------|------------|
| R1 | /services/auth | auth.test.js | auth-service:v1.2.3 |
| R2 | /components/Layout | performance.test.js | portal:v2.1.0 |

All artifacts are linked in the Droidz spec repository with commit hashes for full traceability.