@dzhechkov/harness-cli 0.2.1 → 0.2.3

package/README.md

@@ -94,6 +94,172 @@ dz workflow --task security-audit    # adversarial security scan
 - `dz doctor` runs 7 health checks (node version, adapters, config, SQLite, skills)
 - `dz migrate` detects legacy keysarium/bto installations and recommends migration path
 
+---
+
+## Use Cases
+
+### 1. Short-term product research (one-off study)
+
+**Goal:** Quickly research a product idea, competitors, market — get a structured report.
+
+```bash
+# Option A: via dz CLI
+dz init --target claude-code --preset meta
+# Then in Claude Code:
+#   /explore "Research the market for AI-powered code review tools"
+#   /feature-adr "Summarize findings into an ADR"
+
+# Option B: via keysarium (full 7-phase pipeline)
+npx @dzhechkov/keysarium init
+# Then in Claude Code:
+#   /casarium "AI-powered code review tools — market analysis"
+#   → Phase 0: Discovery → Phase 1: Exploration → Phase 2: Paranoid Research
+#   → Phase 3: Solution Design → Phase 4: Architecture → Phase 5: Presentation
+```
+
+**What you get:**
+- `meta` preset: `/explore` clarifies the problem → `/feature-adr` structures findings as ADR decisions
+- `keysarium`: full 7-phase pipeline with dream cycles, background workers, and presentation generation
+
+**Best for:** Quick study (hours), competitive analysis, technology evaluation.
+
+---
+
+### 2. Long-term product research (evolving over time)
+
+**Goal:** Continuously gather data, add new sources, and "recalculate" the product vision as insights accumulate.
+
+```bash
+# Install keysarium (research pipeline) + evidence-wiki (knowledge base)
+npx @dzhechkov/keysarium init
+# Copy evidence-wiki plugin into your project:
+npx @dzhechkov/evidence-wiki   # or git clone https://github.com/djd1m/evidence-wiki
+
+npm install -g @dzhechkov/harness-cli
+dz init --target claude-code --preset meta
+```
+
+**Workflow — iterative research cycles with evidence wiki:**
+
+```
+Week 1:  /casarium "Product X — initial research"
+         → researches/ directory created with findings
+         → .keysarium/memory/ stores patterns + reward scores
+
+         /wiki-generate                              ← evidence-wiki
+         → Scans researches/, ADRs, docs
+         → Generates wiki/concepts/*.md (atomic pages with inline sources)
+         → Builds wiki/graph.json (knowledge graph)
+         → wiki/INDEX.md links everything
+
+Week 2:  Add new data → /casarium "Product X — update with Q2 metrics"
+         → Memory recalls Week 1 patterns (reward-calibrated learning)
+         → New findings merged with existing, conflicts resolved
+
+         /wiki-generate --check                      ← re-generates wiki
+         → New concepts added, existing updated
+         → Every claim verified: triple-pillar protocol requires N independent
+           typed sources (ADR + methodology + research)
+         → Stale concepts flagged, broken evidence links detected
+
+         /triple-check wiki/concepts/pricing-model.md ← verify specific page
+         → Checks that every factual claim has inline source citations
+         → Flags unsupported statements
+
+Week N:  /casarium "Product X — pivot analysis after customer feedback"
+         → Full history in memory layer + evidence wiki
+         → /harvest extracts reusable knowledge patterns
+         → /wiki-generate rebuilds the entire knowledge graph
+         → Product vision "recalculated" — the wiki IS the living product model
+```
+
+**The evidence-wiki advantage:**
+
+| Without evidence-wiki | With evidence-wiki |
+|----------------------|-------------------|
+| Research in markdown files | Atomic concept pages with inline sources |
+| Findings scattered across `researches/` | Interlinked knowledge graph (`graph.json`) |
+| "I think we decided X" | Every claim has a cited source (triple-pillar) |
+| Hard to see what changed | `/wiki-generate --check` diffs the knowledge base |
+| No verification | `/triple-check` enforces evidence discipline |
+
+**Key features for long-term research:**
+- **Evidence wiki** (`@dzhechkov/evidence-wiki`): atomic concept pages where every factual claim carries inline sources; knowledge graph for cross-referencing; triple-pillar protocol (N independent typed sources per claim)
+- **Reward-calibrated memory** (`@dzhechkov/memory` Reflexion): each checkpoint response trains the system — "ок" = excellent (1.0), feedback = good (0.7), rework = needs_work (0.3)
+- **Agent SDK Dreaming**: between sessions, patterns are consolidated and distilled
+- **`/harvest`** (knowledge-extractor skill): extracts reusable patterns from completed research into `lib/` templates
+- **SQLite + FTS5 backend**: scales to 100k+ records with full-text search across all research sessions
+
+**Best for:** Product strategy over months, continuous market monitoring, evolving product vision with evidence-backed decisions.
+
+---
+
+### 3. Product research + working prototype
+
+**Goal:** Research the product AND build a functional prototype.
+
+#### Option A: Sequential — research first, then code
+
+```bash
+# Step 1: Install research + development presets
+npx @dzhechkov/keysarium init
+# OR:
+dz init --target claude-code --preset keysarium
+
+# Step 2: Research phase
+#   /casarium "SaaS platform for team retrospectives"
+#   → Phase 0-2: Discovery, Exploration, Paranoid Research
+#   → Phase 3: Solution Design (with CJM prototype)
+#   → Result: researches/<slug>/ with full analysis
+
+# Step 3: Switch to development
+dz init --target claude-code --preset feature-adr
+
+# Step 4: Build using research outputs
+#   /feature-adr "Build the retrospective platform based on research in researches/<slug>/"
+#   → Step 0: Router classifies as L/XL
+#   → Step 1-5: Requirements, ADRs, DDD, Architecture (informed by research)
+#   → Step 6: Implementation plan
+#   → Step 7: Code generation (with /frontend-design for UI)
+#   → Step 8-9: QE review + fleet assessment
+```
+
+**What you get:** Research artifacts in `researches/`, then code in `features/<slug>/` + actual repository changes. Research directly feeds into ADR decisions.
+
+#### Option B: Parallel — research and code simultaneously with p-replicator
+
+```bash
+# Install the full product development toolkit
+npx @dzhechkov/p-replicator init
+
+# Single pipeline: research → requirements → prototype
+#   /replicate "SaaS platform for team retrospectives"
+#   → Reverse-engineers similar products (reverse-engineering-unicorn)
+#   → Generates SPARC PRD (sparc-prd-mini)
+#   → Validates requirements (requirements-validator)
+#   → Creates the project structure (pipeline-forge)
+#   → Builds the prototype (cc-toolkit-generator-enhanced)
+#   → Reviews with brutal honesty (brutal-honesty-review)
+```
+
+**What you get:** A working prototype generated from research in a single `/replicate` pipeline run. Faster but less deep than Option A.
+
+#### Comparison
+
+| Aspect | Option A (Sequential) | Option B (p-replicator) |
+|--------|----------------------|------------------------|
+| **Research depth** | Deep (7-phase keysarium) | Moderate (reverse-engineering) |
+| **Code quality** | High (11-step feature-adr + QE) | Good (pipeline-forge + review) |
+| **Time** | Days to weeks | Hours to days |
+| **Best for** | Complex products, regulated domains | MVPs, hackathons, quick validation |
+| **Packages** | `keysarium` + `feature-adr` preset | `p-replicator` |
+| **Research artifacts** | `researches/` directory | Embedded in PRD |
+| **Code artifacts** | `features/<slug>/` + repo changes | Generated project |
+
+**Tip:** For maximum rigor, combine both — use `p-replicator` for a quick prototype, then run `/feature-adr --full-qe-extended` on the generated code for production-grade quality engineering.
+
+---
+
 ## Status
 
-`v0.2.0` — published on npm. Part of [DZ Harness Hub](https://github.com/djd1m/dz-harness-hub).
+`v0.2.1` — published on npm. Part of [DZ Harness Hub](https://github.com/djd1m/dz-harness-hub).

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@dzhechkov/harness-cli",
-  "version": "0.2.1",
+  "version": "0.2.3",
   "description": "The dz CLI — install AI skills for Claude Code, Codex, OpenCode, Hermes. 11 commands, 7 presets, 4 platform adapters.",
   "type": "module",
   "license": "MIT",