@uniqbit/mate-core 0.18.4 → 1.0.0-canary.0

package/src/templates/mate-skills/claude/mate-apply-change/references/openspec-apply-change.md

@@ -0,0 +1,198 @@
+<!-- Vendored from OpenSpec 1.15.0: the `openspec-apply-change` workflow its `claude` tool generates.
+     Copyright (c) OpenSpec Contributors, MIT License (see THIRD-PARTY-NOTICES.md in Mate).
+     Regenerated by `bun run vendor:openspec`; do not edit. -->
+
+Implement tasks from an OpenSpec change.
+
+**Store selection:** If the user names a store (a store is a standalone OpenSpec repo registered on this machine) or the work lives in one, run `openspec store list --json` to discover registered store ids, then pass `--store <id>` on the commands that read or write specs and changes (`new change`, `status`, `instructions`, `list`, `show`, `validate`, `archive`, `doctor`, `context`, `schemas`, `view`). Once selected, treat `--store <id>` as sticky for the rest of the workflow. Every unscoped example of those commands below is shorthand: before running it, append the flag. For example, run `openspec status --change "<name>" --json --store "<id>"`, not the unscoped form shown below. Other commands do not take the flag. Hints printed by commands already carry the flag; keep it on follow-ups. Without a store, commands act on the nearest local `openspec/` root.
+
+**Project check:** These steps expect a project that already uses OpenSpec. Before the first step that writes anything (`new change`, `archive`, `sync specs`, or authoring an artifact file), confirm the project has a root: run `openspec list --json` (with `--store <id>` when a store is selected, since the store is then the root) and read `root`. A root object means the project is set up. `"root": null` means it is not - there is no `openspec/` directory here, and a write such as `openspec new change` would create one as a side effect. The command also exits non-zero, which is that answer rather than a broken CLI, so read the JSON instead of retrying or working around it.
+
+One `"root": null` is not about setup: when a `status` error message starts with `Declared in` or `Invalid store declaration in` and names this project's `openspec/config.yaml` (or `config.yml`), the project does use OpenSpec through a store it declares, which this machine cannot resolve (the store is not registered, or the `store:` line is malformed). Do not treat it as uninitialized and skip the branches below: stop before writing and show the user that error's `message` and `fix`.
+
+Otherwise, with no root, what happens next depends on how this workflow was reached:
+
+- **Auto-selected**: you chose this workflow yourself, without the user naming OpenSpec, naming this skill, or running its slash command. Stop using OpenSpec and answer the request normally, as you would with no OpenSpec installed. Do not ask them to set anything up and do not mention OpenSpec setup.
+- **Explicit OpenSpec request**: the user named OpenSpec, named this skill, or ran its slash command. Stop before writing and ask how to proceed: set this project up (`openspec init`), target a store they already have (`--store <id>`), or continue without OpenSpec for this request. Wait for their answer.
+
+In both branches, never create the root as a side effect: do not run `openspec init` until the user asks for it, do not hand-create `openspec/` files, and do not let a command create it.
+
+**Input**: Optionally specify a change name (e.g., `/mate-apply-change add-auth`). If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.
+
+**Steps**
+
+1. **Select the change**
+
+   If a name is provided, use it. Otherwise:
+   - Infer from conversation context if the user mentioned a change
+   - Auto-select if only one active change exists
+   - If ambiguous, run `openspec list --json` to get available changes and ask the user to select one
+
+   Always announce: "Using change: <name>" and how to override (e.g., `/mate-apply-change <other>`).
+
+2. **Check status to understand the schema**
+   ```bash
+   openspec status --change "<name>" --json
+   ```
+   Parse the JSON to understand:
+   - `schemaName`: The workflow being used (e.g., "spec-driven")
+   - `planningHome`, `changeRoot`, and `actionContext`: planning scope and edit constraints
+   - Which artifact contains the tasks (typically "tasks" for spec-driven, check status for others)
+
+3. **Get apply instructions**
+
+   ```bash
+   openspec instructions apply --change "<name>" --json
+   ```
+
+   This returns:
+   - `contextFiles`: artifact ID -> array of concrete file paths (varies by schema - could be proposal/specs/design/tasks or spec/tests/implementation/docs)
+   - Progress (total, complete, remaining)
+   - Task list with status, source path, and source line
+   - Dynamic instruction based on current state
+   - Optional `context`: current required project instruction input from the selected root
+   - Optional `operationGuidance`: current advisory guidance for apply
+   - `missingArtifacts` (when present): required artifact ids with no output
+
+   **Handle states:**
+   - If `state: "blocked"`: show the message and pause implementation.
+     - If `missingArtifacts` is non-empty: suggest completing the missing artifacts. Run `openspec status --change "<name>" --json`, select the next `ready` artifact (not `skipped` or `blocked`), and use `openspec instructions "<artifact-id>" --change "<name>" --json` for its rules and template. Keep the selected `--store <id>` on both commands.
+     - Otherwise, follow the CLI instruction to create or repair the schema-configured tracking file from existing planning artifacts. Do not assume another artifact is ready or start implementation while blocked.
+   - If `state: "all_done"`: report that all tracked tasks are complete and suggest review or verification as appropriate before archiving
+   - Otherwise: proceed to implementation
+
+   Treat `context` as a required prompt-level input. Read and consider it, and
+   apply relevant project facts, conventions, and constraints while implementing.
+   Treat `operationGuidance` as optional additive advice. Read and consider every
+   entry, and follow entries that are applicable and compatible with the built-in
+   workflow.
+
+   Keep both fields separate from CLI-returned state, missing artifacts, tasks,
+   progress, `contextFiles`, and the built-in `instruction`. They are not
+   evidence of task completion, do not replace the built-in instruction, and do
+   not permit bypassing a blocked state. If context conflicts with the built-in
+   instruction, an explicit user choice, or a CLI-controlled value, report the
+   conflict and preserve the controlling value. If guidance is inapplicable or
+   conflicts with those controlling inputs, do not follow it and explain why.
+   These are prompt-level behavior contracts, not enforceable checks.
+
+4. **Read context files**
+
+   Read every file path listed under `contextFiles` from the apply instructions output.
+   The files depend on the schema being used:
+   - **spec-driven**: proposal, specs, design, tasks
+   - Other schemas: follow the contextFiles from CLI output
+
+   Do not copy `context` or `operationGuidance` verbatim into implementation
+   files or planning artifacts unless the user separately asks for that content.
+
+5. **Show current progress**
+
+   Display:
+   - Schema being used
+   - Progress: "N/M tasks complete"
+   - Remaining tasks overview
+   - Dynamic instruction from CLI
+
+6. **Implement tasks (loop until done or blocked)**
+
+   For each pending task:
+   - Show which task is being worked on
+   - Make the code changes required
+   - Keep changes minimal and focused
+   - Before editing, confirm the checkbox at the returned `sourcePath` and `line` still matches the task description; if it does not, rerun the apply instructions and use the refreshed location
+   - Mark the task complete at its returned `sourcePath` and `line`: `- [ ]` → `- [x]`
+   - Rerun the apply instructions and confirm that task is now done and progress changed
+   - Continue to next task
+
+   **Pause if:**
+   - Task is unclear → ask for clarification
+   - Implementation reveals a design issue → suggest updating artifacts
+   - A task needs work beyond what the spec and tasks describe, or you are tempted to drop, narrow, defer, or accept exceptions to specified behavior to make it fit → surface the added scope and ask; do not absorb it silently
+   - Error or blocker encountered → report and wait for guidance
+   - User interrupts
+
+7. **On completion or pause, show status**
+
+   Display:
+   - Tasks completed this session
+   - Overall progress: "N/M tasks complete"
+   - If all done: report that tracked tasks are complete and suggest review or verification as appropriate before archiving
+   - If paused: explain why and wait for guidance
+
+**Output During Implementation**
+
+```
+## Implementing: <change-name> (schema: <schema-name>)
+
+Working on task 3/7: <task description>
+[...implementation happening...]
+✓ Task complete
+
+Working on task 4/7: <task description>
+[...implementation happening...]
+✓ Task complete
+```
+
+**Output On Completion**
+
+```
+## Implementation Complete
+
+**Change:** <change-name>
+**Schema:** <schema-name>
+**Progress:** 7/7 tasks complete ✓
+
+### Completed This Session
+- [x] Task 1
+- [x] Task 2
+...
+
+All tracked tasks are complete. Review or verify the change as appropriate
+before archiving. You can archive this change with `/mate-archive-change`.
+```
+
+**Output On Pause (Issue Encountered)**
+
+```
+## Implementation Paused
+
+**Change:** <change-name>
+**Schema:** <schema-name>
+**Progress:** 4/7 tasks complete
+
+### Issue Encountered
+<description of the issue>
+
+**Options:**
+1. <option 1>
+2. <option 2>
+3. Other approach
+
+What would you like to do?
+```
+
+**Guardrails**
+- Keep going through tasks until done or blocked
+- Always read context files before starting (from the apply instructions output)
+- If task is ambiguous, pause and ask before implementing
+- If implementation reveals issues, pause and suggest artifact updates
+- Keep code changes minimal and scoped to each task
+- Update task checkbox immediately after completing each task
+- Pause on errors, blockers, or unclear requirements - don't guess
+- When a task needs work beyond what the spec describes, surface the added scope and pause - never silently narrow, defer, or simplify away specified behavior
+- Only mark a task `- [x]` when its specified behavior is fully implemented, not when it is partially done or deferred
+- Use contextFiles from CLI output, don't assume specific file names
+- Use each task's sourcePath and line to update its exact checkbox
+- Do not use context or operation guidance as proof that a task is complete
+- Apply relevant project context; report conflicts with controlling workflow inputs
+- Consider every guidance entry; explain any inapplicable or conflicting advice
+- Do not copy runtime context or operation guidance into implementation files or planning artifacts
+- Preserve CLI-controlled blocked/ready/all-done behavior and completion criteria
+
+**Fluid Workflow Integration**
+
+This skill supports the "actions on a change" model:
+
+- **Can be invoked anytime**: Before all artifacts are done (if tasks exist), after partial implementation, interleaved with other actions
+- **Allows artifact updates**: If implementation reveals design issues, suggest updating artifacts - not phase-locked, work fluidly

