valent-pipeline 0.1.4 → 0.1.5
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json
CHANGED
|
@@ -135,7 +135,38 @@ As a {role} I want {capability} so that {benefit}.
|
|
|
135
135
|
- If an AC is vague ("the UI should look good"), flag it and ask the user to clarify or remove it
|
|
136
136
|
- Include error/edge cases as separate ACs, not just happy paths
|
|
137
137
|
|
|
138
|
-
## Step 7:
|
|
138
|
+
## Step 7: Initialize Knowledge Base
|
|
139
|
+
|
|
140
|
+
Scan the repo to build the curated knowledge files that the Knowledge Agent uses at runtime. Write these to `knowledge/curated/`:
|
|
141
|
+
|
|
142
|
+
### `project-context.md`
|
|
143
|
+
Scan the repo and generate:
|
|
144
|
+
- Project name and purpose (from README, package.json, or ask the user)
|
|
145
|
+
- Directory layout (top-level structure)
|
|
146
|
+
- Tech stack (from `v3/pipeline-config.yaml` + detected from package.json, tsconfig, etc.)
|
|
147
|
+
- Database schema (from Prisma schema, migrations, or SQL files if present)
|
|
148
|
+
- Existing API endpoints (from route files if present)
|
|
149
|
+
- Environment setup (from docker-compose, Dockerfile, .env.example if present)
|
|
150
|
+
|
|
151
|
+
### `code-conventions.md`
|
|
152
|
+
Scan existing source code and extract:
|
|
153
|
+
- Import patterns (ESM vs CJS, path aliases)
|
|
154
|
+
- Naming conventions (camelCase, snake_case, file naming)
|
|
155
|
+
- Project structure patterns (routes, services, controllers, etc.)
|
|
156
|
+
- Test file organization and patterns
|
|
157
|
+
- Error handling patterns
|
|
158
|
+
- Any linting config (.eslintrc, .prettierrc, biome.json)
|
|
159
|
+
|
|
160
|
+
### `api-reference.md` (if API endpoints exist)
|
|
161
|
+
Scan route files and generate:
|
|
162
|
+
- Method, path, request/response shapes
|
|
163
|
+
- Validation rules
|
|
164
|
+
- Auth requirements
|
|
165
|
+
- Status codes
|
|
166
|
+
|
|
167
|
+
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."
|
|
168
|
+
|
|
169
|
+
## Step 8: Report
|
|
139
170
|
|
|
140
171
|
After writing all files, summarize:
|
|
141
172
|
|
|
@@ -143,9 +174,13 @@ After writing all files, summarize:
|
|
|
143
174
|
Created:
|
|
144
175
|
- {backlog_path} ({N} stories)
|
|
145
176
|
- {N} story input files in {story_directory}/
|
|
177
|
+
- knowledge/curated/project-context.md
|
|
178
|
+
- knowledge/curated/code-conventions.md
|
|
179
|
+
- knowledge/curated/api-reference.md (if applicable)
|
|
146
180
|
|
|
147
181
|
Next steps:
|
|
148
182
|
- Review story files and refine ACs if needed
|
|
183
|
+
- Review knowledge/curated/ files for accuracy
|
|
149
184
|
- Run /v3-run-story {first-story-id} to start
|
|
150
185
|
- Or run /v3-run-epic {epic-id} to run the whole epic
|
|
151
186
|
```
|