dev-os

A structured AI-assisted development operating system for building production-ready apps — from idea to deployed product using a stage-gated workflow enforced through Claude Code skills.

---

What This Is

dev-os is a Claude Code project that provides a repeatable, stage-by-stage workflow for building full-stack web applications. Each stage has a dedicated skill that Claude runs when invoked. No stage begins until the previous one is approved.

The current application target is ContractIQ — an enterprise AI contract review platform for NDA and MSA analysis.

---

Folder Structure

dev-os/
├── CLAUDE.md                     # Project instructions & stage-gated workflow rules
├── docs/
│   ├── design.md                 # Brand design system (colors, typography, spacing, components)
│   ├── ContractIQ_PRD.md         # Product Requirements Document for ContractIQ
├── skills/                       # Claude Code custom skills (slash commands)
│   ├── engineering-planner/
│   │   └── SKILL.md              # Stage 1: PRD → engineering docs
│   ├── implementation-specs/
│   │   └── SKILL.md              # Stage 2: Engineering docs → granular specs + SQL
│   ├── security-foundation/
│   │   └── SKILL.md              # Stage 3: Specs → security controls + RLS policies
│   ├── frontend-setup/
│   │   └── SKILL.md              # Stage 4: Scaffold Next.js 14 App Router project
│   └── design-system/
│       └── SKILL.md              # Applied during all frontend work — enforces design.md

Files and folders under docs/engineering/, docs/specs/, docs/security/, and .env.example are generated outputs — they are created during the build workflow and do not exist until their respective stage runs.

---

The Build Workflow

Each stage must be completed and approved before the next begins.

---

Skills

Skills live in skills//SKILL.md and are invoked as slash commands in Claude Code.

/engineering-planner

Transforms a PRD into two engineering documents. Asks clarifying questions (auth strategy, DB, LLM provider, user roles) before generating anything. Output is the authoritative reference for all downstream stages.

/implementation-specs