package/src/templates/mate-skills/claude/mate-archive-change/SKILL.md

@@ -0,0 +1,59 @@
+---
+name: mate-archive-change
+description: Archive a change through mate artifact archive, which records its delivery, reports merge state and its warnings, and runs the OpenSpec archive, also before the merge. Use when the user wants to archive, finalize, or close out an implemented change.
+allowed-tools: Bash(mate:*), Bash(git:*)
+license: MIT
+compatibility: Requires the mate CLI and the openspec capability enabled.
+metadata:
+  author: mate
+  version: "1.0"
+---
+
+# Mate Archive Change
+
+The Archive change stage of the Delivery Path. Archiving applies the change's delta
+specs to the local canonical specs, so a feature's later changes build on it. It is
+allowed **before** the delivery branch merges: publication, not archive, waits for the
+merge. Archiving is local and uncommitted; it publishes nothing.
+
+## Steps
+
+1. **Archive.**
+
+   ```bash
+   mate artifact archive "<change-name>" --json
+   ```
+
+   Run it from the companion or the linked Working Repository. It shows warnings,
+   refreshes merge state from the forge when a token is available, writes the change's
+   `delivery.yaml`, and runs `openspec archive` itself. Do not run `openspec archive`
+   separately.
+
+2. **Answer a missing branch.** When the result's `status` is `needs-branch`, nothing
+   was archived. Ask the user which branch delivers the change, suggesting
+   `suggestedBranch` when it is set, and re-run with exactly one of:
+
+   - `--branch "<branch>"` — a protected branch only with `--direct`, after the user
+     explicitly confirms a direct delivery;
+   - `--not-applicable "<reason>"` — for a specification-only change;
+   - `--skip-branch` — when the user skips the question; publication will ask again.
+
+3. **Report.** Relay every entry of `warnings` first: another active change that
+   modifies the same requirement, a declared dependency that is not archived yet, or
+   planning artifacts its schema requires that are missing (`incomplete-planning`).
+   Warnings never block. Then report the archive `path` and the delivery: each branch
+   with its merge result and source (`forge` or `user`) and PR link, or the
+   not-applicable reason. An open or unknown merge is information, not a failure.
+
+4. **Hand off.** Name `/mate-publish-artifact` as the next step and say that
+   publication holds the archive back until its delivery branch is merged. Do not
+   invoke it.
+
+When `status` is `failed`, report the message (typically incomplete tasks or a
+validation error) and stop.
+
+## Guardrails
+
+- Never commit, tag, or push; publication is `mate-publish-artifact`.
+- A merger account is provenance, never an artifact review.
+- Do not read or echo `MATE_GIT_TOKEN`.

