@jabworks/condux 0.14.1 → 0.14.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.
Files changed (5) hide show
  1. package/package.json +1 -1
  2. package/skills/discovery/evals/trigger_eval.json +4 -4
  3. package/skills/draft-plan/evals/trigger_eval.json +3 -3
  4. package/skills/subagent-execution/evals/trigger_eval.json +2 -2
  5. package/skills/technical-spec/evals/trigger_eval.json +4 -4
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@jabworks/condux",
3
- "version": "0.14.1",
3
+ "version": "0.14.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/discovery/evals/trigger_eval.json CHANGED
@@ -7,12 +7,12 @@
7
7
  { "query": "design session for the new onboarding", "should_trigger": true, "expected_skill": "discovery" },
8
8
  { "query": "brainstorm ideas for the notifications feature", "should_trigger": true, "expected_skill": "discovery" },
9
9
  { "query": "whats done look like for this feature? lets align first", "should_trigger": true, "expected_skill": "discovery" },
10
- { "query": "resume the design we started yesterday", "should_trigger": true, "expected_skill": "discovery" },
11
- { "query": "found an existing design doc for this, continue from it", "should_trigger": true, "expected_skill": "discovery" },
10
+ { "query": "resume the design we started yesterday", "should_trigger": true, "expected_skill": "discovery", "disallowed": ["session-handoff"] },
11
+ { "query": "found an existing design doc for this, continue from it", "should_trigger": true, "expected_skill": "discovery", "disallowed": ["session-handoff"] },
12
12
  { "query": "design a database schema for multi-tenancy", "should_trigger": true, "expected_skill": "discovery" },
13
13
  { "query": "big refactor, unclear boundaries — where do we even start", "should_trigger": true, "expected_skill": "discovery" },
14
- { "query": "resume where we left off last session", "should_trigger": true, "expected_skill": "session-handoff" },
15
- { "query": "pick up from the handoff doc", "should_trigger": true, "expected_skill": "session-handoff" },
14
+ { "query": "resume where we left off last session", "should_trigger": true, "expected_skill": "session-handoff", "disallowed": ["discovery"] },
15
+ { "query": "pick up from the handoff doc", "should_trigger": true, "expected_skill": "session-handoff", "disallowed": ["discovery"] },
16
16
  { "query": "we already have a signed off design, write the plan", "should_trigger": true, "expected_skill": "draft-plan" },
17
17
  { "query": "skip discovery, just plan it", "should_trigger": true, "expected_skill": "draft-plan" },
18
18
  { "query": "small tweak to the button color", "should_trigger": true, "expected_skill": "workflow" },
