@iowarp/clio-coder 0.5.0 → 0.5.2

package/library/registry.yaml

@@ -148,53 +148,50 @@ entries:
           worktree-create. Not for integrating branches; use worktre
   - kind: skill
     name: clio-coder-dev
-    description: "Governs changes to Clio Coder's own source and harness (TUI,
-      skills, agents, tools, prompts, domains): what may change freely, what
-      needs explicit user intent, and how to change it without breaking the
-      architecture. Not for verifying a change against the harness; use
-      clio-coder-test."
+    description: "Develop Clio Coder inside its own repository: trace source
+      contracts, implement bounded changes, coordinate sprint work, and preserve
+      running-agent and session correctness. Use before changing Clio source,
+      prompts, tools, or library; pair with clio-coder-test for validation."
     category: meta
     audit: pass
     triggers:
-      - modify Clio Coder
-      - change the Clio harness
-      - edit Clio skills or agents
-      - evolve Clio tools or prompts
-      - Clio contribution boundary
-    version: 0.4.0
+      - develop Clio in its own repository
+      - implement a Clio sprint packet
+      - change Clio context or session lifecycle
+      - edit Clio skills tools or prompts
+    version: 0.5.0
     sourceUrl: skills/meta/clio-coder-dev
-    sha256: d72e2dcd441600f927738d352766a7472e2340bb60b1a23b6894f921079e4243
+    sha256: a2a9558348234ef5fb5fe821651ef57b8f6430473bd48818a1d468b405c1f61a
     provides:
       - kind: skill
         name: clio-coder-dev
-        description: "Governs changes to Clio Coder's own source and harness (TUI,
-          skills, agents, tools, prompts, domains): what may change freely, what
-          needs explicit user intent, and how to change it without breaking the
-          architecture. Not for verifying a change against the h"
+        description: "Develop Clio Coder inside its own repository: trace source
+          contracts, implement bounded changes, coordinate sprint work, and
+          preserve running-agent and session correctness. Use before changing
+          Clio source, prompts, tools, or library; pair with clio-coder-t"
   - kind: skill
     name: clio-coder-test
-    description: Verifies a Clio Coder source change against the current contract,
-      smoke, boundary, and application test lanes, including temporary-state and
-      local-provider harnesses. Not for deciding what may change; use
-      clio-coder-dev.
+    description: Validate Clio Coder changes using focused source regressions, built
+      CLI and ACP fixtures, skill/library checks, and isolated package or GUI
+      gates. Use when developing or diagnosing Clio itself; select checks from
+      the changed behavior and report evidence without claiming unrun coverage.
     category: meta
     audit: pass
     triggers:
-      - test Clio Coder
-      - verify a Clio source change
-      - run Clio contract tests
-      - test ACP over stdio
-      - Clio mock provider harness
-    version: 0.3.1
+      - validate a Clio change
+      - test Clio context compaction or memory
+      - verify Clio skill activation
+      - choose Clio test gates
+    version: 0.4.0
     sourceUrl: skills/meta/clio-coder-test
-    sha256: c5a1fa81a19d671560d98a5f4e78f56a0515294611bc9ae796aac37165719a92
+    sha256: 6a4748d77d27be81da75ae8359cde2c44f76db83f025920b102a8aa309e17208
     provides:
       - kind: skill
         name: clio-coder-test
