@really-knows-ai/foundry 1.2.1 → 1.2.2

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
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@really-knows-ai/foundry",
3
- "version": "1.2.1",
3
+ "version": "1.2.2",
4
4
  "description": "A structured framework for AI-driven artefact creation with deterministic routing, quality gates, and iterative refinement cycles.",
5
5
  "type": "module",
6
6
  "main": ".opencode/plugins/foundry.js",
@@ -19,11 +19,33 @@ Before running this skill, verify that the `foundry/` directory exists in the pr
19
19
 
20
20
  1. Read the flow definition from `foundry/flows/<flow-id>.md`
21
21
  2. Create a branch off main: `work/<flow-id>-<short-description>`
22
- 3. Create `WORK.md` in the root following the spec in `docs/work-spec.md`:
23
- - Set frontmatter: flow id, first cycle id, first stage
24
- - Write the goal (from flow definition + human context)
25
- - Empty artefacts table with all four columns: `| File | Type | Cycle | Status |`
26
- - Empty feedback section
22
+ 3. Create `WORK.md` in the project root with this structure:
23
+
24
+ ```markdown
25
+ ---
26
+ flow: <flow-id>
27
+ cycle: <first-cycle-id>
28
+ stages: [<determined by cycle skill>]
29
+ max-iterations: 3
30
+ ---
31
+
32
+ # Goal
33
+
34
+ <goal from flow definition + human context>
35
+
36
+ ## Artefacts
37
+
38
+ | File | Type | Cycle | Status |
39
+ |------|------|-------|--------|
40
+
41
+ ## Feedback
42
+ ```
43
+
44
+ - `flow` — set once, never changes
45
+ - `cycle` — current cycle id, updated when each cycle starts
46
+ - `stages` — the ordered route for the cycle, set by the cycle skill. Each entry uses `base:alias` format (e.g. `forge:write-haiku`, `quench:check-syllables`). Determined from the artefact type: if `validation.md` exists, include `quench`; always include `forge` and `appraise`. `hitl` stages are optional.
47
+ - `max-iterations` — how many forge passes before the cycle is blocked (default: 3, can be overridden in cycle definition)
48
+ - Feedback is grouped under `### <file-path>` sub-headings matching the artefact's File column. See the quench and appraise skills for the format.
27
49
  4. Execute each foundry cycle in order by reading its definition from `foundry/cycles/<cycle-id>.md`
28
50
  5. Update the frontmatter cursor as each foundry cycle starts (set `cycle` to the new cycle id)
29
51
  6. When all foundry cycles are done, delete WORK.md — the artefacts and git history are the record