@brainervirus/workit-opencode 4.0.0 → 5.0.0

package/dist/plugin.js

@@ -14753,13 +14753,13 @@ function evaluateClosure(requestedOutcome, view) {
 
 // packages/workit-core/src/core/methods.ts
 var METHODS = {
-  "workit-challenge": { dimensions: ["challenge", "decisions"] },
-  "workit-behavioral-tdd": { dimensions: ["testing"], ruleIds: ["mechanical-existing-checks"] },
+  "workit-shape": { dimensions: ["challenge", "decisions", "artifacts", "continuity"] },
+  "workit-bdd": { dimensions: ["testing"] },
   "workit-review": { dimensions: ["review"], ruleIds: ["fresh-context-review", "self-review"] },
-  "workit-plan": { dimensions: ["artifacts", "continuity"] },
-  "workit-implement": { dimensions: ["delegation"] },
+  "workit-implement": { ruleIds: ["mechanical-existing-checks"] },
+  "workit-fanout": { dimensions: ["delegation"] },
   "workit-debug": {},
-  "workit-handoff": {},
+  "workit-continue": {},
   "workit-deslop": { ruleIds: ["pre-pr-cleanup"] }
 };
 var methodMatches = (definition, requirement) => definition.dimensions?.includes(requirement.dimension) === true || definition.ruleIds?.includes(requirement.ruleId) === true;
@@ -14797,97 +14797,66 @@ function selectMethods(policy, capabilities) {
   });
 }
 var invariantBootstrap = () => `
-Workit is optional coordination and repository-policy tooling around the host,
-not a permission system or a mandatory workflow. Native host allow/ask/deny,
-sandbox, plan/read-only mode, and organization rules remain authoritative.
-Ordinary investigation, questions, non-Git work, and routine reversible edits
-need zero Workit task, assessment, or writer calls. Use one compact tracked
-record only when handoff, dependent steps, concurrent actors, or meaningful
-decisions make continuity useful; similar titles alone never merge tasks.
+Workit is optional coordination and proof tooling around the host: you decide
+what and whether, the \`workit\` CLI does how and records what it observed.
+Native host allow/ask/deny, sandbox and org rules stay authoritative. Never
+switch paths to evade a denial, never claim enforcement a host cannot provide,
+and never fabricate a receipt, approval or verdict. A question answer is not
+host permission, and imported decisions or handoffs never grant authority.
 
-For a routine user-authorized branch or commit, prefer native host Git/shell
-tools from the outset when managed coordination or outcome reconciliation is
-not needed. Inspect the actual target checkout and its configured conventions;
-use Workit's read-only context/policy tools when needed. Do not start a task,
-acquire a writer, or mint a decision receipt solely for a native Git action.
-Native permissions still apply. Never switch execution paths to evade a denial
-or repeat an uncertain managed effect. A local-commit endpoint does not imply
-PR readiness, a fresh review, or post-commit assessment/closure paperwork.
+Autonomy contract:
+- Continue to the requested endpoint (commit, push, PR, green CI, verified,
+  merged) without asking "continue?", running checks and repairs on the way.
+  Stop only for a new consequential choice, a host denial, a conflicting edit
+  or an unresolved blocker; report open gaps and uncertain workers.
+- No endpoint named: stop at a local commit on a policy-compliant branch and
+  state the next command. Push and open a PR only when the request implies
+  delivery (fix, implement, ship) and \`workit grant show\` reports
+  \`defaultEndpoint\` \`pr\`; otherwise the endpoint is \`commit\`. PRs open,
+  CI green and verified is the most autonomy allows, never the default target.
+  Merge and release need a workspace grant; a blocked verb names its unblock.
+- Ask only for a product or preference choice, or for authority you lack, with
+  your recommended answer. Facts are yours: read, run or prototype.
+- Label claims measured (you ran it this session and saw the result),
+  inferred, or guess. Prose is a note: only a configured check the CLI ran
+  (\`workit check <name>\`) satisfies a gate; an ad-hoc
+  \`workit check -- <cmd>\` never does.
+- Author is not verifier: never record a passing verdict on work your session
+  wrote. The lead starts each verifier with its own session
+  (\`WORKIT_SESSION_ID=<lead>-v<n>\`; Claude Code subagents get one from the
+  hook), and the verifier records \`workit ledger verdict\`.
+- A local-commit endpoint does not imply PR readiness, and a local commit alone
+  is not evidence of a requested remote push. Before reporting delivery,
+  reconcile every requested item and observe it (\`workit verify-delivery\`).
 
-For tracked work, inspect its current state and use the shared operations for
-task, policy, evidence, finding, decision, worker, writer, and state changes.
-Each branch has one implicit task: an operation without taskId applies to it,
-and the first recording (a note, check, finding or evidence) creates it, so you
-never manage task ids. Start a record only for an explicit tracked objective;
-assess or reassess only
-when policy selection or changed evidence/constraints requires it. Omitted
-expectedRevision and expectedWorkspaceRevision use current values; explicit
-values are still concurrency-checked, so never copy revisions between calls.
-A busy result means another live Workit call holds the checkout lock: retry the
-same call; it is not a recovery condition. A lock left by a dead process is
-reclaimed on the next write, and \`workit doctor --fix-lock\` clears it on demand.
-An omitted revision absorbs a concurrent write: Workit re-reads, re-checks
-policy, and reapplies the call, returning busy under persistent contention. A
-revision_conflict means a revision you passed is stale: re-read the record
-before deciding whether to retry.
-A solo edit does not need writer acquisition; use it when concurrent checkout
-writers need coordination. Record only observed facts and checks. Close-time
-testing and verification gates accept only a configured check the CLI ran:
-\`workit check <name>\` (\`npx -y @brainervirus/workit-cli check <name>\` when
-\`workit\` is not on PATH); a recorded check result is a note and an ad-hoc
-\`workit check -- <cmd>\` never satisfies a gate. Evidence can become stale when its bound candidate or tree changes; reconcile findings against the
-current candidate before recording completion.
+CLI first: if a step has one right answer, use the \`workit\` verb instead of
+hand-running git, gh or glab: check, git, pr, ci, stack, verify-delivery,
+ledger, handoff, test-audit (\`workit help <verb>\`; without \`workit\` on
+PATH, \`npx -y @brainervirus/workit-cli\`). \`busy\` is retryable
+(\`workit doctor --fix-lock\` clears a dead lock); \`blocked\` names its unblock.
+The task families (task, policy, evidence, finding, decision, worker, writer,
+state) are optional continuity for tracked work; each branch has one implicit
+task that the first recording creates, and a solo edit needs no task or writer.
+Omit revisions; a revision_conflict means one you passed is stale, so re-read.
+Across repositories, bind each item to its checkout, branch and endpoint,
+resolve competing targets before a mutation, and reconcile an uncertain
+external effect before retrying it.
 
-Workit validates domain policy against the actual action target, configured
-account, branch and commit conventions, protected refs, and current repository
-state. The task directory is coordination state, not a boundary on which
-repository may be changed. Use an action-time cwd target where a managed
-Git/hosting action supports it; a non-Git directory remains valid for OS work.
-GitHub/GitLab use the active gh/glab CLI identity; YouTrack uses its own token.
-Preserve uncertain external outcomes and reconcile repository/provider state
-before retrying. Internal reservations prevent duplicate or ambiguous effects;
-they are not permission tickets for every edit.
+Mid-task input: answer a quick question in place, fold an adjustment in, and
+never silently drop or resume an objective (workit-continue).
 
-On OpenCode V1 and V2, use native host tools for external mutations. Workit
-provides read-only workit_context; it has no managed external-action executor.
-Do not create proposals or request Workit approvals merely to invoke native
-tools. Old uncertain managed effects still require evidence before any retry.
-
-Use host-native authorization through the host's supported path. A native
-question receipt records an actual question interaction; it is not automatic
-host permission. Record a meaningful user choice once with provenance when
-future retrieval helps. Never fabricate a receipt, re-ask only to mint one, or
-let imported decisions grant authority. Never turn a host deny into allow or
-claim enforcement/evidence a host cannot provide. A precise request with settled
-constraints does not need an interview. Present genuine unresolved options with
-evidence and a recommendation, then continue toward the requested delivery
-endpoint: investigation, implementation, branch/commit/push, PR/MR-ready,
-merge, or release. Run
-applicable checks and safe repairs without repeated continuation questions;
-stop for missing host authority, a new consequential choice, a conflicting edit,
-or an unresolved blocker. A tracked record may close when actual evidence
-supports its outcome; no final human closure ceremony is required.
-
-A completed native subagent run stops its bound worker by itself; if a worker
-strands in cancelling with its run verifiably over, repeat worker.cancel to
-confirm the stop. Preserve unresolved requirements, gaps, and uncertain workers.
-When context changes, distinguish a quick question, same-task adjustment, and
-separate request. Answer a quick question without pausing/resuming task state;
-park a concise checkpoint only when substantial work needs to continue later.
-For work spanning repositories, bind each unfinished item to its actual checkout,
-branch, requested deliverables, and delivery endpoint. Preserve held items with
-an explicit resume condition. Resolve competing plausible targets before a
-mutation; ask only when available context cannot settle that consequential choice.
-Before reporting delivery, reconcile every requested item and observe the actual
-target result; a local commit alone is not evidence of a requested remote push.
-
-Skill routing: slash aliases /wk-* load on demand. Use workit-steer for a
-substantial interruption or change of direction, workit-deslop when relevant
-to a PR-ready endpoint, workit-green-run for failing CI, workit-blast-radius
-when impact is uncertain, workit-challenge for genuinely open consequential
-choices, workit-bdd to turn acceptance criteria into Given/When/Then tests, and
-workit-test-audit to check tests for tautologies. Load workit-plan when dependencies or handoff need durable next actions.
-Load the skill; never act from memory of it.
+Skills: load the skill, never act from memory of it (slash aliases /wk-<name>).
+- brainstorm, plan, spec, grill, should we: workit-shape
+- implement, build, add a feature: workit-implement
+- review, blast radius: workit-review
+- bug, broken, flaky, regression: workit-debug
+- ship, babysit, CI, merge: workit-ship
+- resume, pick up, handoff, interruption: workit-continue
+- BDD, TDD, acceptance criteria, Given/When/Then: workit-bdd
+- test audit, tautology, weak tests: workit-test-audit
+- deslop, slop, dead code: workit-deslop
+- fan out, parallelize, parallel agents, swarm: workit-fanout
+- verify the app, smoke test, prove it works: workit-verify-app
 `.trim();
 
 // packages/workit-core/src/core/task-context.ts