package/src/templates/mate-skills/{agents/mate-openspec-backfill → claude/mate-backfill-spec}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: mate-openspec-backfill
+name: mate-backfill-spec
 description: Reverse-engineer an OpenSpec spec for one existing feature and write it directly to the canonical spec, ready to publish. Use when the user wants to backfill, document, or spec existing or legacy behavior that has no spec yet.
 allowed-tools: Bash(openspec:*), Bash(mate:*), Bash(git remote:*), Bash(git diff:*)
 license: MIT
@@ -11,7 +11,7 @@ metadata:
 
 # Mate OpenSpec Backfill
 
-Specify one feature that already exists in the working repository. A backfill records behavior that already shipped, so the run writes the canonical spec `openspec/specs/<capability>/spec.md` directly and leaves it uncommitted. It never creates a change and never publishes; publication happens afterwards through `mate-artifact-publish`.
+Specify one feature that already exists in the working repository. A backfill records behavior that already shipped, so the run writes the canonical spec `openspec/specs/<capability>/spec.md` directly and leaves it uncommitted. It never creates a change and never publishes; publication happens afterwards through `mate-publish-artifact`.
 
 ## Scope rules
 
@@ -70,12 +70,12 @@ Specify one feature that already exists in the working repository. A backfill re
 
    Fix every reported error and re-validate until it passes. Do not hand off a spec that fails validation.
 
