opencode-plugin-flow 4.1.14 → 4.1.16
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 +8 -0
- package/README.md +9 -9
- package/dist/cli.js +120 -102
- package/dist/index.js +116 -98
- package/dist/index.js.map +4 -4
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -3,6 +3,14 @@
|
|
|
3
3
|
One short line per release. For the full rationale behind each entry, see the
|
|
4
4
|
commit history and review evidence.
|
|
5
5
|
|
|
6
|
+
## [4.1.16] - 2026-06-22
|
|
7
|
+
|
|
8
|
+
Quote Flow skill frontmatter lore so GitHub previews parse cleanly and CI guards future YAML slips.
|
|
9
|
+
|
|
10
|
+
## [4.1.15] - 2026-06-22
|
|
11
|
+
|
|
12
|
+
Refine Flow's orchestration lore into a quick path, bundled wave example, tested doc links, and trusted-publishing release guidance.
|
|
13
|
+
|
|
6
14
|
## [4.1.14] - 2026-06-22
|
|
7
15
|
|
|
8
16
|
Publish Flow through npm trusted publishing so release CI no longer depends on expiring npm tokens.
|
package/README.md
CHANGED
|
@@ -21,8 +21,8 @@ The manager still owns every Flow state change. Workers gather evidence; they do
|
|
|
21
21
|
Use OpenCode's plugin installer when your OpenCode version supports it:
|
|
22
22
|
|
|
23
23
|
```bash
|
|
24
|
-
opencode plugin opencode-plugin-flow@4.1.
|
|
25
|
-
npx -y opencode-plugin-flow@4.1.
|
|
24
|
+
opencode plugin opencode-plugin-flow@4.1.16 --global --force
|
|
25
|
+
npx -y opencode-plugin-flow@4.1.16 sync
|
|
26
26
|
```
|
|
27
27
|
|
|
28
28
|
The first command adds Flow to your global OpenCode plugin config or replaces an
|
|
@@ -48,7 +48,7 @@ OpenCode config manually instead:
|
|
|
48
48
|
|
|
49
49
|
```json
|
|
50
50
|
{
|
|
51
|
-
"plugin": ["opencode-plugin-flow@4.1.
|
|
51
|
+
"plugin": ["opencode-plugin-flow@4.1.16"]
|
|
52
52
|
}
|
|
53
53
|
```
|
|
54
54
|
|
|
@@ -59,7 +59,7 @@ duplicate entry.
|
|
|
59
59
|
Then run the same pre-start skill sync and start or restart OpenCode:
|
|
60
60
|
|
|
61
61
|
```bash
|
|
62
|
-
npx -y opencode-plugin-flow@4.1.
|
|
62
|
+
npx -y opencode-plugin-flow@4.1.16 sync
|
|
63
63
|
```
|
|
64
64
|
|
|
65
65
|
Project-local skill overrides still work through OpenCode's normal lookup:
|
|
@@ -84,15 +84,15 @@ version in your global `opencode.json`.
|
|
|
84
84
|
To inspect the installed skill set:
|
|
85
85
|
|
|
86
86
|
```bash
|
|
87
|
-
npx -y opencode-plugin-flow@4.1.
|
|
87
|
+
npx -y opencode-plugin-flow@4.1.16 doctor
|
|
88
88
|
```
|
|
89
89
|
|
|
90
90
|
For automation, keep the default human-readable `doctor` output and opt into
|
|
91
91
|
machine behavior explicitly:
|
|
92
92
|
|
|
93
93
|
```bash
|
|
94
|
-
npx -y opencode-plugin-flow@4.1.
|
|
95
|
-
npx -y opencode-plugin-flow@4.1.
|
|
94
|
+
npx -y opencode-plugin-flow@4.1.16 doctor --json
|
|
95
|
+
npx -y opencode-plugin-flow@4.1.16 doctor --check
|
|
96
96
|
```
|
|
97
97
|
|
|
98
98
|
`doctor --check` and `doctor --strict` exit nonzero when the health status is
|
|
@@ -111,7 +111,7 @@ above first. Missing, incomplete, or outdated managed skills can still be
|
|
|
111
111
|
repaired with:
|
|
112
112
|
|
|
113
113
|
```bash
|
|
114
|
-
npx -y opencode-plugin-flow@4.1.
|
|
114
|
+
npx -y opencode-plugin-flow@4.1.16 sync
|
|
115
115
|
```
|
|
116
116
|
|
|
117
117
|
Then restart OpenCode so the refreshed registry is loaded. `sync` manages all
|
|
@@ -226,7 +226,7 @@ First remove `opencode-plugin-flow` from your OpenCode plugin config so future
|
|
|
226
226
|
OpenCode startups stop loading Flow. Then remove Flow-owned synced skills:
|
|
227
227
|
|
|
228
228
|
```bash
|
|
229
|
-
npx -y opencode-plugin-flow@4.1.
|
|
229
|
+
npx -y opencode-plugin-flow@4.1.16 uninstall
|
|
230
230
|
```
|
|
231
231
|
|
|
232
232
|
Restart OpenCode after both steps. This removes Flow-owned synced skills when
|
package/dist/cli.js
CHANGED
|
@@ -1,5 +1,5 @@
|
|
|
1
1
|
#!/usr/bin/env node
|
|
2
|
-
import{createHash as
|
|
2
|
+
import{createHash as Pe}from"node:crypto";import{mkdir as je,readdir as re,readFile as Se,rm as We,writeFile as b}from"node:fs/promises";import{createRequire as Oe}from"node:module";import{dirname as Be,join as u,normalize as ze,sep as Ee}from"node:path";var S=`# Flow worker handoff contract
|
|
3
3
|
|
|
4
4
|
Flow managers merge only the worker's final response. Treat that response as the
|
|
5
5
|
worker report of record: it must include the assigned scope, what was actually
|
|
@@ -137,7 +137,74 @@ live-verified | test-verified | type-check-only | not-verified
|
|
|
137
137
|
|
|
138
138
|
The manager must inspect and validate any candidate patch before recording Flow
|
|
139
139
|
completion.
|
|
140
|
-
`;var W=`# Parallel
|
|
140
|
+
`;var W=`# Parallel full-wave example
|
|
141
|
+
|
|
142
|
+
Use this example after \`parallel-orchestration.md\` when a broad Flow task needs a
|
|
143
|
+
concrete worker wave shape.
|
|
144
|
+
|
|
145
|
+
Goal: review whether bundled Flow command guidance is self-contained and aligned
|
|
146
|
+
with hidden worker permissions.
|
|
147
|
+
|
|
148
|
+
Serial orientation: the manager reads \`src/config-shared.ts\` enough to identify
|
|
149
|
+
five public command templates and six hidden worker configs. The manager keeps
|
|
150
|
+
\`flow-status\` local because it is one line and does not need a worker.
|
|
151
|
+
|
|
152
|
+
Coverage gate: ten countable items remain after the local check.
|
|
153
|
+
|
|
154
|
+
- Slice A: \`flow-auto\`, \`flow-plan\`, and \`flow-run\` templates, expected 3/10.
|
|
155
|
+
- Slice B: \`flow-review\` template plus \`flow-reviewer\` config, expected 2/10.
|
|
156
|
+
- Slice C: remaining hidden worker permission blocks, expected 5/10 after
|
|
157
|
+
excluding the reviewer already covered by Slice B.
|
|
158
|
+
|
|
159
|
+
Worker prompts:
|
|
160
|
+
|
|
161
|
+
\`\`\`text
|
|
162
|
+
Overall goal, context only: confirm Flow public commands are self-contained.
|
|
163
|
+
Mode: evidence
|
|
164
|
+
Your exact slice: flow-auto, flow-plan, and flow-run templates in src/config-shared.ts.
|
|
165
|
+
Expected coverage: 3/3 templates.
|
|
166
|
+
Do: report bundled sections, setup preflight coverage, and any gaps with file:line evidence.
|
|
167
|
+
Do not: call state-changing Flow tools, edit .flow/**, own sibling slices, or make the final Flow verdict.
|
|
168
|
+
Return exactly the matching handoff shape from handoff-format.md.
|
|
169
|
+
\`\`\`
|
|
170
|
+
|
|
171
|
+
\`\`\`text
|
|
172
|
+
Overall goal, context only: confirm Flow review command and hidden reviewer behavior.
|
|
173
|
+
Mode: review
|
|
174
|
+
Your exact slice: flow-review command template and flow-reviewer config in src/config-shared.ts.
|
|
175
|
+
Expected coverage: 2/2 surfaces.
|
|
176
|
+
Do: separate blocking findings from advisory notes and cite file:line evidence.
|
|
177
|
+
Do not: call state-changing Flow tools, edit .flow/**, own sibling slices, or make the final Flow verdict.
|
|
178
|
+
Return exactly the matching handoff shape from handoff-format.md.
|
|
179
|
+
\`\`\`
|
|
180
|
+
|
|
181
|
+
\`\`\`text
|
|
182
|
+
Overall goal, context only: confirm hidden worker permissions match the orchestration model.
|
|
183
|
+
Mode: audit
|
|
184
|
+
Your exact slice: flow-evidence-worker, flow-validation-worker, flow-audit-worker, flow-candidate-worker, and flow-verifier-worker permissions in src/config-shared.ts.
|
|
185
|
+
Expected coverage: 5/5 worker permission blocks.
|
|
186
|
+
Do: report edit, bash, task, skill, flow_*, and flow_status permissions with evidence.
|
|
187
|
+
Do not: call state-changing Flow tools, edit .flow/**, own sibling slices, or make the final Flow verdict.
|
|
188
|
+
Return exactly the matching handoff shape from handoff-format.md.
|
|
189
|
+
\`\`\`
|
|
190
|
+
|
|
191
|
+
Handoff checks: the manager accepts only reports with terminal status, matching
|
|
192
|
+
coverage counts, concrete file:line evidence, confidence tags, and claims inside
|
|
193
|
+
the assigned slice. A claim such as \`[high] validation workers may run commands;
|
|
194
|
+
evidence: src/config-shared.ts:281-288; corroboration: single source\` is usable.
|
|
195
|
+
A claim such as \`[high] permissions look safe; evidence: config reviewed\` is
|
|
196
|
+
dropped or retasked.
|
|
197
|
+
|
|
198
|
+
Verifier pass: the manager sends any single-source claim that will enter the
|
|
199
|
+
Flow payload to \`flow-verifier-worker\`, for example: \`C1: validation, audit,
|
|
200
|
+
candidate, and verifier workers have bash ask while evidence and review workers
|
|
201
|
+
have bash deny; sources: src/config-shared.ts worker permission blocks\`.
|
|
202
|
+
|
|
203
|
+
Final synthesis: the manager re-reads the relevant config lines, keeps only
|
|
204
|
+
verified or clearly labeled claims, and records one artifact such as a plan
|
|
205
|
+
decision, review payload, or docs patch. Raw handoffs and unverified suggestions
|
|
206
|
+
do not move into the next wave or user-facing answer.
|
|
207
|
+
`;var O=`# Parallel orchestration
|
|
141
208
|
|
|
142
209
|
Use fan-out when Flow work is broad enough that independent workers can gather
|
|
143
210
|
evidence faster than one linear pass. The manager still owns the Flow session:
|
|
@@ -149,6 +216,22 @@ Read these companion references before a broad wave:
|
|
|
149
216
|
- \`handoff-format.md\` for the exact worker response shapes.
|
|
150
217
|
- \`verification-gates.md\` for coverage checks, handoff acceptance, verifier
|
|
151
218
|
triggers, and synthesis rules.
|
|
219
|
+
- \`parallel-full-wave-example.md\` for a concrete end-to-end wave after the rules
|
|
220
|
+
below are clear.
|
|
221
|
+
|
|
222
|
+
## Quick path
|
|
223
|
+
|
|
224
|
+
1. Orient serially and keep the immediate blocker local.
|
|
225
|
+
2. Fan out only when two to five non-overlapping slices reduce known
|
|
226
|
+
uncertainty.
|
|
227
|
+
3. Write a coverage gate before spawning workers: total scope, exact slices,
|
|
228
|
+
expected counts, and overlap/gap check.
|
|
229
|
+
4. Give each worker a named mode, exact slice, expected coverage, and the
|
|
230
|
+
required handoff shape.
|
|
231
|
+
5. Accept only scoped, evidenced, confidence-labeled claims; verify important
|
|
232
|
+
weak, contested, or single-source claims.
|
|
233
|
+
6. Synthesize one manager-owned artifact. Raw handoffs do not become the answer,
|
|
234
|
+
Flow payload, or patch decision.
|
|
152
235
|
|
|
153
236
|
## Operational defaults
|
|
154
237
|
|
|
@@ -287,71 +370,6 @@ For research or current-doc slices, require source checks for versioned or
|
|
|
287
370
|
time-sensitive facts. For implementation candidates, remind workers that other
|
|
288
371
|
work may be active and that they must not revert unrelated changes.
|
|
289
372
|
|
|
290
|
-
## Full-wave example
|
|
291
|
-
|
|
292
|
-
Goal: review whether bundled Flow command guidance is self-contained and aligned
|
|
293
|
-
with hidden worker permissions.
|
|
294
|
-
|
|
295
|
-
Serial orientation: the manager reads \`src/config-shared.ts\` enough to identify
|
|
296
|
-
five public command templates and six hidden worker configs. The manager keeps
|
|
297
|
-
\`flow-status\` local because it is one line and does not need a worker.
|
|
298
|
-
|
|
299
|
-
Coverage gate: ten countable items remain after the local check.
|
|
300
|
-
|
|
301
|
-
- Slice A: \`flow-auto\`, \`flow-plan\`, and \`flow-run\` templates, expected 3/10.
|
|
302
|
-
- Slice B: \`flow-review\` template plus \`flow-reviewer\` config, expected 2/10.
|
|
303
|
-
- Slice C: remaining hidden worker permission blocks, expected 5/10 after
|
|
304
|
-
excluding the reviewer already covered by Slice B.
|
|
305
|
-
|
|
306
|
-
Worker prompts:
|
|
307
|
-
|
|
308
|
-
\`\`\`text
|
|
309
|
-
Overall goal, context only: confirm Flow public commands are self-contained.
|
|
310
|
-
Mode: evidence
|
|
311
|
-
Your exact slice: flow-auto, flow-plan, and flow-run templates in src/config-shared.ts.
|
|
312
|
-
Expected coverage: 3/3 templates.
|
|
313
|
-
Do: report bundled sections, setup preflight coverage, and any gaps with file:line evidence.
|
|
314
|
-
Do not: call state-changing Flow tools, edit .flow/**, own sibling slices, or make the final Flow verdict.
|
|
315
|
-
Return exactly the matching handoff shape from handoff-format.md.
|
|
316
|
-
\`\`\`
|
|
317
|
-
|
|
318
|
-
\`\`\`text
|
|
319
|
-
Overall goal, context only: confirm Flow review command and hidden reviewer behavior.
|
|
320
|
-
Mode: review
|
|
321
|
-
Your exact slice: flow-review command template and flow-reviewer config in src/config-shared.ts.
|
|
322
|
-
Expected coverage: 2/2 surfaces.
|
|
323
|
-
Do: separate blocking findings from advisory notes and cite file:line evidence.
|
|
324
|
-
Do not: call state-changing Flow tools, edit .flow/**, own sibling slices, or make the final Flow verdict.
|
|
325
|
-
Return exactly the matching handoff shape from handoff-format.md.
|
|
326
|
-
\`\`\`
|
|
327
|
-
|
|
328
|
-
\`\`\`text
|
|
329
|
-
Overall goal, context only: confirm hidden worker permissions match the orchestration model.
|
|
330
|
-
Mode: audit
|
|
331
|
-
Your exact slice: flow-evidence-worker, flow-validation-worker, flow-audit-worker, flow-candidate-worker, and flow-verifier-worker permissions in src/config-shared.ts.
|
|
332
|
-
Expected coverage: 5/5 worker permission blocks.
|
|
333
|
-
Do: report edit, bash, task, skill, flow_*, and flow_status permissions with evidence.
|
|
334
|
-
Do not: call state-changing Flow tools, edit .flow/**, own sibling slices, or make the final Flow verdict.
|
|
335
|
-
Return exactly the matching handoff shape from handoff-format.md.
|
|
336
|
-
\`\`\`
|
|
337
|
-
|
|
338
|
-
Handoff checks: the manager accepts only reports with terminal status, matching
|
|
339
|
-
coverage counts, concrete file:line evidence, confidence tags, and claims inside
|
|
340
|
-
the assigned slice. A claim such as \`[high] validation workers may run commands;
|
|
341
|
-
evidence: src/config-shared.ts:281-288; corroboration: single source\` is usable.
|
|
342
|
-
A claim such as \`[high] permissions look safe; evidence: config reviewed\` is
|
|
343
|
-
dropped or retasked.
|
|
344
|
-
|
|
345
|
-
Verifier pass: the manager sends any single-source claim that will enter the
|
|
346
|
-
Flow payload to \`flow-verifier-worker\`, for example: \`C1: validation, audit,
|
|
347
|
-
candidate, and verifier workers have bash ask while evidence and review workers
|
|
348
|
-
have bash deny; sources: src/config-shared.ts worker permission blocks\`.
|
|
349
|
-
|
|
350
|
-
Final synthesis: the manager re-reads the relevant config lines, keeps only
|
|
351
|
-
verified or clearly labeled claims, and records one artifact such as a plan
|
|
352
|
-
decision, review payload, or docs patch. Raw handoffs and unverified suggestions
|
|
353
|
-
do not move into the next wave or user-facing answer.
|
|
354
|
-
|
|
355
373
|
## Where handoffs go
|
|
356
374
|
|
|
357
375
|
- Planning evidence becomes \`requirements\`, \`decisions\`, feature \`targets\`,
|
|
@@ -386,7 +404,7 @@ Start a follow-up wave when first-wave handoffs reveal:
|
|
|
386
404
|
|
|
387
405
|
Do not recurse by default. If a worker says it needs another worker, the manager
|
|
388
406
|
decides whether that is a second wave and writes the next bounded prompt.
|
|
389
|
-
`;var
|
|
407
|
+
`;var B='# Recovery playbook\n\nUse this when a Flow tool returns `status: "error"`, a blocker, or a `nextAction` that conflicts with memory.\n\n## First response\n\n1. Re-anchor with `flow_status`.\n2. Read the returned `summary`, `recovery`, `lastError`, and active feature.\n3. Fix the cause, then retry the smallest valid Flow action.\n\n## Common cases\n\n- `missing_session`: start with `flow_plan_save` using the user\'s goal.\n- `missing_goal`: ask for a concrete goal before planning.\n- `Approved plans cannot be changed`: use `flow_feature_reset` when only affected features need another pass; otherwise close and start a new goal.\n- `No feature is currently running`: call `flow_run_start` before completing.\n- `already in progress`: finish, reset, or block the active feature before starting another.\n- `Completion requires recorded validation evidence`: run real validation and include at least one passing `validationRun`.\n- `Completion requires all recorded validation to pass`: fix failures and rerun. Do not relabel failed checks as passed.\n- `Non-final feature completion requires targeted validation`: use `validationScope: "targeted"` for ordinary features.\n- `Final feature completion requires broad validation`: run the project-level gate and use `validationScope: "broad"`.\n- `Completion requires a passing featureReview`: run or request a real review and include a passing `featureReview` only when there are no blocking findings.\n- `Final feature completion requires a finalReview`: perform final review and include `finalReview`.\n- `Final review depth must match the plan policy`: use `reviewDepth` equal to the approved plan\'s `finalReviewPolicy`; valid final-review values are `broad` and `detailed`.\n- `Cannot close ... unfinished features`: complete, reset, defer, or abandon honestly. Do not mark completed while work remains.\n\n## Reset guidance\n\nUse `flow_feature_reset` when the active or completed work was built on the wrong assumption, validation revealed a design issue, dependencies need to be rerun, or dependent features must be invalidated. Resetting a feature also resets its dependents.\n\n## Closure guidance\n\nUse `flow_session_close`:\n\n- `completed`: only after all planned features are complete.\n- `deferred`: the user intentionally postpones unfinished work.\n- `abandoned`: the session should be archived without claiming delivery.\n\nAfter closure, the active `.flow/session.json` is removed and the archived JSON is stored under `.flow/history/`.\n';var z=`# Verification gates
|
|
390
408
|
|
|
391
409
|
Verification is how Flow keeps parallel work from turning into parallel
|
|
392
410
|
guesswork. Worker handoffs are candidate evidence; the manager decides what can
|
|
@@ -478,7 +496,7 @@ Before presenting or recording the result:
|
|
|
478
496
|
|
|
479
497
|
\`Status: success\` only says the worker believes its slice is done. The manager
|
|
480
498
|
still checks coverage and evidence before trusting the result.
|
|
481
|
-
`;var
|
|
499
|
+
`;var E=`---
|
|
482
500
|
name: flow
|
|
483
501
|
description: Run the end-to-end Flow loop for skills-first OpenCode work. Use when a user asks for Flow-guided planning through implementation, resumable autonomous delivery, session status, or completion with validation and review gates.
|
|
484
502
|
---
|
|
@@ -553,7 +571,7 @@ Planning and running require loaded Flow tools; do not simulate plan approval or
|
|
|
553
571
|
- Unknown runtime error: read \`summary\` and \`recovery\`; see \`references/recovery-playbook.md\` for common cases.
|
|
554
572
|
|
|
555
573
|
Never fabricate validation output, backfill review approval you did not perform, or close as \`deferred\`/\`abandoned\` merely to avoid an unfinished-work blocker.
|
|
556
|
-
`;var
|
|
574
|
+
`;var N=`---
|
|
557
575
|
name: flow-commit
|
|
558
576
|
description: Prepare safe Git commits and commit messages. Use only when the user asks to inspect, stage, validate, write a commit message, or create a commit; preserves unrelated work and never pushes, amends, rebases, or publishes without explicit authorization.
|
|
559
577
|
---
|
|
@@ -669,7 +687,7 @@ Before running \`git commit\`, report:
|
|
|
669
687
|
|
|
670
688
|
After a successful commit, report the commit hash and leave push or release
|
|
671
689
|
actions for a separate explicit request.
|
|
672
|
-
`;var
|
|
690
|
+
`;var G=`# Safe refactor workflow
|
|
673
691
|
|
|
674
692
|
Refactoring is a behavior-preserving sequence of small changes. This workflow keeps cleanup from becoming an unreviewable rewrite.
|
|
675
693
|
|
|
@@ -711,7 +729,7 @@ Weak evidence includes:
|
|
|
711
729
|
- Public contracts and compatibility shims remain intact or were explicitly planned.
|
|
712
730
|
- Deleted code is actually unreachable or obsolete.
|
|
713
731
|
- Validation can catch a realistic mistake in the refactor.
|
|
714
|
-
`;var
|
|
732
|
+
`;var V=`# Deslop smell rubric
|
|
715
733
|
|
|
716
734
|
Use this rubric to turn vague cleanup instincts into reviewable findings.
|
|
717
735
|
|
|
@@ -745,7 +763,7 @@ class; severity; location; evidence read; refutation checked; why it matters; sa
|
|
|
745
763
|
\`\`\`
|
|
746
764
|
|
|
747
765
|
Rate as blocking only when the smell materially raises defect risk, blocks planned work, hides behavior, or makes the success claim unverifiable. Style-only cleanup is advisory.
|
|
748
|
-
`;var
|
|
766
|
+
`;var M=`---
|
|
749
767
|
name: flow-deslop
|
|
750
768
|
description: Clean up and refactor code with evidence-backed code-smell analysis. Use for AI-slop removal, overengineering reduction, maintainability refactors, behavior-preserving cleanup, duplicated or bloated code, speculative abstractions, dead code, or broad cleanup/refactor review.
|
|
751
769
|
---
|
|
@@ -787,7 +805,7 @@ For each claimed smell removal, verify:
|
|
|
787
805
|
- **blast radius** — public contracts and downstream callers still work.
|
|
788
806
|
|
|
789
807
|
Never approve cleanup because it "looks cleaner" without evidence. Tests passing is necessary but not sufficient when the refactor changes structure across files.
|
|
790
|
-
`;var
|
|
808
|
+
`;var L=`# Parallel discovery
|
|
791
809
|
|
|
792
810
|
Use this only after a serial orientation pass has identified the repo shape and the likely slices. Workers are read-only evidence gatherers; the planner owns the plan.
|
|
793
811
|
|
|
@@ -863,7 +881,7 @@ If workers disagree, inspect the source artifact yourself. If a candidate findin
|
|
|
863
881
|
Apply the manager synthesis barrier from
|
|
864
882
|
\`../../flow/references/verification-gates.md\`: only distilled, evidence-backed
|
|
865
883
|
claims become plan fields.
|
|
866
|
-
`;var
|
|
884
|
+
`;var $=`# Planning examples
|
|
867
885
|
|
|
868
886
|
## Rate limiting feature set
|
|
869
887
|
|
|
@@ -948,9 +966,9 @@ Better plan:
|
|
|
948
966
|
- Validation that only says "manual testing".
|
|
949
967
|
- Targets that name the entire repo.
|
|
950
968
|
- Features with hidden dependencies instead of \`dependsOn\`.
|
|
951
|
-
`;var
|
|
969
|
+
`;var Q=`---
|
|
952
970
|
name: flow-plan
|
|
953
|
-
description: Plan Flow work for the v4 skills-first runtime: inspect the repo, decompose a user goal into right-sized features, save a draft with flow_plan_save, and approve it with flow_plan_approve.
|
|
971
|
+
description: "Plan Flow work for the v4 skills-first runtime: inspect the repo, decompose a user goal into right-sized features, save a draft with flow_plan_save, and approve it with flow_plan_approve."
|
|
954
972
|
---
|
|
955
973
|
|
|
956
974
|
# Flow Plan
|
|
@@ -1018,7 +1036,7 @@ Use only \`finalReviewPolicy: "broad"\` or \`"detailed"\`. These are the canonic
|
|
|
1018
1036
|
After saving, summarize the plan to the user. Call \`flow_plan_approve\` only after explicit user approval, unless the user already authorized autonomous implementation. Approved plans are immutable; changing them later requires reset/closure rather than silent edits.
|
|
1019
1037
|
|
|
1020
1038
|
See \`references/planning-examples.md\` for payload examples and decomposition anti-patterns.
|
|
1021
|
-
`;var
|
|
1039
|
+
`;var K=`# Review rubric
|
|
1022
1040
|
|
|
1023
1041
|
Use this to decide whether a \`featureReview\` or \`finalReview\` payload may pass.
|
|
1024
1042
|
|
|
@@ -1106,9 +1124,9 @@ When reviewing a findings report, verify findings adversarially:
|
|
|
1106
1124
|
- Downgrade or reject findings that do not survive refutation.
|
|
1107
1125
|
|
|
1108
1126
|
Approve only on evidence actually inspected. A review is a claim of coverage, not a courtesy stamp.
|
|
1109
|
-
`;var
|
|
1127
|
+
`;var Y=`---
|
|
1110
1128
|
name: flow-review
|
|
1111
|
-
description: Review Flow work in the v4 runtime: inspect feature or final-session changes, classify findings, and return featureReview or finalReview payloads for flow_feature_complete.
|
|
1129
|
+
description: "Review Flow work in the v4 runtime: inspect feature or final-session changes, classify findings, and return featureReview or finalReview payloads for flow_feature_complete."
|
|
1112
1130
|
---
|
|
1113
1131
|
|
|
1114
1132
|
# Flow Review
|
|
@@ -1176,7 +1194,7 @@ Use \`status: "failed"\` when any blocking finding remains. Advisory findings ma
|
|
|
1176
1194
|
\`finalReview\` payload.
|
|
1177
1195
|
|
|
1178
1196
|
Never approve to unblock completion, fix findings in the review pass, or vouch for validation you did not inspect.
|
|
1179
|
-
`;var
|
|
1197
|
+
`;var X=`# Audit findings rubric
|
|
1180
1198
|
|
|
1181
1199
|
What counts as a valid finding when the feature's deliverable is a findings report: a codebase audit, a review-first feature, or any report whose findings a later feature will fix. The commands you run are still governed by \`validation-rubric.md\`; this rubric governs the findings themselves.
|
|
1182
1200
|
|
|
@@ -1229,7 +1247,7 @@ follow-up order — correctness and persisted/user-input surfaces first
|
|
|
1229
1247
|
\`\`\`
|
|
1230
1248
|
|
|
1231
1249
|
Never: promote a hypothesis to blocking severity; cite a line you did not read in context; rate severity against a deployment model the product does not have; pad the report to look thorough — six verified findings outrank nine where three die on first contact.
|
|
1232
|
-
`;var
|
|
1250
|
+
`;var J=`# Validation evidence rubric
|
|
1233
1251
|
|
|
1234
1252
|
Use this before recording \`flow_feature_complete\`.
|
|
1235
1253
|
|
|
@@ -1286,9 +1304,9 @@ Broad validation usually means the repo's full check command, full relevant test
|
|
|
1286
1304
|
- If validation needs external access, missing credentials, or ambiguous user input, record \`status: "needs_input"\` with an honest \`outcome\`.
|
|
1287
1305
|
|
|
1288
1306
|
Never trim failing output, relabel a failed command as passed, or use "not run" as completion evidence.
|
|
1289
|
-
`;var
|
|
1307
|
+
`;var Z=`---
|
|
1290
1308
|
name: flow-run
|
|
1291
|
-
description: Execute one approved Flow feature in the v4 runtime: start a feature with flow_run_start, make scoped changes, gather real validation evidence, obtain review payloads, and complete with flow_feature_complete.
|
|
1309
|
+
description: "Execute one approved Flow feature in the v4 runtime: start a feature with flow_run_start, make scoped changes, gather real validation evidence, obtain review payloads, and complete with flow_feature_complete."
|
|
1292
1310
|
---
|
|
1293
1311
|
|
|
1294
1312
|
# Flow Run
|
|
@@ -1373,7 +1391,7 @@ Complete with:
|
|
|
1373
1391
|
\`\`\`
|
|
1374
1392
|
|
|
1375
1393
|
If genuinely blocked, call \`flow_feature_complete\` with \`status: "needs_input"\` and an \`outcome\` that explains the blocker and next step. Never fabricate validation or review evidence to force progress.
|
|
1376
|
-
`;var
|
|
1394
|
+
`;var H=`---
|
|
1377
1395
|
name: flow-test
|
|
1378
1396
|
description: Test, validate, make test plans, triage failures, and gather Flow validation evidence. Use when selecting checks, running tests, running browser QA for UI changes, classifying failures, or preparing validationRun evidence for flow_feature_complete.
|
|
1379
1397
|
---
|
|
@@ -1497,7 +1515,7 @@ covered. Static inspection alone is a gap for behavioral changes.
|
|
|
1497
1515
|
|
|
1498
1516
|
Never relabel a failed command as passed, invent output, or use "not run" as
|
|
1499
1517
|
completion evidence.
|
|
1500
|
-
`;var
|
|
1518
|
+
`;var ee=`# UI quality rubric
|
|
1501
1519
|
|
|
1502
1520
|
Use this rubric for frontend planning, implementation, and review.
|
|
1503
1521
|
|
|
@@ -1541,7 +1559,7 @@ class; severity; location or screenshot area; evidence inspected; user impact; f
|
|
|
1541
1559
|
\`\`\`
|
|
1542
1560
|
|
|
1543
1561
|
Blocking UI findings are issues that prevent task completion, hide required information, break accessibility basics, create incoherent layout at supported sizes, or make the visual success claim unverifiable.
|
|
1544
|
-
`;var
|
|
1562
|
+
`;var ae=`# Visual verification workflow
|
|
1545
1563
|
|
|
1546
1564
|
Use this workflow when UI changes can be run locally. Flow execution may create visual evidence; Flow review usually assesses recorded evidence because the reviewer is read-only.
|
|
1547
1565
|
|
|
@@ -1581,7 +1599,7 @@ Record the reason and use the strongest available substitute:
|
|
|
1581
1599
|
- code inspection against existing component patterns.
|
|
1582
1600
|
|
|
1583
1601
|
Do not claim visual polish was verified if no visual artifact was inspected.
|
|
1584
|
-
`;var
|
|
1602
|
+
`;var te=`---
|
|
1585
1603
|
name: flow-ui-quality
|
|
1586
1604
|
description: Review and improve frontend UI quality for Flow work. Use for UX/UI design, frontend polish, visual quality review, responsive and accessible interfaces, interaction states, screenshots, browser-verified UI work, and avoiding generic AI-generated UI.
|
|
1587
1605
|
---
|
|
@@ -1629,23 +1647,23 @@ Approve only when the interface is both useful and inspectable:
|
|
|
1629
1647
|
- Screenshot/browser evidence supports the claim whenever feasible.
|
|
1630
1648
|
|
|
1631
1649
|
Never approve a UI change based only on code shape. If users will judge it visually, Flow evidence should include visual inspection.
|
|
1632
|
-
`;var y=[{name:"flow",files:[{relativePath:"SKILL.md",content:
|
|
1633
|
-
`)}async function m(e){try{return await
|
|
1650
|
+
`;var y=[{name:"flow",files:[{relativePath:"SKILL.md",content:E},{relativePath:"references/recovery-playbook.md",content:B},{relativePath:"references/parallel-orchestration.md",content:O},{relativePath:"references/parallel-full-wave-example.md",content:W},{relativePath:"references/handoff-format.md",content:S},{relativePath:"references/verification-gates.md",content:z}]},{name:"flow-plan",files:[{relativePath:"SKILL.md",content:Q},{relativePath:"references/planning-examples.md",content:$},{relativePath:"references/parallel-discovery.md",content:L}]},{name:"flow-run",files:[{relativePath:"SKILL.md",content:Z},{relativePath:"references/validation-rubric.md",content:J},{relativePath:"references/audit-rubric.md",content:X}]},{name:"flow-test",files:[{relativePath:"SKILL.md",content:H}]},{name:"flow-review",files:[{relativePath:"SKILL.md",content:Y},{relativePath:"references/review-rubric.md",content:K}]},{name:"flow-deslop",files:[{relativePath:"SKILL.md",content:M},{relativePath:"references/smell-rubric.md",content:V},{relativePath:"references/refactor-workflow.md",content:G}]},{name:"flow-ui-quality",files:[{relativePath:"SKILL.md",content:te},{relativePath:"references/ui-rubric.md",content:ee},{relativePath:"references/visual-verification.md",content:ae}]},{name:"flow-commit",files:[{relativePath:"SKILL.md",content:N}]}];var q=".flow-skill-version";function _(){return process.env.HOME??process.env.USERPROFILE??""}function D(e=_()){return u(e,".config","opencode","skills")}function g(e){return Pe("sha256").update(e).digest("hex")}function k(e,a){return[`version=${a}`,...e.files.map((t)=>`file=${t.relativePath} sha256=${g(t.content)}`),""].join(`
|
|
1651
|
+
`)}async function m(e){try{return await Se(e,"utf8")}catch(a){if(a.code==="ENOENT")return null;throw a}}function T(e){let a=new Map;if(!e)return a;for(let t of e.split(/\r?\n/)){let r=/^file=(.+) sha256=([a-f0-9]{64})$/.exec(t)??/^file=(.+)=sha256:([a-f0-9]{64})$/.exec(t);if(r?.[1]&&r[2])a.set(r[1],r[2]);let s=/^hash=sha256:([a-f0-9]{64})$/.exec(t);if(s?.[1]&&!a.has("SKILL.md"))a.set("SKILL.md",s[1])}return a}function Ne(e){if(!e)return null;for(let a of e.split(/\r?\n/)){let t=/^version=(.+)$/.exec(a);if(t?.[1])return t[1]}return null}function x(e,a){let t=ze(u(e,...a.split("/")));if(t!==e&&t.startsWith(`${e}${Ee}`))return t;throw Error(`Unsafe skill file path '${a}'.`)}async function Ge(e,a){let t=`${e}.backup.${g(a).slice(0,12)}`;for(let r=0;;r+=1){let s=r===0?t:`${t}.${r}`;try{return await b(s,a,{encoding:"utf8",flag:"wx"}),s}catch(n){if(n.code==="EEXIST")continue;throw n}}}async function Ve(e,a,t){let r=u(t,e.name),s=u(r,q),n=await m(s),d=T(n);if(await m(u(r,"SKILL.md"))!==null&&n===null)return{name:e.name,action:"skipped_foreign"};let i=!1,l=[];for(let o of e.files){let c=x(r,o.relativePath),h=await m(c);if(h===o.content)continue;i=!0;let w=d.get(o.relativePath);if(h!==null&&(w?g(h)!==w:n!==null))l.push(await Ge(c,h))}if(!i&&n===k(e,a))return{name:e.name,action:"unchanged"};if(!i)return await b(s,k(e,a),"utf8"),{name:e.name,action:"marker_updated"};let v=n!==null;for(let o of e.files){let c=x(r,o.relativePath);await je(Be(c),{recursive:!0}),await b(c,o.content,"utf8")}return await b(s,k(e,a),"utf8"),{name:e.name,action:l.length>0?"updated_with_backup":v?"updated":"installed",...l.length>0?{backupPaths:l}:{}}}function Me(){return y.map((e)=>e.name)}function Le(e){return`npx -y opencode-plugin-flow@${e} doctor`}function F(){if(process.env.npm_package_version)return process.env.npm_package_version;try{let e=Oe(import.meta.url);for(let a of["../package.json","../../package.json"])try{let t=e(a);if(t.version)return t.version}catch{}}catch{}return"0.0.0"}async function ne(e,a=_()){let t=D(a);return Promise.all(y.map((r)=>Ve(r,e,t)))}async function se(e=F(),a=_()){let t=D(a),r=new Set(Me()),s=await Promise.all(y.map(async(o)=>{let c=u(t,o.name),h=await m(u(c,q)),w=Ne(h),P=T(h);if(await m(u(c,"SKILL.md"))===null)return{name:o.name,path:c,status:"missing",markerVersion:w,missingFiles:o.files.map((f)=>f.relativePath),editedFiles:[],outdatedFiles:[]};if(h===null)return{name:o.name,path:c,status:"foreign",markerVersion:w,missingFiles:[],editedFiles:[],outdatedFiles:[]};let R=[],U=[],C=[];for(let f of o.files){let A=await m(x(c,f.relativePath));if(A===null){R.push(f.relativePath);continue}if(A===f.content)continue;let j=P.get(f.relativePath);if(j&&g(A)!==j){U.push(f.relativePath);continue}C.push(f.relativePath)}let de=h!==k(o,e),le=R.length>0?"incomplete":U.length>0?"edited":de||C.length>0?"outdated":"ok";return{name:o.name,path:c,status:le,markerVersion:w,missingFiles:R,editedFiles:U,outdatedFiles:C}})),n=[];try{n=await re(t)}catch(o){if(o.code!=="ENOENT")throw o}let d=n.filter((o)=>(o==="flow"||o.startsWith("flow-"))&&!r.has(o)).map((o)=>u(t,o)),p=s.filter((o)=>["missing","incomplete","outdated"].includes(o.status)).map((o)=>o.name),i=s.filter((o)=>["foreign","edited"].includes(o.status)).map((o)=>o.name),l=i.length>0,v=p.length>0;return{status:l?"action_required":v?"sync_required":"ok",version:e,root:t,expectedSkills:[...r],skills:s,syncRequiredSkills:p,actionRequiredSkills:i,unmanagedFlowSkills:d}}function oe(e,a,t){if(t.length===0)return;e.push(`- ${a}: ${t.join(", ")}`)}function ie(e){let a=["Flow doctor",`- status: ${e.status}`,`- plugin version: ${e.version}`,`- skills root: ${e.root}`,`- expected skills: ${e.expectedSkills.join(", ")}`];oe(a,"startup sync can install/update",e.syncRequiredSkills),oe(a,"needs user decision",e.actionRequiredSkills),a.push("","Skills:");for(let t of e.skills){if(a.push(`- ${t.name}: ${t.status} (${t.path})${t.markerVersion?` marker=${t.markerVersion}`:""}`),t.missingFiles.length>0)a.push(` missing: ${t.missingFiles.join(", ")}`);if(t.editedFiles.length>0)a.push(` edited: ${t.editedFiles.join(", ")}`);if(t.outdatedFiles.length>0)a.push(` outdated: ${t.outdatedFiles.join(", ")}`)}if(e.unmanagedFlowSkills.length>0){a.push("","Unmanaged Flow-like skill folders:");for(let t of e.unmanagedFlowSkills)a.push(`- ${t}`)}if(a.push("","Recommendation:"),e.status==="ok")a.push("- Flow skills are present and current.");else if(e.status==="sync_required")a.push("- Start or restart OpenCode with opencode-plugin-flow enabled so startup sync can install or update the listed skills. If Flow then reports restart_required, restart OpenCode once more so the refreshed skill registry is used.");else a.push("- Resolve user-owned or edited managed skill folders, then restart OpenCode. Move a folder aside to let Flow recreate it, or keep it intentionally as a local override.");return a.push(`- Details command: ${Le(e.version)}`),`${a.join(`
|
|
1634
1652
|
`)}
|
|
1635
|
-
`}async function
|
|
1636
|
-
`)}function
|
|
1637
|
-
`);return}process.stdout.write(
|
|
1638
|
-
`);return}if(a==="--version"||a==="-v"){process.stdout.write(`${
|
|
1639
|
-
`);return}if(a!=="uninstall"&&a!=="doctor"&&a!=="sync"){process.stderr.write(`${
|
|
1640
|
-
`),process.exitCode=2;return}if(a==="doctor"){if(
|
|
1641
|
-
`),process.exitCode=2;return}let
|
|
1642
|
-
`),process.exitCode=2;return}if(a==="sync"){let
|
|
1643
|
-
`);for(let i of
|
|
1653
|
+
`}async function ce(e=_()){let a=D(e),t=[],r=[],s;try{s=await re(a)}catch(n){if(n.code==="ENOENT")return{removed:t,kept:r};throw n}for(let n of s){if(n!=="flow"&&!n.startsWith("flow-"))continue;let d=u(a,n),p=await m(u(d,q));if(p===null){r.push(d);continue}let i=T(p),l=!1;for(let[v,o]of i){let c=await m(x(d,v));if(c!==null&&g(c)!==o){l=!0;break}}if(l){r.push(d);continue}await We(d,{recursive:!0,force:!0}),t.push(d)}return{removed:t,kept:r}}function I(){return["usage: opencode-plugin-flow <doctor|sync|uninstall> [options]","","commands:"," doctor Inspect managed Flow skills"," sync Install or refresh managed Flow skills"," uninstall Remove pristine Flow-owned managed skills","","doctor options:"," --json Write the doctor report as JSON"," --check, --strict Exit nonzero when doctor status is not ok","","global options:"," --help Show this help"," --version Print the plugin version"].join(`
|
|
1654
|
+
`)}function $e(e,a){return e.every((t)=>a.has(t))}function Qe(e,a){if(a.json){process.stdout.write(`${JSON.stringify(e,null,2)}
|
|
1655
|
+
`);return}process.stdout.write(ie(e))}async function Ke(e){let a=e[2],t=e.slice(3);if(a==="--help"||a==="-h"){process.stdout.write(`${I()}
|
|
1656
|
+
`);return}if(a==="--version"||a==="-v"){process.stdout.write(`${F()}
|
|
1657
|
+
`);return}if(a!=="uninstall"&&a!=="doctor"&&a!=="sync"){process.stderr.write(`${I()}
|
|
1658
|
+
`),process.exitCode=2;return}if(a==="doctor"){if(!$e(t,new Set(["--json","--check","--strict"]))){process.stderr.write(`${I()}
|
|
1659
|
+
`),process.exitCode=2;return}let n=await se();if(Qe(n,{json:t.includes("--json")}),(n.status==="sync_required"||n.status==="action_required")&&(t.includes("--check")||t.includes("--strict")))process.exitCode=1;return}if(t.length>0){process.stderr.write(`${I()}
|
|
1660
|
+
`),process.exitCode=2;return}if(a==="sync"){let s=F(),n=await ne(s),d=n.filter((i)=>["installed","updated","updated_with_backup"].includes(i.action)),p=n.filter((i)=>i.action==="skipped_foreign");process.stdout.write(`Flow skill sync (${s})
|
|
1661
|
+
`);for(let i of n){process.stdout.write(`- ${i.name}: ${i.action}
|
|
1644
1662
|
`);for(let l of i.backupPaths??[])process.stdout.write(` backup: ${l}
|
|
1645
1663
|
`)}if(d.length>0)process.stdout.write(`Restart OpenCode so the refreshed skill registry is used.
|
|
1646
1664
|
`);if(p.length>0)process.stdout.write(`Some managed skill folders are user-owned or edited; run doctor for repair guidance.
|
|
1647
|
-
`);return}let r=await
|
|
1648
|
-
`);for(let
|
|
1665
|
+
`);return}let r=await ce();for(let s of r.removed)process.stdout.write(`Removed Flow skill: ${s}
|
|
1666
|
+
`);for(let s of r.kept)process.stdout.write(`Kept non-Flow or user-edited skill: ${s}
|
|
1649
1667
|
`);process.stdout.write(`Remove opencode-plugin-flow from your OpenCode plugin config and restart OpenCode.
|
|
1650
|
-
`)}
|
|
1668
|
+
`)}Ke(process.argv).catch((e)=>{process.stderr.write(`${e instanceof Error?e.message:String(e)}
|
|
1651
1669
|
`),process.exitCode=1});
|