@@ -17843,6 +17812,7 @@ var shellPolicy = (cwd, command) => {
 };
 // packages/workit-core/src/hooks/handle.ts
 var offered = new Set;
+var CLAUDE_JUDGES = new Set(["workit:verifier", "workit:reviewer"]);
 // packages/workit-core/src/hooks/hosts/fields.ts
 var SHELLS = new Set(["sh", "bash", "zsh", "dash", "pwsh", "powershell", "cmd"]);
 
@@ -20471,6 +20441,7 @@ var getWorkitBootstrap = () => {
     return cached2;
   cached2 = `${marker}
 ${invariantBootstrap()}
+On OpenCode, run external mutations with native host tools or the workit CLI; workit_context is read-only and there is no managed external-action executor, so do not create proposals or request Workit approvals merely to invoke native tools.
 OpenCode Workit decisions use the native question header "Workit decision: <purpose>", the exact presented question, and exactly two options: approved (description = approved content) and rejected (description = Reject this decision).`;
   return cached2;
 };
@@ -20615,40 +20586,30 @@ import path28 from "node:path";
 
 // packages/workit-core/src/core/skill-manifests.ts
 var WORKIT_METHOD_SKILLS = [
-  "workit-challenge",
-  "workit-behavioral-tdd",
-  "workit-review",
-  "workit-plan",
+  "workit-shape",
   "workit-implement",
+  "workit-review",
   "workit-debug",
-  "workit-handoff",
-  "workit-babysit",
-  "workit-blast-radius",
-  "workit-deslop",
-  "workit-diagram",
-  "workit-mockup",
-  "workit-green-run",
-  "workit-steer",
+  "workit-ship",
+  "workit-continue",
   "workit-bdd",
-  "workit-test-audit"
+  "workit-test-audit",
+  "workit-deslop",
+  "workit-fanout",
+  "workit-verify-app"
 ];
 var WORKIT_SKILL_ALIASES = {
-  "wk-challenge": "workit-challenge",
-  "wk-babysit": "workit-babysit",
+  "wk-shape": "workit-shape",
   "wk-implement": "workit-implement",
-  "wk-plan": "workit-plan",
-  "wk-debug": "workit-debug",
   "wk-review": "workit-review",
-  "wk-handoff": "workit-handoff",
-  "wk-tdd": "workit-behavioral-tdd",
-  "wk-blast-radius": "workit-blast-radius",
-  "wk-deslop": "workit-deslop",
-  "wk-diagram": "workit-diagram",
-  "wk-mockup": "workit-mockup",
-  "wk-green-run": "workit-green-run",
-  "wk-steer": "workit-steer",
+  "wk-debug": "workit-debug",
+  "wk-ship": "workit-ship",
+  "wk-continue": "workit-continue",
   "wk-bdd": "workit-bdd",
-  "wk-test-audit": "workit-test-audit"
+  "wk-test-audit": "workit-test-audit",
+  "wk-deslop": "workit-deslop",
+  "wk-fanout": "workit-fanout",
+  "wk-verify-app": "workit-verify-app"
 };
 if (false) {}
 