-8. **Hand off.** Report the written path and show the uncommitted diff (`git diff -- openspec/specs/<capability>/`, or the file itself when it is new). Point the user to `mate-artifact-publish`: the spec appears there under **Drifted specs** and can be published on its own or with the rest.
+8. **Hand off.** Report the written path and show the uncommitted diff (`git diff -- openspec/specs/<capability>/`, or the file itself when it is new). Point the user to `mate-publish-artifact`: the spec appears there under **Drifted specs** and can be published on its own or with the rest.
 
 ## Guardrails
 
 - Never create an OpenSpec change, change artifacts, or verification tasks, and never archive.
-- Never commit, tag, push, or publish — never run `mate artifact publish`. Publication belongs to `mate-artifact-publish`.
+- Never commit, tag, push, or publish — never run `mate artifact publish`. Publication belongs to `mate-publish-artifact`.
 - Never write any file before the user approves the review table.
 - Never write a requirement without a citation in the review table, and never spec a suspected bug without the user's ruling.
 - Never write citations or evidence tags into the canonical spec.

package/src/templates/mate-skills/claude/mate-clarify-intent/SKILL.md

@@ -0,0 +1,95 @@
+---
+name: mate-clarify-intent
+description: Pick the pre-explore mode a request needs (interview, grilling, or skip) from what it already states, then run that one mode. Use only when the user explicitly starts clarifying an idea before exploring a change.
+disable-model-invocation: true
+license: MIT
+compatibility: Requires the mate CLI and the openspec capability enabled.
+metadata:
+  author: mate
+  version: "1.0"
+---
+
+# Mate Clarify Intent
+
+The optional first stage of the Delivery Path. It runs before `/mate-explore-change`
+and decides how much clarification a request needs: an interview when intent is
+incomplete, grilling when intent is clear but a proposed direction needs testing, or
+nothing at all for a small, fully specified change.
+
+Read only the user's request and this conversation. Do not read or investigate the
+repository; questions that need repository evidence go to explore.
+
+## Step 1: Fill the slot table
+
+Mark each slot `stated`, `implied`, or `missing` from the request and conversation:
+
+| Slot       | Question                                      |
+| ---------- | --------------------------------------------- |
+| Who        | Who benefits or is affected?                  |
+| Why        | What problem or change makes this needed now? |
+| Success    | How will we know it worked?                   |
+| Constraint | What limit binds the solution?                |
+
+`implied` Success counts as `missing`: a guessed success measure is the gap this stage
+exists to close. Then note whether the request proposes a direction (an approach,
+design, or solution shape): yes or no.
+
+## Step 2: Route
+
+Apply the first rule that matches:
+
+1. Any slot `missing` → **interview**.
+2. All slots filled and a direction is proposed → **grill**.
+3. All slots filled, no direction, and the change is minimal-eligible (one Area, low
+   risk, no new dependency or data-model change) → **skip**.
+4. Otherwise → **grill**.
+
+## Step 3: Announce and accept an override
+
+Show the slot table with each slot's mark, the direction answer, and the route with
+its rule in one line, for example:
+
+```text
+Route: interview — Success is missing.
+Reply `interview`, `grill`, or `skip` to switch; anything else continues.
+```
+
+A one-word reply `interview`, `grill`, or `skip` replaces the route without further
+questions. Run exactly one mode.
+
+## Step 4: Run the routed mode
+
+Run the mode by **reading its instructions and following them**, not by invoking a
+skill. Resolve the file relative to this skill's own directory:
+
+- **interview** → read `../mate-interview-me/SKILL.md` and follow it from its first
+  step.
+- **grill** → read `../mate-grill-me/SKILL.md` and follow it.
+- **skip** → run nothing.
+
+`mate-interview-me` and `mate-grill-me` are manual-only skills: never call them through
+the skill mechanism. Reading the file is the supported way to run them from here. If
+the file is missing, report that the companion's Mate skills need
+`mate companion update` and stop.
+
+## Step 5: Hand off
+
+A routed mode ends with its own `PRE-EXPLORE HANDOFF` block naming
+`/mate-explore-change`. For **skip**, emit:
+
+```text
+PRE-EXPLORE HANDOFF (skip)
+Confirmed:   <the four slots as stated>
+Unresolved:  none
+Assumptions: <points explore should verify, or "none">
+Next: /mate-explore-change
+```
+
+Tell the user the next step is `/mate-explore-change`; do not invoke it.
+
+## Mate Boundary
+
+Conversational only. Do not create or modify code, context files, ADRs, OpenSpec
+artifacts, or any other file. This skill runs before `/mate-explore-change`: wide
+repository investigation and option comparison belong there, recorded under
+Unresolved or Assumptions in the handoff.

