prjct-cli 2.76.2 → 3.0.0

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/CHANGELOG.md CHANGED
@@ -2,41 +2,46 @@
2
2
 
3
3
  ## [Unreleased]
4
4
 
5
+ ## [3.0.0] - 2026-06-26
6
+
7
+ ### Added
8
+ - v3.0 AI Agile OS second brain context refresh
9
+
10
+ ## [2.77.0] - 2026-06-26
11
+
12
+ ### Added
13
+ - context quality cleanup
14
+
5
15
  ## [2.76.2] - 2026-06-26
6
16
 
7
17
  ### Bug Fixes
8
18
 
9
19
  - vault regen self-heals missing files (no more stale-complete vault) (#476)
10
20
 
11
-
12
21
  ## [2.76.1] - 2026-06-26
13
22
 
14
23
  ### Bug Fixes
15
24
 
16
25
  - prjct sync regenerates the vault (was leaving it stale) (#475)
17
26
 
18
-
19
27
  ## [2.76.0] - 2026-06-26
20
28
 
21
29
  ### Features
22
30
 
23
31
  - project context RAG — the history of contexts (context is gold) (#474)
24
32
 
25
-
26
33
  ## [2.75.0] - 2026-06-26
27
34
 
28
35
  ### Features
29
36
 
30
37
  - deterministic project id, stable deviceId, local-safe sync (#473)
31
38
 
32
-
33
39
  ## [2.74.0] - 2026-06-26
34
40
 
35
41
  ### Features
36
42
 
37
43
  - sync specs + full analysis to the cloud vault (#472)
38
44
 
39
-
40
45
  ## [2.73.0] - 2026-06-25
41
46
 
42
47
  ### Added
package/README.md CHANGED
@@ -1,6 +1,9 @@
1
1
  # prjct-cli
2
2
 
3
- **Project memory + quality workflows for AI coding agents.** prjct-cli gives Claude Code (and any agent) durable memory of your projects: decisions, learnings, gotchas, hot files, recurring bugs. Plus 5 named quality workflows (review, qa, security, investigate, ship) that persist findings back to memory so the next session compounds.
3
+ **AI Agile OS for coding agents.** prjct-cli gives Claude Code, Codex, Gemini,
4
+ Cursor, Windsurf, and any agent a project second brain: intent briefs, bounded
5
+ RAG context, preventive guardrails, synthesized learning, and performance
6
+ signals for each dev+LLM work cycle.
4
7
 
5
8
  [![npm](https://img.shields.io/npm/v/prjct-cli)](https://www.npmjs.com/package/prjct-cli)
6
9
  [![Claude Code](https://img.shields.io/badge/Claude%20Code-Ready-6366f1)]()
@@ -174,10 +177,11 @@ Use `prjct agents doctor --fix` inside a prjct project to refresh the portable
174
177
  `AGENTS.md` surface and any repo-local IDE rule adapters prjct manages. The
175
178
  command is idempotent and reports what changed.
176
179
 
177
- ## Value proof commands
180
+ ## AI Agile intelligence
178
181
 
179
182
  prjct should justify itself with project evidence, not vague claims. These
180
- read-only commands show whether the project is actually compounding:
183
+ read-only commands show whether dev+LLM work cycles are getting cheaper,
184
+ safer, and more precise:
181
185
 
182
186
  ### Version evals
183
187
 
@@ -198,11 +202,12 @@ checks. See [EVALS.md](./EVALS.md) for the full workflow.
198
202
 
199
203
  | Command | What it proves |
200
204
  |---|---|
201
- | `prjct value --md` | Durable memory, preventive guardrails, shipped work, sync metrics, and detected agent coverage. |
202
- | `prjct memory-doctor --md` | Duplicate, stale, low-signal, or untyped memories before they poison recall. |
203
- | `prjct report 7 --md` | A human weekly report from shipped features, completed tasks, and carry-forward lessons. |
204
- | `prjct handoff codex --md` | A takeover prompt for the next agent with the checks it should run first. |
205
- | `prjct guardrails --md` | File-specific warnings for the current changeset from preventive memory. |
205
+ | `prjct insights value --md` | Durable memory, preventive guardrails, shipped work, sync metrics, and detected agent coverage. |
206
+ | `prjct insights quality --md` | Duplicate, stale, low-signal, or untyped memories before they poison recall. |
207
+ | `prjct insights report 7 --md` | A human/team report from shipped work and carry-forward lessons. |
208
+ | `prjct insights continue codex --md` | A continuation brief for the next agent with checks it should run first. |
209
+ | `prjct insights guardrails --md` | File-specific warnings for the current changeset from preventive memory. |
210
+ | `prjct performance 14 --md` | Time, tokens, model/runtime, prompt synthesis, tools, outcome, and quality signals per work cycle where available. |
206
211
 
207
212
  ## Execution environments (zero-config)
208
213
 
@@ -213,9 +218,9 @@ The same binary runs in a plain shell, inside Claude Code, in an OpenAI Codex sa
213
218
  In a real terminal — branded, animated, colored:
214
219
 
215
220
  ```text
216
- $ prjct task "add OAuth refresh"
217
- ⚡ prjct ✓ Task started: add OAuth refresh
218
- branch: task/add-oauth-refresh · status: active
221
+ $ prjct work "add OAuth refresh"
222
+ ⚡ prjct ✓ Work cycle started: add OAuth refresh
223
+ branch: work/add-oauth-refresh · status: active
219
224
  harness: H2 feature/medium · evidence: focused-tests, scope-check, spec-or-design
220
225
  ```
221
226
 
@@ -224,9 +229,9 @@ animation), so logs stay clean. With `--md`, output is plain markdown an agent
224
229
  can consume directly:
225
230
 
226
231
  ```text
227
- $ prjct task "add OAuth refresh" --md
228
- > Task started: **add OAuth refresh**
229
- > branch `task/add-oauth-refresh` · status `active`
232
+ $ prjct work "add OAuth refresh" --md
233
+ > Work cycle started: **add OAuth refresh**
234
+ > branch `work/add-oauth-refresh` · status `active`
230
235
  > harness `H2 feature/medium` · evidence `focused-tests, scope-check, spec-or-design`
231
236
  ```
232
237
 
@@ -235,9 +240,9 @@ $ prjct task "add OAuth refresh" --md
235
240
  ```bash
236
241
  # In any git repo
237
242
  prjct sync # register the project (auto on first prjct command)
238
- prjct task "add OAuth refresh" # start tracking work
243
+ prjct work "add OAuth refresh" # start an AI Agile work cycle
239
244
  prjct remember decision "we chose JWT + refresh rotation"
240
- prjct status done # close the active task
245
+ prjct remember context "implemented refresh rotation; model/tokens unknown; tests passed"
241
246
  prjct ship # bump version, commit, push, open PR
242
247
  ```
243
248
 
@@ -255,38 +260,36 @@ prjct team --enforce # pre-commit hook blocks commits without prjc
255
260
  ## Inside Claude Code / Gemini CLI
256
261
 
257
262
  ```bash
258
- p. capture "llamar a Ana re: pricing" # GTD inbox anything goes
259
- p. task "add OAuth refresh" # start tracking work
263
+ p. remember context "call Ana re pricing; no work cycle yet"
264
+ p. work "add OAuth refresh" # start an AI Agile work cycle
260
265
  p. remember decision "we chose JWT + refresh rotation"
261
- p. status done # close the active task
266
+ p. performance 7 # inspect dev+LLM efficiency
262
267
  p. ship # commit, push, open PR
263
268
  ```
264
269
 
265
270
  Cursor and Windsurf use their installed prjct router files; otherwise run `prjct <command> --md` and follow the output.
266
271
 
267
- ### Core verbs
272
+ ### AI Agile verbs
268
273
 
269
274
  | Verb | What it does |
270
275
  |---|---|
271
- | `prjct capture "<text>"` | GTD-style universal inbox. Bare `prjct "<text>"` also routes here. |
272
- | `prjct task ["<desc>"]` | Register a task or show the active one. |
273
- | `prjct status <value>` | Inline status change on the active task (`done`, `paused`, `active`, …). |
274
- | `prjct tag <k:v>` | Tag the active task (`type:bug`, `domain:auth`, …). |
276
+ | `prjct intent "<title>"` | Frame objective, constraints, risks, and success signal before high-stakes work. |
277
+ | `prjct work ["<intent>"]` | Start or inspect an AI Agile work cycle with context and evidence. |
275
278
  | `prjct remember <type> "<content>"` | Persist a memory entry (decision, learning, gotcha, …). |
276
279
  | `prjct forget <id>` | Delete a memory entry by id (`prjct forget mem_1234`) — the delete half of `remember`. |
277
280
  | `prjct search "<query>"` | Search project memory — blended BM25 + semantic + recency recall (`prjct search mem_1234` resolves an entry by id). |
278
- | `prjct embeddings <set\|status\|test\|clear>` | Configure the global BYOT embeddings provider any OpenAI-compatible API (OpenAI, OpenRouter, Ollama, Azure, …), one secure key, all projects. |
281
+ | `prjct guard <file>` | Surface preventive memory before editing a risky file. |
282
+ | `prjct performance [days]` | Measure dev+LLM efficiency per work cycle. |
283
+ | `prjct insights [value\|quality\|report\|continue\|guardrails]` | Project intelligence and quality proof. |
279
284
  | `prjct ship [name]` | Run the project's ship workflow (commit, push, PR, persist). |
280
285
  | `prjct sync` | Re-index files, git co-change, imports; refresh project analysis. |
281
- | `prjct regen` | Full rebuild of the Obsidian vault snapshot from SQLite. |
282
- | `prjct value` | Show whether prjct is paying for itself in this project. |
283
- | `prjct memory-doctor` | Audit memory quality before noisy context spreads to every agent. |
284
- | `prjct report [days]` | Generate a human report from shipped work and project memory. |
285
- | `prjct handoff [agent]` | Prepare the next AI coding agent to continue with context. |
286
- | `prjct guardrails` | Check the current changeset against known project traps. |
287
286
  | `prjct agents doctor` | Show the auditable compatibility matrix for local and project agent runtimes. |
288
287
  | `prjct review-risk` | Advisory change-size + delivery-geometry signal for the branch (read-only; never gates, never splits). |
289
- | `prjct seed <add\|list>` | Manage packs (persona, memory types, workflow slots). |
288
+
289
+ Compatibility aliases from v2 still execute for existing scripts: `task`,
290
+ `status`, `tag`, `capture`, `spec`, `audit-spec`, `value`, `memory-doctor`,
291
+ `report`, `handoff`, `guardrails`, `regen`, and `analyze`. They are no longer
292
+ the product surface.
290
293
 
291
294
  ## Personas & Packs
292
295
 
@@ -518,23 +521,27 @@ In any git repo, run `prjct sync` (it auto-runs on the first `prjct` command) or
518
521
  `prjct init`. This creates `.prjct/prjct.config.json` with a `projectId`, builds
519
522
  the SQLite store at `~/.prjct-cli/projects/<projectId>/`, and generates the vault.
520
523
 
521
- **How do I add a development task?**
522
- Run `prjct task "<description>"` from the repo. It registers the task in SQLite,
523
- auto-classifies a lightweight harness (H0-H3) with expected evidence, and marks
524
- it active — worked example:
524
+ **How do I start an AI Agile work cycle?**
525
+ Run `prjct work "<intent>"` from the repo. It registers the work cycle in
526
+ SQLite, pulls relevant second-brain context, auto-classifies a lightweight
527
+ harness (H0-H3) with expected evidence, and marks it active — worked example:
525
528
 
526
529
  ```bash
527
- $ prjct task "add OAuth refresh"
528
- ⚡ prjct ✓ Task started: add OAuth refresh
529
- branch: task/add-oauth-refresh · status: active
530
+ $ prjct work "add OAuth refresh"
531
+ ⚡ prjct ✓ Work started: add OAuth refresh
532
+ branch: work/add-oauth-refresh · status: active
530
533
  harness: H2 feature/medium · evidence: focused-tests, scope-check, spec-or-design
531
534
 
532
- $ prjct tag type:feature domain:auth # optional: categorize it
533
- $ prjct status done # closes it; warns if harness evidence is missing
535
+ $ prjct remember context "OAuth refresh depends on the existing token rotation helper."
536
+ $ prjct performance --md # duration/tokens/model/runtime when available
534
537
  $ prjct ship # bump version, commit, PR
535
538
  ```
536
539
 
537
- Inside an agent you can say it: `p. task "add OAuth refresh"` in Claude Code, or run `prjct task "…" --md` from any wired agent. `prjct task` with no argument prints the currently active task.
540
+ Inside an agent you can say it: `p. work "add OAuth refresh"` in Claude Code,
541
+ or run `prjct work "..." --md` from any wired agent. `prjct work` with no
542
+ argument prints the currently active work cycle. The old `task/status/tag/spec`
543
+ verbs still execute for existing scripts, but they are compatibility aliases,
544
+ not the v3 product model.
538
545
 
539
546
  **How do I get AI assistance for a coding problem?**
540
547
  Inside Claude Code (or any wired agent) describe the problem in natural
@@ -549,9 +556,10 @@ persisting findings to memory. Concrete examples:
549
556
  | "qa the checkout page" | `qa` | Real browser, atomic fixes, regression tests |
550
557
 
551
558
  You can also pull project knowledge directly: ask "what patterns does this
552
- project use?" and the agent reads `<vault-root>/<slug>/_generated/patterns.md`
553
- instead of grepping source (the lookup-first protocol). Outside an agent, every
554
- command takes `--md` to emit agent-ready markdown.
559
+ project use?" and the agent runs `prjct search`, `prjct context memory`, or
560
+ `prjct guard` before reading source. The generated vault is a snapshot fallback;
561
+ the fast path is SQLite + retrieval so agents do not flood their context.
562
+ Outside an agent, every command takes `--md` to emit agent-ready markdown.
555
563
 
556
564
  **What does prjct-cli output look like in a normal terminal?**
557
565
  A branded, **animated** spinner with full colors and interactive prompts (the