valent-pipeline 0.1.4 → 0.1.6

package/package.json

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

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

@@ -135,7 +135,42 @@ As a {role} I want {capability} so that {benefit}.
 - If an AC is vague ("the UI should look good"), flag it and ask the user to clarify or remove it
 - Include error/edge cases as separate ACs, not just happy paths
 
-## Step 7: Report
+## 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/`.
+
+**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)
+- Tech stack (from `v3/pipeline-config.yaml` + detected from package.json, tsconfig, etc.)
+- Database schema (from Prisma schema, migrations, or SQL files if present)
+- Existing API endpoints (from route files if present)
+- Environment setup (from docker-compose, Dockerfile, .env.example if present)
+
+**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)
+- Project structure patterns (routes, services, controllers, etc.)
+- Test file organization and patterns
+- Error handling patterns
+- Any linting config (.eslintrc, .prettierrc, biome.json)
+
+**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
+
+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
 
 After writing all files, summarize:
 
@@ -143,9 +178,13 @@ After writing all files, summarize:
 Created:
   - {backlog_path} ({N} stories)
   - {N} story input files in {story_directory}/
+  - knowledge/curated/project-context.md
+  - knowledge/curated/code-conventions.md
+  - knowledge/curated/api-reference.md (if applicable)
 
 Next steps:
   - Review story files and refine ACs if needed
+  - Review knowledge/curated/ files for accuracy
   - Run /v3-run-story {first-story-id} to start
   - Or run /v3-run-epic {epic-id} to run the whole epic
 ```

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/');