@jabworks/condux 0.25.1 → 0.25.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 +1 -1
- package/skills/workflow/SKILL.md +12 -2
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@jabworks/condux",
|
|
3
|
-
"version": "0.25.
|
|
3
|
+
"version": "0.25.2",
|
|
4
4
|
"description": "OpenCode plugin for the condux workflow toolkit — bundles the condux skills and injects the specialist agents (coder, explorer, planner, researcher) plus an opt-in plan-review listener.",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"publishConfig": {
|
package/skills/workflow/SKILL.md
CHANGED
|
@@ -18,8 +18,8 @@ No under-planning for a cross-cutting feature.
|
|
|
18
18
|
## Live Context
|
|
19
19
|
|
|
20
20
|
```!
|
|
21
|
-
git status --short
|
|
22
|
-
git log --oneline -5
|
|
21
|
+
git status --short 2>/dev/null || echo "(not a git repository yet)"
|
|
22
|
+
git log --oneline -5 2>/dev/null || echo "(no commits yet)"
|
|
23
23
|
```
|
|
24
24
|
|
|
25
25
|
## Operating Rules
|
|
@@ -106,6 +106,15 @@ Every tier ends with `preflight` then `finalize` — no exceptions.
|
|
|
106
106
|
After the user picks, load **only** that skill, run it, then return to the nearest
|
|
107
107
|
checkpoint and re-present the menu until the user chooses Done.
|
|
108
108
|
|
|
109
|
+
**When the question tool caps the options.** CP-1 and CP-3 have five rows, and
|
|
110
|
+
some hosts' question tools take four (Claude Code's AskUserQuestion does). The
|
|
111
|
+
first four rows go on buttons, recommended first. The fifth row rides in the
|
|
112
|
+
free-text slot the tool adds ("Other"), and the question text names it:
|
|
113
|
+
"Plan ready — how do we proceed? (or type 'revise' to rework the plan)" for
|
|
114
|
+
CP-1, "(or say done)" for CP-3. Never merge two rows into one button to make
|
|
115
|
+
room — "Use agents" for the two agent rows is exactly the erosion this rule
|
|
116
|
+
prevents. A host with no cap, or a plain-text menu, shows every row.
|
|
117
|
+
|
|
109
118
|
### CP-1 — Plan ready
|
|
110
119
|
|
|
111
120
|
*After draft-plan sign-off (LARGE) or the inline plan (MEDIUM). Plan review already
|
|
@@ -248,6 +257,7 @@ Stop if you catch yourself doing any of these:
|
|
|
248
257
|
| Tests / lint / typecheck mid-implementation | Save it all for `finalize` |
|
|
249
258
|
| Spawning agents for a task you can just do | Default is to implement yourself |
|
|
250
259
|
| Omitting the subagent options from a checkpoint menu | The default shapes the recommendation, never the menu — present every CP-1 row |
|
|
260
|
+
| Merging or dropping rows to fit a four-option question tool | Four rows on buttons, the fifth named in the question text and taken through "Other" |
|
|
251
261
|
| Silently skipping discovery on a LARGE task | Ask — it's a soft gate, not a free pass |
|
|
252
262
|
| Rewriting a test spec to make it pass | Stop and ask — never silently edit specs |
|
|
253
263
|
| Auto-running code-review, commits, or agents | They're checkpoint choices; run only when picked |
|