@kaddo/cli 3.117.0 → 3.119.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/README.md CHANGED
@@ -61,7 +61,12 @@ a conclusion.
61
61
  kaddo init --mode poc
62
62
  # or change an existing project
63
63
  kaddo project mode poc
64
- kaddo bootstrap
64
+ kaddo add agents
65
+ kaddo add skills
66
+ # define the hypothesis and success criteria in knowledge/delivery/poc.md
67
+ kaddo context
68
+ kaddo understand
69
+ kaddo create spike
65
70
  ```
66
71
 
67
72
  The canonical record is `knowledge/delivery/poc.md`. It concludes as `validated`, `rejected`, or
@@ -69,6 +74,18 @@ The canonical record is `knowledge/delivery/poc.md`. It concludes as `validated`
69
74
  first experiment. Token savings can result from this focused context, but the goal is better
70
75
  evidence and decisions, not prompt optimization.
71
76
 
77
+ POC mode does not require the standard Business/Product knowledge baseline. Add technical context
78
+ or Project Resources only when they are relevant to the experiment.
79
+
80
+ Install the agent prompts and reusable skills as part of the initial POC setup. They provide the
81
+ guided refinement and implementation context; they do not add a Business/Product baseline.
82
+
83
+ After recording `validated`, `rejected`, or `inconclusive`, run `kaddo poc report` to prepare a
84
+ deterministic, source-attributed final-report handoff. The report is optional; a reviewed proposal
85
+ is persisted only with confirmation as immutable `knowledge/delivery/poc-report-v001.md` (later
86
+ versions never overwrite earlier ones). It is `missing`, `current`, or `stale` based on a source
87
+ fingerprint; new evidence never regenerates it automatically.
88
+
72
89
  ## The Knowledge Model
73
90
 
74
91
  Kaddo organizes project knowledge into four layers under `knowledge/`: