valent-pipeline 0.1.5 → 0.1.6

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "valent-pipeline",
-  "version": "0.1.5",
+  "version": "0.1.6",
   "description": "v3 multi-agent AI pipeline for software development lifecycle",
   "type": "module",
   "bin": {

package/skills/v3-setup-backlog/SKILL.md

@@ -137,9 +137,11 @@ As a {role} I want {capability} so that {benefit}.
 
 ## Step 7: Initialize Knowledge Base
 
-Scan the repo to build the curated knowledge files that the Knowledge Agent uses at runtime. Write these to `knowledge/curated/`:
+Scan the repo to build the curated knowledge files that the Knowledge Agent uses at runtime. Write these to `knowledge/curated/`.
 
-### `project-context.md`
+**Use haiku subagents in parallel** to scan the repo efficiently. Launch up to 3 agents simultaneously, each responsible for one knowledge file:
+
+**Agent 1 → `project-context.md`:**
 Scan the repo and generate:
 - Project name and purpose (from README, package.json, or ask the user)
 - Directory layout (top-level structure)
@@ -148,7 +150,7 @@ Scan the repo and generate:
 - Existing API endpoints (from route files if present)
 - Environment setup (from docker-compose, Dockerfile, .env.example if present)
 
-### `code-conventions.md`
+**Agent 2 → `code-conventions.md`:**
 Scan existing source code and extract:
 - Import patterns (ESM vs CJS, path aliases)
 - Naming conventions (camelCase, snake_case, file naming)
@@ -157,14 +159,16 @@ Scan existing source code and extract:
 - Error handling patterns
 - Any linting config (.eslintrc, .prettierrc, biome.json)
 
-### `api-reference.md` (if API endpoints exist)
+**Agent 3 → `api-reference.md`** (only if API endpoints exist):
 Scan route files and generate:
 - Method, path, request/response shapes
 - Validation rules
 - Auth requirements
 - Status codes
 
-If the repo is empty or brand new (no source code yet), create minimal placeholder files noting "No existing code detected — Knowledge Agent will update these as stories ship."
+All three agents run in parallel using `model: "haiku"` to minimize cost. Collect their outputs and write the files.
+
+If the repo is empty or brand new (no source code yet), skip the subagents and create minimal placeholder files noting "No existing code detected — Knowledge Agent will update these as stories ship."
 
 ## Step 8: Report
 

package/src/commands/init.js

@@ -79,7 +79,20 @@ export async function init(options = {}) {
     console.log('  SQLite knowledge mode selected. Run "valent-pipeline db init" to create the database.');
   }
 
-  // 8. Update .gitignore
+  // 8. Configure Claude settings for agent teams
+  const claudeSettingsPath = join(projectRoot, '.claude', 'settings.json');
+  let claudeSettings = {};
+  if (fileExists(claudeSettingsPath)) {
+    try {
+      claudeSettings = JSON.parse(readFile(claudeSettingsPath));
+    } catch { /* start fresh if parse fails */ }
+  }
+  if (!claudeSettings.env) claudeSettings.env = {};
+  claudeSettings.env.CLAUDE_CODE_ENABLE_EXPERIMENTAL_AGENT_TEAMS = '1';
+  writeFileSafe(claudeSettingsPath, JSON.stringify(claudeSettings, null, 2) + '\n');
+  console.log('  Configured .claude/settings.json (agent teams enabled)');
+
+  // 9. Update .gitignore
   appendToGitignore(projectRoot, 'v3/pipeline.db');
   appendToGitignore(projectRoot, 'v3/pipeline.db-*');
   appendToGitignore(projectRoot, 'v3/chromadb-data/');