-        description: Verifies a Clio Coder source change against the current contract,
-          smoke, boundary, and application test lanes, including temporary-state
-          and local-provider harnesses. Not for deciding what may change; use
-          clio-coder-dev.
+        description: Validate Clio Coder changes using focused source regressions, built
+          CLI and ACP fixtures, skill/library checks, and isolated package or
+          GUI gates. Use when developing or diagnosing Clio itself; select
+          checks from the changed behavior and report evidence wi
   - kind: skill
     name: coding-standards
     description: Correct-by-construction TypeScript rules (errors as values, parse
@@ -235,7 +232,7 @@ entries:
       - write a continuation brief
     version: 0.5.1
     sourceUrl: skills/context/context-handoff
-    sha256: f5d32418c95dcc9766b5564b00e9d27de6c86662b742666792f1ef984921ad24
+    sha256: 64fc4593679735a9e827d8753183595c48fc38ce031902af2d17da7f747a68b1
     provides:
       - kind: skill
         name: context-handoff
@@ -944,3 +941,266 @@ entries:
           integration branch, testing after each merge and running the full
           suite before the main line moves, with exact rollback on failure. Not
           for creating worktrees; use worktree-create. Not for closeou
+  - kind: plugin
+    name: wtfp
+    description: Portable, evidence-grounded academic research and writing workflows.
+    version: 0.7.3
+    sourceUrl: https://github.com/akougkas/wtf-p/tree/v0.7.3/vendors/plugin
+    sha256: 5a4209bed7c4926dc884c5b04bb66ce5ed61083e1b718045cf720f295cc2f3b5
+    provides:
+      - kind: agent
+        name: wtfp-argument-verifier
+        description: Verify that completed section text actually delivers the claims,
+          evidence, constraints, and connections promised by its plan. Execution
+          summaries are navigation aids, not proof; verdicts must be grounded in
+          the manuscript itself.
+      - kind: agent
+        name: wtfp-citation-expert
+        description: "Find a precise, defensible set of sources for explicit manuscript
+          claims and analyze whether the existing bibliography covers the
+          approved argument. Every recommendation must be grounded in resolvable
+          scholarly metadata and its relevance must be explained "
+      - kind: agent
+        name: wtfp-citation-formatter
+        description: Audit bibliography integrity and produce deterministic corrections
+          without touching the primary bibliography. The role cross-references
+          manuscript citation keys, detects missing and unused entries,
+          identifies likely duplicates, and normalizes records while
+      - kind: agent
+        name: wtfp-coherence-checker
+        description: Evaluate the manuscript as a connected argument rather than a set
+          of individually acceptable sections. Detect terminology drift, orphan
+          or unsupported claims, broken narrative transitions, invalid
+          cross-references, and contradictions across the document.
+      - kind: agent
+        name: wtfp-outliner
+        description: Turn the approved project brief into the structural foundation for
+          an academic document. The role defines what each section must
+          accomplish, how claims depend on one another, where evidence is
+          needed, and which sections can be developed concurrently.
+      - kind: agent
+        name: wtfp-plan-checker
+        description: "Determine whether proposed section plans are likely to produce the
+          intended academic outcome. Verification is goal-backward: a
+          syntactically complete plan still fails if it omits a claim, lacks
+          usable evidence, contradicts an author decision, or cannot fit"
+      - kind: agent
+        name: wtfp-prose-polisher
+        description: Improve clarity, rhythm, concision, and authorial voice without
+          changing technical meaning, evidence, citation placement, or
+          argumentative direction. Polishing is a constrained transformation,
+          not a substantive rewrite.
+      - kind: agent
+        name: wtfp-research-synthesizer
+        description: Investigate the literature needed to plan and write a specific
+          section well. The output is an evidence-traceable synthesis of
+          foundational and recent work, standard approaches, genuine gaps,
+          positioning options, and concrete writing guidance—not a search-r
+      - kind: agent
+        name: wtfp-section-planner
+        description: "Convert one approved section goal into small, executable writing
+          plans. A plan is a precise writing contract: it connects claims,
+          evidence, word budgets, sequencing, author decisions, and measurable
+          completion criteria without pre-writing the section."
+      - kind: agent
+        name: wtfp-section-reviewer
+        description: Review a section as an academic evaluator and produce prioritized,
+          actionable feedback. The invocation may select a review
+          lens—adversarial peer, significance-focused chair, production editor,
+          or constructive mentor—without changing the underlying evidence
+      - kind: agent
+        name: wtfp-section-writer
+        description: Execute an approved section plan into evidence-grounded academic
+          prose or the explicitly requested scaffold. Preserve the author’s
+          epistemic authority, make only supported claims, and leave an
+          auditable account of what was produced and what remains unresol
+      - kind: fleet
+        name: wtfp-draft-review
+        description: Draft one approved section and independently review its argument
+          and evidence.
+      - kind: fleet
+        name: wtfp-plan-section
+        description: Create and independently check one evidence-grounded section plan.
+      - kind: prompt
+        name: wtfp:add-todo
+        description: Capture a bounded note or task without disrupting the active
+          research flow.
+      - kind: prompt
+        name: wtfp:analyze-bib
+        description: Analyze a bibliography and map its evidence to the paper's sections
+          and claims.
+      - kind: prompt
+        name: wtfp:audit-milestone
+        description: Run readiness checks across section completion, arguments, length,
+          citations, and reviews.
+      - kind: prompt
+        name: wtfp:check-refs
+        description: Audit citation integrity and emit a validated
+          corrected-bibliography candidate without mutating source records or
+          manuscript inputs.
+      - kind: prompt
+        name: wtfp:check-todos
+        description: Review pending tasks and explicitly act on, defer, complete, or
+          dismiss each one.
+      - kind: prompt
+        name: wtfp:checkpoint
+        description: Save, list, or restore an exact portable paper-state checkpoint.
+      - kind: prompt
+        name: wtfp:contribute
+        description: Guide a bounded WTF-P contribution from branch creation through a
+          reviewable change request.
+      - kind: prompt
+        name: wtfp:create-outline
+        description: Build the section structure, argument map, dependencies, and word
+          budgets.
+      - kind: prompt
+        name: wtfp:create-poster
+        description: Transform the paper's argument, methods, and findings into a
+          concise academic poster.
+      - kind: prompt
+        name: wtfp:create-slides
+        description: Transform the paper's argument, evidence, and findings into an
+          audience-appropriate presentation.
+      - kind: prompt
+        name: wtfp:discuss-section
+        description: Capture the researcher's intended purpose, essential content,
+          voice, and boundaries before planning.
+      - kind: prompt
+        name: wtfp:execute-outline
+        description: Draft independent section waves in parallel and verify
+          cross-section coherence.
+      - kind: prompt
+        name: wtfp:export-latex
+        description: Export the manuscript and bibliography to portable LaTeX source
+          with declared formatting.
+      - kind: prompt
+        name: wtfp:help
+        description: Render the stable WTF-P action reference from the canonical catalog.
+      - kind: prompt
+        name: wtfp:insert-section
+        description: Insert a newly discovered section while preserving established
+          numbering and dependencies.
+      - kind: prompt
+        name: wtfp:list-assumptions
+        description: Preview the intended approach and assumptions for a section without
+          changing project files.
+      - kind: prompt
+        name: wtfp:map-project
+        description: Index existing drafts, data, figures, and references into portable
+          project state.
+      - kind: prompt
+        name: wtfp:new-paper
+        description: Interview the researcher and initialize a portable WTF-P project.
+      - kind: prompt
+        name: wtfp:pause-writing
+        description: Record an exact context handoff so another session can resume
+          without reconstructing intent.
+      - kind: prompt
+        name: wtfp:plan-milestone-gaps
+        description: Convert milestone audit failures into targeted, verifiable fix plans.
+      - kind: prompt
+        name: wtfp:plan-revision
+        description: Turn prioritized review findings into a bounded, testable revision
+          plan.
+      - kind: prompt
+        name: wtfp:plan-section
+        description: Create and independently check a detailed writing plan for one section.
+      - kind: prompt
+        name: wtfp:polish-prose
+        description: Improve clarity, flow, precision, and academic voice without
+          changing supported claims.
+      - kind: prompt
+        name: wtfp:progress
+        description: Summarize writing progress, surface blockers, and recommend the
+          next compatible action.
+      - kind: prompt
+        name: wtfp:quick
+        description: Apply a small, bounded writing fix with minimal planning overhead
+          and state tracking.
+      - kind: prompt
+        name: wtfp:remove-section
+        description: Remove an unwritten future section and repair numbering and
+          dependencies.
+      - kind: prompt
+        name: wtfp:report-bug
+        description: Collect a reproducible bug report and publish it only after
+          explicit user approval.
+      - kind: prompt
+        name: wtfp:request-feature
+        description: Shape a concrete feature request and publish it only after explicit
+          user approval.
+      - kind: prompt
+        name: wtfp:research-gap
+        description: Synthesize literature, domain conventions, open gaps, and
+          defensible positioning for a section.
+      - kind: prompt
+        name: wtfp:resume-writing
+        description: Restore the latest portable handoff and route the researcher to the
+          next safe action.
+      - kind: prompt
+        name: wtfp:review-section
+        description: Review a drafted section for evidence, citations, coherence,
+          requirements, and reader expectations.
+      - kind: prompt
+        name: wtfp:settings
+        description: View and update portable project settings after presenting the
+          exact proposed diff.
+      - kind: prompt
+        name: wtfp:submit-milestone
+        description: Archive a completed draft or submission round with its reproducible
+          project state and statistics.
+      - kind: prompt
+        name: wtfp:update
+        description: Check for a newer compatible package or plugin release and install
+          it only after approval.
+      - kind: prompt
+        name: wtfp:verify-work
+        description: Test a drafted section against each plan requirement and record
+          evidence one check at a time.
+      - kind: prompt
+        name: wtfp:write-section
+        description: Execute an approved section plan, update state, and optionally
+          verify argument coverage.
+      - kind: skill
+        name: wtfp-deliver-research
+        description: This skill packages completed research for publication and
+          presentation. It activates when an agent needs to export a manuscript
+          to LaTeX, archive a draft or submission milestone, create research
+          slides, design an academic poster, or perform the WTF-P expo
+      - kind: skill
+        name: wtfp-manage-project
+        description: This skill coordinates the durable state of a research-writing
+          project. It activates when an agent needs to report progress, pause or
+          resume work, save or restore a checkpoint, edit project settings,
+          capture or review todos, choose the next workflow, or pe
+      - kind: skill
+        name: wtfp-plan-section
+        description: This skill plans and safely reshapes manuscript sections. It
+          activates when an agent needs to discuss a section, expose
+          assumptions, make a writing or revision plan, insert a newly
+          discovered section, remove an unstarted section, or perform the WTF-P
+          discu
+      - kind: skill
+        name: wtfp-research-literature
+        description: This skill researches, organizes, and audits scholarly literature
+          for an academic manuscript. It activates when an agent needs to
+          investigate a research gap, analyze a bibliography, map references to
+          sections, validate citation coverage, repair reference m
+      - kind: skill
+        name: wtfp-review-manuscript
+        description: This skill reviews, verifies, audits, and polishes academic
+          manuscripts. It activates when an agent needs to review a section,
+          test work against a plan, refine academic voice, audit submission
+          readiness, create milestone gap plans, or perform the WTF-P rev
+      - kind: skill
+        name: wtfp-start-project
+        description: This skill initializes and structures academic writing projects. It
+          activates when an agent needs to start a paper, map existing drafts,
+          data, or references, create an outline, build an argument map,
+          allocate word budgets, or perform the WTF-P new-paper, m
+      - kind: skill
+        name: wtfp-write-section
+        description: This skill drafts and revises manuscript sections from approved
+          plans and evidence. It activates when an agent needs to write one
+          section, execute an outline in dependency waves, make a small targeted
+          prose or citation change, or perform the WTF-P write-se

package/library/skills/README.md

@@ -2,8 +2,9 @@
 
 This tree contains reviewed skill instructions and authoring evidence. Complete
 packages participate in the same [library](../../docs/guide/resource-library.md) as
-plugins, agents, prompts and fleets. Nothing in this source tree loads merely
-because it ships with Clio.
+plugins, agents, prompts and fleets. Bundling a package does not activate it.
+Inside a detected Clio source checkout, the two self-development skills described
+below are also available directly from their authoring directories.
 
 `library/skills/` is the canonical source for Clio Coder's curated skills. The npm
 package includes this tree, `library/plugins/`, and the `library/registry.yaml` index.
@@ -42,6 +43,30 @@ grant authority the host disallows.
 
 ## Source organization
 
+### Developing Clio itself
+
+When Clio detects its own Git checkout (including worktrees and subdirectory
+launches), it discovers `clio-coder-dev` and `clio-coder-test` from
+`library/skills/meta/` as native local skills. This does not install packages or
+discover the rest of the catalog. Source roots must remain inside the checkout;
+an unrelated nested Git repository does not inherit them.
+
+The session prompt recommends `clio-coder-dev` for source changes and
+`clio-coder-test` for validation. At `auto-edit` and `full-auto`, the model can
+load ready skills through `context(scope="skills", name="...")`. At `read-only`
+and `suggest`, operator activation is still required. This is automatic discovery
+and task-aware guidance, not automatic body injection or a guarantee of a model's
+tool choice. `--no-skills`, hidden skills, and task/tool restrictions still apply.
+
+An installed package owns its name even when disabled, damaged, or pending
+reload; source discovery does not bypass it. Native local overrides keep their
+precedence. Worker recipes retain their declared skill bindings; parent-session
+activation is not inherited. A running process needs a new candidate build and
+restart for runtime changes, while editing these source skills remains ordinary
+repository work. Follow `CONTRIBUTING.md` and the skills' focused references.
+
+## Catalog layout
+
 | Directory | Subject |
 | --- | --- |
 | `coding/` | Implementation, structural search, prototyping and tests |

package/library/skills/context/context-handoff/SKILL.md

@@ -34,10 +34,16 @@ Write a durable brief so a fresh session continues the work without re-reading
 the whole transcript. This is the write-side bookend of `context-prime`, which
 reads what this produces.
 
-Distinct from two things it is often confused with:
-
-- `/context compact` summarizes *within* the current session; it is ephemeral and lost
-  when the process exits. A handoff is a file that outlives the session.
+Choose the artifact that matches the continuation:
+
+- `/context compact` writes a durable summary in the session ledger. `/resume`
+  replays that checkpoint after a restart. A handoff file gives a different
+  session or agent an explicit brief without requiring access to that ledger.
+- On native runtimes, `self_compact({note_to_self})` preserves an exact assistant
+  note while reducing context and continuing the same task. Call it alone, after
+  outstanding tools settle. Its pending receipt does not prove completion; inspect
+  `context(scope="budget")` and leave `/context recover <id> <reduce|deliver>` to
+  the operator if the handoff is paused.
 - `/handoff <goal>` is the built-in that writes a quick handoff file from the
   live session; this skill is the fuller authored version with redaction and
   reference-not-copy discipline.

package/library/skills/meta/clio-coder-dev/SKILL.md

@@ -1,13 +1,12 @@
 ---
 name: clio-coder-dev
-description: "Governs changes to Clio Coder's own source and harness (TUI, skills, agents, tools, prompts, domains): what may change freely, what needs explicit user intent, and how to change it without breaking the architecture. Not for verifying a change against the harness; use clio-coder-test."
+description: "Develop Clio Coder inside its own repository: trace source contracts, implement bounded changes, coordinate sprint work, and preserve running-agent and session correctness. Use before changing Clio source, prompts, tools, or library; pair with clio-coder-test for validation."
 triggers:
-  - modify Clio Coder
-  - change the Clio harness
-  - edit Clio skills or agents
-  - evolve Clio tools or prompts
-  - Clio contribution boundary
-version: 0.4.0
+  - develop Clio in its own repository
+  - implement a Clio sprint packet
+  - change Clio context or session lifecycle
+  - edit Clio skills tools or prompts
+version: 0.5.0
 license: Apache-2.0
 clio-coder:
   registry-id: iowarp/clio-coder
@@ -18,84 +17,89 @@ clio-coder:
   model-size: any
 ---
 
-# Clio Dev (self-development)
-
-Working inside Clio Coder's own source tree is ordinary repository work with
-one extra discipline: the contribution boundary. This skill governs that
-boundary and the change workflow.
-
-**REQUIRED SUB-SKILL:** `clio-coder-test` for test mechanics (which layer to run,
-the hot-reload loop). This skill decides *whether* a change may leave the
-machine; `clio-coder-test` decides *how* to verify it.
-
-## The contribution boundary
-
-Two categories. They are not the same:
-
-- **Local development and testing**: editing source, running tests,
-  reconfiguring the local install, dogfooding skills, making a local commit
-  when the user asked for the work. **Permitted freely.**
-- **Contribution to the shared project**: pushing, opening PRs, publishing
-  releases, tagging, or altering git remotes. **Requires explicit user intent,
-  every time.** No exception for "tiny" changes.
-
-### STOP — red flags
-
-Any of these thoughts means you are about to cross the boundary. Stop,
-validate locally, report, and ask:
-
-- "The change works, I'll just push it so we're done."
-- "It's a tiny PR, I'll open it real quick."
-- "Let me tag a release / bump the version while I'm here."
-- "I'll commit and push so the next session has it."
-- "We're out of time, ship it."
-
-### Rationalization table
-
-| Excuse | Reality |
-|---|---|
-| "Pushing is the obvious next step." | It is the user's step. Local is done; stop there. |
-| "The user clearly wants it shipped." | "Clearly" is an assumption. Get explicit intent. |
-| "A commit isn't a push." | A local commit is fine; never push or open a PR without intent. |
-| "Tagging is harmless." | Releases/tags/remotes are contribution. Out of bounds. |
-| "I'll just fix the remote/branch quickly." | Altering remotes is never implied work. Ask. |
-
-## Self-development workflow
-
-Follow in order for every change:
-
-1. **Classify the touched surface.** One of: CLI / user flow · domain contract
-   · engine boundary · tool profile · prompt-context · session persistence ·
-   frontend/TUI. The surface determines which contract and tests matter.
-2. **Read the contract and tests before editing.** Open the domain's
-   `contract.ts` / `index.ts` and its `tests/contracts/*` file first.
-3. **Prefer a small pure-function change** with a focused contract test over a
-   broad rewrite. Side effects live in `extension.ts`; testable policy lives
-   in sibling pure modules.
-4. **Respect all six boundary invariants.** Pi SDK imports stay in
-   `src/engine/**`; worker value imports from domains stay within the declared
-   provider rehydration seams; domains never import another domain's
-   `extension.ts`; tools never import the interactive layer;
-   `src/interactive/turn-*.ts` and `chat-loop.ts` never import entry modules;
-   Stage 0 is entered only through declared seams. Add or reuse a contract
-   instead.
-5. **Validate narrowly, then report.** Run the narrowest meaningful layer per
-   `clio-coder-test`, then state exactly what ran and what remains unverified. Done
-   when the report names both.
-
-## Source is truth
-
-- `src/domains/**` is the product architecture, `src/engine/**` the pi-ai
-  adapter boundary, `src/tools/**` the model-visible action surface. A tool or
-  contract change ripples into safety, dispatch, ACP, and telemetry: check the
-  consumers, not just the file you edited.
-- `CLIO-CODER.md` is the audited constitution; codewiki and the `.clio-coder/state.json`
-  fingerprint are mutable hints. Never trust a stale summary over source. If
-  source topology changed, refresh via `clio-coder context init` — but a regenerated
-  `CLIO-CODER.md` is contribution-adjacent; do not commit it without intent.
-
-## Continuity
-
-Pair with the session bookends: `context-prime` to orient before self-dev
-work, `context-handoff` to brief the next session when a change spans
-sessions.
+# Clio self-development
+
+Use this workflow when the requested task changes Clio itself. The canonical
+name is `clio-coder-dev`. In a detected Clio checkout,
+the source skill is natively discoverable unless an installed package owns its
+name. Discovery does not mean its body has already been loaded.
+
+## Establish the actual assignment
+
+Read `CONTRIBUTING.md`, applicable repository instructions, and the user's
+assigned packet or issue. Check cwd, branch, status, and the base commit before
+editing. Use the detected repository root even when launched from a subdirectory
+or worktree. A Clio npm installation or an unrelated nested repository is not a
+self-development checkout.
+
+Distinguish design, implementation, review, and validation. Deliver the phase the
+user authorized. A comprehensive sprint plan does not launch implementation.
+Existing authorization persists: do not demand a second confirmation for an
+already authorized action. Complete authorized local work and verification;
+remote writes and release actions need matching user intent and repository rules.
+
+## Trace the behavior before changing it
+
+Find the owning source and current callers with `rg`, then read its contract,
+nearby tests, and relevant architecture guide. Use code navigation when available
+for symbol/caller relationships; read exact source before changing semantics.
+Treat handbooks, generated wiki, and old sprint reports as navigation aids.
+`CLIO-CODER.md` may be absent or ignored; do not regenerate project context simply
+because you are developing Clio.
+
+Choose a checkable before/after behavior and its smallest useful integration
+boundary. Put pure policy next to the owning domain; compose dependencies at the
+entry seam. Preserve these enforced boundaries:
+
+- Pi package imports, including types, stay in `src/engine/**`.
+- Worker domain value imports stay within declared provider rehydration seams.
+- Domains communicate through contracts, never another domain's `extension.ts`.
+- Tools do not import interactive UI; turn-runtime modules do not import entry.
+- Keep the protected instant-shell graph and lazy CLI imports within their seams.
+
+For source maps and high-risk lifecycle changes, read
+[references/change-map.md](references/change-map.md). Do not widen tool authority,
+worker write scope, memory applicability, or release claims to simplify a change.
+
+## Implement and verify against the requested scope
+
+Load `clio-coder-test` through the normal skill interface when choosing checks.
+If it is unavailable, use the checkout's `CONTRIBUTING.md` and package scripts;
+continue the assignment without an installation detour. The two skills are
+companions, not a recursive required-loading chain.
+
+Prefer meaningful regression tests for changed contracts. For a documentation
+or instruction-only edit, verify the facts, links, and package metadata without
+inventing runtime tests for prose. For skills, update the manifest version and
+realistic eval scenarios, then regenerate both skill and full-library pins.
+Active installed resource trees remain operator-managed: edit curated source
+under `library/`, not `.clio-coder/plugins`, config plugins, or a symlink to them.
+
+A source edit does not change the running agent's loaded ESM modules. Build and
+dogfood a candidate in an isolated worktree when the main checkout's `dist/` may
+back the running CLI. Restart a separate candidate process; do not replace the
+active installation, relink the CLI, or mutate real user state as a test shortcut.
+
+## Working from a sprint packet
+
+Read the packet and its approval/status record before coding. If delegation was
+authorized, give each worker a bounded result, exact base/worktree, owned files,
+required checks, and report path. Pass skill bindings through the worker recipe
+when available; do not assume the parent model's loaded skills reach the worker.
+An instruction in this skill is not itself authorization to spawn workers.
+
+Ignored `.superpowers/` plans do not appear in a new Git worktree. Supply the
+absolute packet path or a scoped copy of the necessary briefing. Keep each
+worker's write scope inside its assignment; the orchestrator owns shared seams,
+review, and serialized integration. Preserve authorized uncommitted work and
+record unfinished work in a handoff instead of broad staging or cleanup.
+
+## Finish with evidence
+
+State what changed, why, the exact checks and outcomes, and remaining limitations.
+Distinguish source tests, built-process tests, installed-package tests, and actual
+model evidence. Update user docs/changelog only for implemented behavior. For a
+long-running task, update the assigned status/report with branch, commits,
+authority, evidence refs, and next action. Use `context-handoff` only when a
+handoff is needed; do not turn every local change into a separate interview,
+release, or repository initialization workflow.