@jabworks/condux 0.17.0 → 0.17.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jabworks/condux",
-  "version": "0.17.0",
+  "version": "0.17.2",
   "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.",
   "type": "module",
   "publishConfig": {

package/skills/discovery/SKILL.md

@@ -239,10 +239,13 @@ open. It still accepts a submitted decision, which means **one server covers
 the whole of discovery** — launched at §1, still serving at sign-off. Never
 start a second one.
 
-Announce it and move on — do not ask first:
+Manual mode binds a **free port** — there is no fixed number to assume. The
+server prints the URL on startup (`Plan review → http://127.0.0.1:<port>`, on
+stderr); read it from that output and announce exactly that URL — do not ask
+first:
 
-> "Design preview running at http://127.0.0.1:7777 — it updates as we go. Say
-> the word if you'd rather I close it."
+> "Design preview running at http://127.0.0.1:<port> — it updates as we go.
+> Say the word if you'd rather I close it."
 
 The preview's purpose is to help make the *next* decision, so gating it behind
 an opt-in defeats what it is for; and discovery only runs on the LARGE tier, so

package/skills/draft-plan/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: draft-plan
-description: "Turns a signed-off design into an executable plan of lean task cards (what, why, gotchas, dependencies). Writes Markdown; review in the browser via plan-review. Run for LARGE tasks after /discovery sign-off. Never writes a plan without a signed-off design — if discovery hasn't run, apply the soft gate first."
+description: "Turns a signed-off design into an executable plan of lean task cards (what, why, gotchas, dependencies). Writes Markdown; review in the browser via plan-review. Run for LARGE tasks after /discovery sign-off, and for any request to write, create, or revise a task plan — including creating or updating the .condux/plans file, the artifact this skill owns. A plan request with no signed-off design still routes here; the skill applies the soft gate itself rather than writing a plan without one."
 argument-hint: "<feature name or design summary>"
 effort: high
 ---

package/skills/technical-spec/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: technical-spec
-description: "Persists feature decisions, API contracts, implementation details, and quirks into a structured, queryable spec tree — one folder per feature, one file per concern. Invoke-only — discovery runs it at design sign-off and preflight's drift check reads its output; the user runs it via /technical-spec when they say \"save spec\", \"document this\", \"write up what we decided\", or \"spec this out\". Not for turning a rough idea into a design first — that's discovery."
+description: "Persists feature decisions, API contracts, implementation details, and quirks into a structured, queryable spec tree — one folder per feature, one file per concern. Invoke-only — discovery runs it at design sign-off and preflight's drift check reads its output; the user runs it via /technical-spec when they say \"save spec\", \"document this\", \"write up what we decided\", \"record the decision rationale\", or \"spec this out\" — recording decisions for the future is spec work even when phrased as remembering. Not for turning a rough idea into a design first — that's discovery."
 disable-model-invocation: true
 ---
 

package/skills/technical-spec/evals/trigger_eval.json

@@ -1,13 +1,13 @@
 [
   { "query": "save spec", "should_trigger": true, "expected_skill": "technical-spec" },
-  { "query": "document what we decided", "should_trigger": true, "expected_skill": "technical-spec", "disallowed": ["draft-plan"] },
+  { "query": "document what we decided", "should_trigger": true, "expected_skill": "technical-spec", "disallowed": ["draft-plan", "remember"] },
   { "query": "spec this out", "should_trigger": true, "expected_skill": "technical-spec" },
   { "query": "persist the api contract and the quirks we found", "should_trigger": true, "expected_skill": "technical-spec" },
   { "query": "write up the field mappings from backend to UI", "should_trigger": true, "expected_skill": "technical-spec" },
   { "query": "update the spec for wan-config", "should_trigger": true, "expected_skill": "technical-spec" },
   { "query": "scaffold a spec folder for this feature", "should_trigger": true, "expected_skill": "technical-spec" },
   { "query": "whats the format for quirks.md", "should_trigger": true, "expected_skill": "technical-spec", "kind": "in-context" },
-  { "query": "record the decision rationale for future sessions", "should_trigger": true, "expected_skill": "technical-spec", "disallowed": ["draft-plan"] },
+  { "query": "record the decision rationale for future sessions", "should_trigger": true, "expected_skill": "technical-spec", "disallowed": ["draft-plan", "remember"] },
   { "query": "bump the index.md changelog for the spec", "should_trigger": true, "expected_skill": "technical-spec" },
   { "query": "save the design as a tech spec with live preview", "should_trigger": true, "expected_skill": "technical-spec", "disallowed": ["draft-plan"] },
   { "query": "sepc this out pls", "should_trigger": true, "expected_skill": "technical-spec" },

package/skills/workflow/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: workflow
-description: "Routes any dev task into the right execution tier (Small/Medium/Large) and carries condux's operating rules — proportional effort, lazy skill loading, soft gates, implement-yourself-by-default. Trigger with any implementation request — feature, bug fix, refactor, new endpoint, UI change. Every dev task starts here; other skills execute within /workflow, not instead of it. Also the operating manual — questions about how condux works, its tiers, soft gates, checkpoints, and named agents."
+description: "Routes any dev task into the right execution tier (Small/Medium/Large) and carries condux's operating rules — proportional effort, lazy skill loading, soft gates, implement-yourself-by-default. Trigger with any dev task, however small or mundane — feature, bug fix, refactor, new endpoint, UI change, adding tests, CI and tooling config, docs and README edits, a one-line tweak. Every task starts here regardless of size (the tier decides the ceremony), including requests to start or prep a task, like loading its spec before beginning. Other skills execute within /workflow, not instead of it. Also the operating manual — how condux works: tiers, soft gates, checkpoints, named agents."
 argument-hint: "<task description>"
 ---