package/src/templates/mate-skills/claude/mate-explore-change/SKILL.md

@@ -0,0 +1,50 @@
+---
+name: mate-explore-change
+description: Explore a change with its Working Repository and Area resolved from the companion context map, and suggest slicing a large feature into several changes. Builds on the OpenSpec explore workflow. Use when the user wants to explore, investigate, or think through a change before proposing it.
+allowed-tools: Bash(mate:*), Bash(openspec:*), Bash(git:*)
+license: MIT
+compatibility: Requires the mate CLI and the openspec capability enabled.
+metadata:
+  author: mate
+  version: "1.0"
+---
+
+# Mate Explore Change
+
+The Explore change stage of the Delivery Path. It runs the OpenSpec explore workflow
+and adds two things: the scope comes from the companion context map, and a feature too
+large for one change is suggested as several.
+
+## Steps
+
+1. **Follow the OpenSpec workflow.** Read
+   [references/openspec-explore.md](references/openspec-explore.md) and follow it for the
+   exploration itself. When a `PRE-EXPLORE HANDOFF` block is in this conversation, treat
+   its Confirmed points as settled and start from its Unresolved questions and
+   Assumptions.
+
+2. **Resolve scope from the context map.** Before reading code, identify the canonical
+   Working Repository (`org/repository` from its Git remote) and the repository-relative
+   Area (the owning package root in a monorepo). Read the Companion Repository's
+   `CONTEXT-MAP.md`, then only the repository-scoped map for that Working Repository,
+   and load only the contexts it maps to that Area. Use their vocabulary in the
+   exploration. When the map has no entry for the Area, say so instead of borrowing
+   another Area's context.
+
+3. **Suggest slicing when the feature is large.** Slicing test: a feature needs
+   slicing when it spans several Areas, several independent behaviours, or more work
+   than one review can hold (roughly more than 10 tasks or 400 changed lines).
+   Several Areas that only work together stay one change with a scope per Area. When
+   the explored direction passes the test, propose slices: one change per slice,
+   each reviewable and archivable on its own, in dependency order. Name the
+   dependencies between slices; they become `dependsOn` entries when the changes are
+   proposed. Several slices may share one delivery branch. Slicing is a suggestion;
+   the user decides.
+
+4. **Hand off.** End by naming `/mate-propose-change` as the next step, once per agreed
+   slice. Do not invoke it.
+
+## Boundary
+
+Exploration writes no product code. Agent artifacts written while exploring go to the
+Companion Repository, never the Working Repository.