@@ -20675,7 +20636,13 @@ var packageRoot2 = () => {
   }
   return path27.resolve(dir, "..");
 };
-var assetsRoot = () => path27.join(packageRoot2(), "assets");
+var skillsRoot = () => {
+  const root = packageRoot2();
+  const canonical = path27.resolve(root, "..", "workit-core", "skills");
+  if (existsSync9(path27.join(root, "src")) && existsSync9(canonical))
+    return canonical;
+  return path27.join(root, "assets", "skills");
+};
 
 // packages/workit-opencode/src/v2/registry.ts
 var parseFrontmatter = (markdown) => {
@@ -20697,7 +20664,7 @@ var parseFrontmatter = (markdown) => {
   };
 };
 var registerSkills = async (ctx) => {
-  const skillsDir = path28.join(assetsRoot(), "skills");
+  const skillsDir = skillsRoot();
   if (!existsSync10(skillsDir))
     return new Set;
   const listed = await ctx.skill.list().catch(() => ({ data: [] }));

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@brainervirus/workit-opencode",
-  "version": "4.0.0",
+  "version": "5.0.0",
   "private": false,
   "description": "Workit OpenCode plugin — native tools, adaptive policy, and sixteen method skills",
   "keywords": [
@@ -39,7 +39,7 @@
     "typecheck": "tsc --noEmit"
   },
   "dependencies": {
-    "@brainervirus/workit-core": "^4.0.0"
+    "@brainervirus/workit-core": "^5.0.0"
   },
   "devDependencies": {
     "@opencode/plugin": "2.0.18"

package/assets/skills/workit-babysit/SKILL.md

@@ -1,37 +0,0 @@
----
-name: workit-babysit
-description: Use when the user asks to babysit a PR or explicitly opts in to PR follow-up
----
-
-# Babysit a PR to PR-ready
-
-PR creation does not start babysitting. `babysit:true` opts into this skill;
-omission means no follow-up. A PR URL by itself is not an instruction to drive
-it. When the user asks to babysit a URL from a route Workit did not enforce,
-help without claiming the Workit route was enforced. Never mutate PR topology
-(no rebase strategy changes, no force-push).
-
-
-## Method
-
-1. Default to drive mode for an explicit babysit request: resolve conflicts,
-   address review threads, and get checks green. Watch reports status only;
-   threads-only addresses review threads. Ask about mode only when the choice
-   materially changes the work.
-2. Work toward PR-ready in order: conflicts → review threads → CI. Keep a brief
-   checkpoint when continuity needs it; task progress is optional.
-3. Classify CI before retry: flake (rerun once) vs stale base (verify with
-   `git merge-base --is-ancestor` before updating) vs real failure (fix).
-4. Triage bot findings skeptically: reproduce or quote code before acting;
-   invalid bots get a reasoned dismissal, never silent ignore.
-5. Batch fixes into one push wave; re-verify green after every push.
-6. Stop at PR-ready. A PR creation or babysit request does not authorize merge
-   or release. Continue to merge or release only when the user explicitly sets
-   that delivery endpoint and host authority allows the action.
-
-## Completion
-
-Report PR-ready status with evidence for fixes, or a brief blocker report. If
-the user explicitly authorized merge, honor the configured strategy only after
-checks and required approval. After a squash merge, re-record evidence against
-the new base commit before closing tracked work.

package/assets/skills/workit-behavioral-tdd/SKILL.md

@@ -1,56 +0,0 @@
----
-name: workit-behavioral-tdd
-description: Use when policy identifies behavior, side effects, permissions, or data handling that may change and a regression boundary is needed
----
-
-# Behavioral TDD
-
-Test the observable behavior at a stable boundary, not the implementation shape.
-Use this method when assessment selects the `testing` dimension.
-
-
-## Method
-
-1. Inspect the task requirement, current candidate, intended behavior, and real
-   verification entry point with shared `task`, `policy`, and `evidence` operations.
-2. State one behavior and its observable result. Choose the narrowest stable
-   boundary a caller or user depends on; avoid private helpers and incidental
-   representations.
-3. Write one vertical RED slice that fails for the missing behavior and run it
-   through the CLI so the failure is observed: `workit check test` (the repo's
-   configured `test` check; `npx -y @brainervirus/workit-cli check test` when
-   `workit` is not on PATH). Implement the smallest change, then run the same
-   check GREEN. Close accepts only a fresh passing run of the configured check
-   that `workit check` observed; a recorded "tests pass" is a note, and an
-   ad-hoc `workit check -- <cmd>` never satisfies the gate. If no `test` check
-   is configured or detected, add `workit.checks.json` (committed) with it.
-4. Add only another slice for a distinct behavior or risk. Any edit makes the
-   observed check stale: re-run `workit check test` before closing.
-
-## Reject noisy tests
-
-- A dependency/version-pin assertion is not behavioral evidence.
-- A test that mirrors branches, private calls, or exact implementation structure
-  is coupled to internals; replace it with the public effect.
-- Duplicate assertions and tests that add no distinct failure signal are noise;
-  delete them.
-- Do not claim a passing test satisfies a different requirement.
-- Banned: tautologies (asserts what the code says, not what it must do),
-  ghost loops (assert inside a possibly-empty loop), smoke-only renders,
-  type-only or CSS-class coupling. If the test still passes when every
-  imported function returns undefined, rewrite the assertion or delete it.
-  `workit test-audit --diff` flags these; triage them with workit-test-audit.
-  Turning acceptance criteria into scenarios and seams is workit-bdd.
-
-Run RED/GREEN through `workit check`, which records the observed result on the
-current task; shared `evidence` operations are for notes and non-test evidence.
-Do not add a second lifecycle, approval chain, or test workflow outside the
-current task state.
-
-## Common mistakes
-
-| Mistake | Correction |
-| --- | --- |
-| "The pin changed, so assert the new string" | Exercise the affected consumer behavior. |
-| "The code is obvious" | A small vertical slice still proves the contract. |
-| Keeping a passing test after the boundary moved | Re-run `workit check test` on the current tree. |

package/assets/skills/workit-blast-radius/SKILL.md

@@ -1,26 +0,0 @@
----
-name: workit-blast-radius
-description: Use when a small-looking change could break something else, before close or merge
----
-
-# Blast radius beyond the diff
-
-A small diff is not a small risk. Prove the one fact it is safe because of,
-with runnable proof — not assertion.
-
-
-## Method
-
-1. List what the change touches: callers, shared state, contracts, config,
-   migrations. Grep every caller of each touched function.
-2. For each: state the one fact it is safe because of (type boundary,
-   existing test, unreachable path) plus how to run the proof.
-3. Run the proofs. Unproven claims stay labeled UNPROVEN in findings —
-   never silently treated as safe.
-4. Fix at the shared root (one guard where all callers route through),
-   not per caller.
-
-## Completion
-
-Blast-radius note in evidence or review: each risk with fact + proof
-command, or an UNPROVEN finding for what could not be proven.

package/assets/skills/workit-challenge/SKILL.md

@@ -1,47 +0,0 @@
----
-name: workit-challenge
-description: Use when requirements or consequences leave a real decision open
----
-
-# Challenge open choices with evidence
-
-Skip this method for a precise, settled request.
-
-## Method
-
-1. Ground the outcome, constraints, evidence, and important unknowns. Inspect
-   code and project docs before asking about facts they can answer.
-2. Separate observations, inferences, and proposals. Test assumptions that
-   could change the recommendation.
-3. When viable alternatives exist, present two or three genuinely different
-   approaches. Recommend one; for each, give its benefit, cost or risk, when it
-   fits, and the smallest useful validation. Do not invent a weak alternative.
-4. Ask only consequential questions, in dependency order. Group independent
-   choices into one small round. If an authorized reversible default works,
-   state it and proceed.
-5. Record a settled choice once in the existing conversation or task context.
-   A discussion decision is knowledge; never fabricate a native permission
-   receipt or reopen it without new evidence.
-6. Create durable documentation only when requested or when the decision needs
-   a future reader. Brainstorming alone does not require a spec.
-
-Say directly when evidence shows a proposal is weak, overcomplicated, or solves
-the wrong problem. Raise a counter-case only when it adds a real constraint.
-
-## Guardrails
-
-- Do not create a universal spec, plan, approval chain, or second lifecycle.
-- Unknowns that affect an action remain unresolved until evidence or a user
-  decision closes them.
-- Use shared operations for tracked state and provenance; never write task
-  metadata directly.
-- An in-session counter-case is not fresh-context review.
-
-## Common mistakes
-
-| Mistake | Correction |
-| --- | --- |
-| Asking what code or docs already answer | Ground first; the user owns choices, not lookups. |
-| Listing every hypothetical objection | Raise only objections that can change the decision. |
-| Asking for agreement without a recommendation | Recommend an option and explain the tradeoff. |
-| Treating a discussion decision as permission | Record it as knowledge; preserve native host authority. |

package/assets/skills/workit-diagram/SKILL.md

@@ -1,27 +0,0 @@
----
-name: workit-diagram
-description: Use when a spec or plan needs a flow or architecture diagram
----
-
-# Mermaid when needed, never by default
-
-Tables first, ASCII trees second, mermaid only when a flow or architecture
-needs it. Flowchart, sequence, state, or ER only. No renderer, no network.
-
-
-## Syntax rules (mermaid v11)
-
-- Fence as ` ```mermaid `, no surrounding prose inside the fence.
-- Quote node labels containing punctuation: `A["input (x, y)"]`.
-- One direction per diagram (`TD` or `LR`); keep nodes under twelve.
-- Name actors exactly as the codebase names them (real symbols only).
-
-## Verify
-
-Re-read the fence before commit: balanced quotes/brackets, every node
-reachable, labels match spec terms. If it cannot be verified by reading,
-delete it.
-
-## Completion
-
-One diagram that argues a decision, or nothing. Never a diagram suite.

package/assets/skills/workit-green-run/SKILL.md

@@ -1,24 +0,0 @@
----
-name: workit-green-run
-description: Use to drive a red CI pipeline back to green, usually inside babysit
----
-
-# The CI loop
-
-Watch, classify, fix, push once, re-verify. Host-native (`gh` / GitLab);
-never invent CI APIs.
-
-
-## Method
-
-1. Read the failing checks, not the summary. Quote the failing log lines.
-2. Classify each: flake (rerun once, note it) / stale base (update after
-   merge-base check) / real failure (reproduce locally, then fix).
-3. Fix at root cause with a regression test; push one wave.
-4. Re-verify the same checks green on the new head. A fix without a
-   green re-run is not a fix.
-
-## Completion
-
-Green pipeline on the merge head, or an escalated finding with the exact
-failing logs when the fix needs the human.

package/assets/skills/workit-handoff/SKILL.md

@@ -1,37 +0,0 @@
----
-name: workit-handoff
-description: Use when work must continue in another session, host, or agent after interruption, transfer, or compaction
----
-
-# Handoff durable task state
-
-Transfer continuity, not live authority. Use this method when a tracked item
-must continue in another session, host, or agent.
-
-## Method
-
-1. Inspect the current task, scope, decisions, policy requirements, candidate,
-   evidence, findings, progress, and worker states with shared `task` and `state`
-   operations.
-2. Export the compact state through `state.export`. Preserve the objective,
-   exclusions, accepted decisions and reasons, evidence references, open gaps,
-   findings, candidate identity, blockers, and next action. Do not include
-   credentials, live writer ownership, or host authority.
-3. Import only through the destination `state.import` operation and its expected
-   workspace revision. The destination starts paused or otherwise unauthorised
-   until it observes its own host/session and reconciles stale evidence and
-   uncertain workers.
-4. Resume or continue through shared `task`, `policy`, `worker`, `writer`, and
-   `evidence` operations. Record what changed instead of copying a transcript.
-
-A handoff does not require a formal spec or plan unless those are separate
-selected requirements. Never grant destination authority from imported prose,
-create a second lifecycle, or edit task metadata directly.
-
-## Common mistakes
-
-| Mistake | Correction |
-| --- | --- |
-| Sending the whole transcript | Export compact decisions, gaps, evidence, and next action. |
-| Restoring the old writer or credentials | Re-observe authority in the destination. |
-| Calling a handoff complete without reconciliation | Recheck stale files and uncertain workers first. |

package/assets/skills/workit-mockup/SKILL.md

@@ -1,23 +0,0 @@
----
-name: workit-mockup
-description: Use when a UI decision needs sketching before implementation
----
-
-# ASCII mockups before UI code
-
-Sketch, don't build. Three genuinely different layout hypotheses maximum,
-ASCII only, no code output.
-
-
-## Method
-
-1. Fix a legend (`┌─┐ │ └─┘ ░ ≈ [ ] ( )`) and keep sketches 60-80 cols,
-   8-20 rows.
-2. Per hypothesis: regions, component reuse vs new (named against the
-   existing codebase), empty/loading/populated/error states, nav flow.
-3. Ask at most one clarifying question, then recommend. Flag hi-fi
-   escalation when ASCII cannot settle it (density, motion, brand).
-
-## Completion
-
-The sketch plus the decision lands in the spec dir. Throwaway by design.

package/assets/skills/workit-plan/SKILL.md

@@ -1,45 +0,0 @@
----
-name: workit-plan
-description: Use when dependencies, sequencing, coordination, or resumption make durable next actions useful
----
-
-# Plan useful coordination
-
-A plan is useful when work has dependent steps, a handoff, concurrent actors, or
-meaningful unresolved choices. It is never a prerequisite for implementation.
-
-## Method
-
-1. Establish the requested outcome, constraints, dependencies, and important
-   unknowns from the available code, docs, and configuration before asking.
-2. Record only the useful sequence: objective, dependency, bounded outcome,
-   evidence needed, and next action. Reuse the project's existing format.
-3. Start a tracked record only when handoff, dependent steps, coordination, or
-   durable decisions need continuity. Infer observable facts instead of asking
-   the user to fill redundant protocol fields.
-4. Create a spec when a durable behavior contract or interface is requested or
-   will help a future reader. Use an ADR for a consequential trade-off and a
-   glossary for stable terms. A small fix needs no document.
-5. If the user authorized implementation, proceed through the agreed endpoint
-   and applicable checks. Do not ask for a separate plan approval or repeat
-   "continue?". Stop for a new consequential choice, host denial, conflict, or
-   blocker that cannot be resolved safely.
-6. Update a checkpoint at meaningful boundaries when another session may need
-   to resume. Keep settled decisions, changed files, actual checks, blockers,
-   and the next action; omit transcript and process trivia.
-
-## Shape
-
-Plan slices as small end-to-end outcomes with explicit dependencies and checks.
-Keep repo policy and native host authority separate. Preserve the user's branch
-and commit conventions. Do not prescribe one commit per step or create a second
-approval chain unless the user asked for that delivery format.
-
-## Common mistakes
-
-| Mistake | Correction |
-| --- | --- |
-| Writing a packet for a bounded reversible change | Leave the change undocumented. |
-| Asking what repository state or code can answer | Inspect it first. |
-| Treating the plan as authority | Follow the user's scope and native host permissions. |
-| Copying a transcript into the plan | Keep decisions, evidence, gaps, and next action only. |