package/skills/draft-plan/evals/trigger_eval.json CHANGED
@@ -1,8 +1,8 @@
1
1
  [
2
- { "query": "write the implementation plan", "should_trigger": true, "expected_skill": "draft-plan", "accept": ["workflow"] },
3
- { "query": "turn the design into task cards", "should_trigger": true, "expected_skill": "draft-plan" },
2
+ { "query": "write the implementation plan", "should_trigger": true, "expected_skill": "draft-plan", "accept": ["workflow"], "disallowed": ["technical-spec"] },
3
+ { "query": "turn the design into task cards", "should_trigger": true, "expected_skill": "draft-plan", "disallowed": ["technical-spec"] },
4
4
  { "query": "plan out the epic we signed off yesterday", "should_trigger": true, "expected_skill": "draft-plan" },
5
- { "query": "create the .condux/plans file for this feature", "should_trigger": true, "expected_skill": "draft-plan" },
5
+ { "query": "create the .condux/plans file for this feature", "should_trigger": true, "expected_skill": "draft-plan", "disallowed": ["technical-spec"] },
6
6
  { "query": "break this down into tasks with dependencies", "should_trigger": true, "expected_skill": "draft-plan" },
7
7
  { "query": "write-plan for checkout v2", "should_trigger": true, "expected_skill": "draft-plan" },
8
8
  { "query": "we havent designed this yet but write a plan anyway", "should_trigger": true, "expected_skill": "draft-plan", "accept": ["discovery"] },
package/skills/subagent-execution/evals/trigger_eval.json CHANGED
@@ -2,14 +2,14 @@
2
2
  { "query": "execute the plan with specialist agents", "should_trigger": true, "expected_skill": "subagent-execution" },
3
3
  { "query": "run the plan task by task with subagents", "should_trigger": true, "expected_skill": "subagent-execution" },
4
4
  { "query": "use the coder agent to implement the plan", "should_trigger": true, "expected_skill": "subagent-execution" },
5
- { "query": "resume plan execution from the ledger", "should_trigger": true, "expected_skill": "subagent-execution" },
5
+ { "query": "resume plan execution from the ledger", "should_trigger": true, "expected_skill": "subagent-execution", "disallowed": ["session-handoff"] },
6
6
  { "query": "spawn agents for the LARGE plan", "should_trigger": true, "expected_skill": "subagent-execution" },
7
7
  { "query": "whats in spawn-rules for picking an agent", "should_trigger": true, "expected_skill": "subagent-execution" },
8
8
  { "query": "prepare a task brief for task 4", "should_trigger": true, "expected_skill": "subagent-execution" },
9
9
  { "query": "build the review package for the implementer's commits", "should_trigger": true, "expected_skill": "subagent-execution" },
10
10
  { "query": "which model should the coder agent get for this task", "should_trigger": true, "expected_skill": "subagent-execution" },
11
11
  { "query": "continue the wave, tasks 5 and 6 are unblocked", "should_trigger": true, "expected_skill": "subagent-execution" },
12
- { "query": "we compacted mid-plan, where were we with the agents", "should_trigger": true, "expected_skill": "subagent-execution" },
12
+ { "query": "we compacted mid-plan, where were we with the agents", "should_trigger": true, "expected_skill": "subagent-execution", "disallowed": ["session-handoff"] },
13
13
  { "query": "dont re-dispatch tasks that are already done", "should_trigger": true, "expected_skill": "subagent-execution" },
14
14
  { "query": "spawn the agents for this plan", "should_trigger": true, "expected_skill": "subagent-execution" },
15
15
  { "query": "dispatch these three unrelated fixes in parallel", "should_trigger": true, "expected_skill": "subagent-deployment" },
package/skills/technical-spec/evals/trigger_eval.json CHANGED
@@ -1,17 +1,17 @@
1
1
  [
2
2
  { "query": "save spec", "should_trigger": true, "expected_skill": "technical-spec" },
3
- { "query": "document what we decided", "should_trigger": true, "expected_skill": "technical-spec" },
3
+ { "query": "document what we decided", "should_trigger": true, "expected_skill": "technical-spec", "disallowed": ["draft-plan"] },
4
4
  { "query": "spec this out", "should_trigger": true, "expected_skill": "technical-spec" },
5
5
  { "query": "persist the api contract and the quirks we found", "should_trigger": true, "expected_skill": "technical-spec" },
6
6
  { "query": "write up the field mappings from backend to UI", "should_trigger": true, "expected_skill": "technical-spec" },
7
7
  { "query": "update the spec for wan-config", "should_trigger": true, "expected_skill": "technical-spec" },
8
8
  { "query": "scaffold a spec folder for this feature", "should_trigger": true, "expected_skill": "technical-spec" },
9
9
  { "query": "whats the format for quirks.md", "should_trigger": true, "expected_skill": "technical-spec", "kind": "in-context" },
10
- { "query": "record the decision rationale for future sessions", "should_trigger": true, "expected_skill": "technical-spec" },
10
+ { "query": "record the decision rationale for future sessions", "should_trigger": true, "expected_skill": "technical-spec", "disallowed": ["draft-plan"] },
11
11
  { "query": "bump the index.md changelog for the spec", "should_trigger": true, "expected_skill": "technical-spec" },
12
- { "query": "save the design as a tech spec with live preview", "should_trigger": true, "expected_skill": "technical-spec" },
12
+ { "query": "save the design as a tech spec with live preview", "should_trigger": true, "expected_skill": "technical-spec", "disallowed": ["draft-plan"] },
13
13
  { "query": "sepc this out pls", "should_trigger": true, "expected_skill": "technical-spec" },
14
- { "query": "write up what we decided about the milestone", "should_trigger": true, "expected_skill": "technical-spec" },
14
+ { "query": "write up what we decided about the milestone", "should_trigger": true, "expected_skill": "technical-spec", "disallowed": ["draft-plan"] },
15
15
  { "query": "update the spec with what we built", "should_trigger": true, "expected_skill": "technical-spec" },
16
16
  { "query": "load the spec for checkout before we start the task", "should_trigger": true, "expected_skill": "workflow", "accept": ["spec-browser"], "note": "spec-browser owns \"where is the spec for X\" navigation; loading a spec before a task is servable by either the router's step-2 lookup or the spec site." },
17
17
  { "query": "browse the specs tree", "should_trigger": true, "expected_skill": "spec-browser" },