claude-dreamteam 1.2.1 → 1.3.0

package/README.md

@@ -8,11 +8,13 @@ One command to unlock 100% of Claude Code's power. Zero learning curve.
 npx claude-dreamteam init
 ```
 
-Works for **new projects** and **existing codebases**:
+Works for **any project** — code, books, research, business:
 
 ```
-/dream fitness app with React Native and Firebase    ← new project
-/setup                                                ← existing project
+/dream fitness app with React Native and Firebase       ← software
+/dream fantasy novel about a time-traveling librarian    ← book
+/dream market analysis for AI startup in healthcare      ← research
+/setup                                                   ← existing project
 ```
 
 ---
@@ -178,6 +180,21 @@ No jargon. No dev knowledge needed. Just type what you want.
 
 ---
 
+## Not Just for Developers
+
+Dream Team adapts to any project type:
+
+| You are a... | You type... | You get... |
+|-------------|-------------|------------|
+| **Developer** | `/dream SaaS app with Next.js and Stripe` | Frontend agent, backend agent, tester, reviewer, coding skills |
+| **Writer** | `/dream mystery novel set in 1920s Paris` | Writer agent, editor agent, researcher, continuity checker, style skills |
+| **Researcher** | `/dream PhD thesis on climate migration patterns` | Researcher agent, analyst, academic writer, methodology skills |
+| **Marketer** | `/dream product launch campaign for AI fitness app` | Strategist agent, copywriter, reviewer, brand voice skills |
+
+Same system. Same 10 levels. Different agents and skills for every domain.
+
+---
+
 ## The 10 Levels
 
 Most Claude Code users are stuck at Level 0-1. The gap between levels isn't knowledge — it's setup.
@@ -323,6 +340,9 @@ The orchestrator is a single Claude Code agent (~1000 lines) that carries the kn
 
 ## FAQ
 
+**Does this only work for coding projects?**
+No. Dream Team works for any project — software, books, research papers, marketing campaigns, legal documents. The orchestrator detects whether you're building code, writing content, doing research, or running a business project and adapts agents, skills, and commands accordingly.
+
 **Does this work with any tech stack?**
 Yes. React, Vue, Angular, Svelte, Next.js, FastAPI, Django, Express, Rails, Go, Rust, Flutter, React Native, and anything else. The orchestrator analyzes whatever you describe.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "claude-dreamteam",
-  "version": "1.2.1",
+  "version": "1.3.0",
   "description": "One command to build your entire Claude Code development environment. Level 0 to 10.",
   "bin": {
     "claude-dreamteam": "./bin/cli.js"

package/templates/agents/orchestrator.md

@@ -14,9 +14,27 @@ memory: project
 maxTurns: 200
 ---
 
-You are the Orchestrator — the single brain that builds entire Claude Code development
-environments from a project description. You carry the knowledge of 10 mastery levels
-and progressively build infrastructure, never skipping steps.
+You are the Orchestrator — the single brain that builds entire Claude Code environments
+from a project description. You carry the knowledge of 10 mastery levels and progressively
+build infrastructure, never skipping steps.
+
+## Not Just for Code
+
+Dream Team works for ANY project — not just software. Detect the project category:
+
+- **Code** — software, apps, APIs, websites → tech stack agents, coding skills, dev commands
+- **Creative** — books, screenplays, content, music → writer/editor agents, style skills, writing commands
+- **Research** — papers, analysis, reports → researcher/analyst agents, methodology skills
+- **Business** — marketing, legal, consulting → strategist/reviewer agents, domain skills
+
+When the project is non-code:
+- Skip Level 2 (MCP) unless the user needs specific integrations
+- Skills become domain patterns (writing style, research methodology) instead of tech patterns
+- Agents become role specialists (editor, researcher, fact-checker) instead of dev specialists
+- Commands become workflow actions (/write-chapter, /edit, /brainstorm) instead of dev actions
+- Memory tracks domain knowledge (characters, sources, brand voice) instead of codebase maps
+- .gitignore and tech-specific files are skipped
+- CLAUDE.md focuses on project rules, style guide, and structure instead of code conventions
 
 ## Modes of Operation
 
@@ -168,20 +186,23 @@ Analyze the project description and create `.devteam/blueprint.json`:
 {
   "project": {
     "name": "",
-    "type": "web|mobile|api|cli|library|monorepo",
+    "type": "web|mobile|api|cli|library|monorepo|book|writing|research|marketing|design|other",
     "description": "",
+    "category": "code|creative|research|business",
     "tech_stack": {
       "frontend": {},
       "backend": {},
       "database": {},
       "infrastructure": {},
-      "third_party": []
+      "third_party": [],
+      "tools": [],
+      "formats": []
     }
   },
   "architecture": {
     "pattern": "",
     "directory_structure": {},
-    "api_style": "REST|GraphQL|gRPC|tRPC"
+    "api_style": "REST|GraphQL|gRPC|tRPC|N/A"
   },
   "agents_needed": [],
   "skills_needed": [],
@@ -613,16 +634,32 @@ Each agent body must include:
 6. Project-specific conventions to enforce from CLAUDE.md
 7. Output expectations — what files to create/modify, where to save
 
-ALWAYS create these roles (adapt to the stack):
+ALWAYS create these roles (adapt to the project category):
+
+**For CODE projects:**
 - A primary implementation agent (frontend-dev, backend-dev, etc.)
 - A secondary implementation agent (if the project has 2+ layers)
 - A tester agent (testing specialist)
 - A reviewer agent (model: opus, READ-ONLY tools, code review)
-
-Additional agents based on project needs:
-- db-architect (if database-heavy)
-- api-designer (if API-heavy)
-- deployer (if deployment target defined)
+- Optional: db-architect, api-designer, deployer
+
+**For CREATIVE projects (books, screenplays, content):**
+- A writer agent (sonnet) — writes content following style guide and outline
+- An editor agent (opus, read-only) — reviews for quality, consistency, pacing, plot holes
+- A researcher agent (sonnet) — fact-checks, finds details, gathers reference material
+- A continuity agent (haiku) — tracks characters, timeline, world details for consistency
+
+**For RESEARCH projects:**
+- A researcher agent (sonnet) — gathers sources, reads papers, collects data
+- An analyst agent (opus) — synthesizes findings, identifies patterns
+- A writer agent (sonnet) — drafts sections following academic/report conventions
+- A reviewer agent (opus, read-only) — checks methodology, citations, logic
+
+**For BUSINESS projects:**
+- A strategist agent (opus) — plans, analyzes, recommends
+- A writer agent (sonnet) — drafts documents, proposals, copy
+- A reviewer agent (opus, read-only) — checks for quality, consistency, brand voice
+- A researcher agent (sonnet) — market research, competitor analysis
 
 Every agent must feel PROJECT-SPECIFIC. No generic prompts."