@plainconceptsplatform/agent-harness 3.9.0 → 3.11.0

package/skills/pc-plan-apply/SKILL.md

@@ -1,90 +1,92 @@
----
-name: pc-plan-apply
-description: Implement tasks from a plan. OpenSpec-annotated tasks (from pc-plan-propose) run as parallel subagent waves; Todo pane tasks (from /plan-quick) run sequentially in-session. Load when implementing a prepared plan. Invoked by the /plan-apply command (interactive) and the plan-goal pipeline (autonomous).
-license: MIT
----
-
-# Plan Apply
-
-## Input
-
-The caller provides (all optional):
-- A mode (see below). Default: `interactive`.
-- A `start_from` hint: `branch` (default, full protocol from step 1) or `load-plan` (the caller already created the feature branch; skip step 1).
-
-## Modes
-
-- `interactive` (default): report progress to the user and surface failures for their decision.
-- `autonomous`: there is no user to return to between waves. Loop until every task is DONE, or until the progress guard or the retry limit trips, then report to the caller, whose failure policy governs. APPLY completes by handing control back to `/plan-goal`, which has four phases left to run: `N/N tasks` is this stage's boundary, not the pipeline's.
-
-## Plan source detection
-
-1. Check if an OpenSpec change exists: inspect `openspec/changes/` for an active change folder with a `tasks.md`.
-2. If found and tasks have `<!-- agent` annotations (written by `pc-plan-propose`): OpenSpec mode. Follow the protocol below. Annotated tasks run in subagent waves. They never become sequential lead work because the task count seems small, the lead prefers direct implementation, or a worker has not yet been inspected.
-3. If no OpenSpec change exists, but there are `pending` items in the Todo pane (from `/plan-quick`): Simple mode. Follow the [simple mode](simple-mode.md) reference.
-
-## OpenSpec mode: parallel subagent waves
-
-Load `@openspec-apply-change` for change selection, status, and closing. Its own implement step does not apply here: annotated tasks are implemented only by spawning the annotated tier worker, and the lead never implements. Take that step from the protocol below instead.
-
-Referring to it by number would break silently. `@openspec-apply-change` is installed by `openspec init --force` with no version pinned, so an inserted step upstream renumbers the one being replaced, and the sequential default would then run alongside these waves.
-
-**Implement via native subagent waves.**
-
-You are the lead. You orchestrate from this session only; you spawn workers with the native `task` tool. Workers are ephemeral (one batch, then they exit) and navigable (`ctrl+x` arrow down, left/right arrows). There is no board, no claiming, no merging, no external dashboard.
-
-Core rule: push, don't pull. A worker is born with its work: every `task()` spawn prompt contains the exact task IDs and text it must do. There is no claim step, so a worker can never sit idle waiting for an assignment.
-
-**1. Branch.** Create `feature/{change-slug}` if not already on one. (Skip this step when the caller passed `start_from: load-plan`.)
-
-**2. Load the plan and workers.** Parse `tasks.md`. Each task carries `<!-- agent, depends_on, touches -->` (from `pc-plan-propose`). Read `.opencode/harness-models.json` (written by `pc-subagent-tiers` and `node .opencode/scripts/sync-agents.mjs`) for the effective model of every tier and the generated agent files. If the manifest is missing, run `node .opencode/scripts/sync-agents.mjs` once; if it still fails, stop. The tier-suffixed name in an annotation (for example, `backend-engineer.build`) is the worker to spawn; its model is the manifest's, not `harness.json`'s. `harness.user.json` overrides `harness.json`, so never report a model from `harness.json` alone. Read `.opencode/harness.json` -> `agents.maxConcurrent` (the wave cap, 1 to 5, enforced by `pc-subagent-monitor`).
-
-When `.platform/contract.yml` declares `reuse` and the change's `proposal.md` has no `## What is reused` section, stop the APPLY stage and report it: the plan never checked what the template already ships. Otherwise every spawn prompt in step 7 carries that section.
-
-Before hydrating the Todo board, resolve every task's annotated worker. If any task has a blank agent annotation, its base template is missing, its tier variant is unavailable, or the manifest has no effective model for its tier, stop the APPLY stage and report the task ID, expected worker, and missing file. Do not replace the worker with `fullstack-engineer`, `general`, or the lead session.
-
-**3. Hydrate the Todo board.** `todowrite` one item per task: `pending`. The Todo pane is the visible subagent board (opencode plugins cannot draw a custom pane, so the native Todo widget is the live UI). While a task is in flight, its label must carry the worker: `<agent> · <model>`, with the model read from `.opencode/harness-models.json`, so the pane shows which agent on which model is doing what. The Todo list is a projection only: never read it for recovery; rebuild it from `tasks.md` and git and `.opencode/harness-run.json`.
-
-**4. Worker context.** Before each wave, derive file-disjointness from `touches:` globs and `git diff`.
-
-<!-- PC-OPTIMIZATION-CODEGRAPH-START -->
-<!-- PC-OPTIMIZATION-CODEGRAPH-END -->
-
-<!-- PC-OPTIMIZATION-MEMORY-START -->
-<!-- PC-OPTIMIZATION-MEMORY-END -->
-
-**5. The wave loop.** Repeat until no tasks remain:
-
-```
-eligible = unchecked tasks whose every depends_on is DONE (committed/checked)
-if eligible is empty but tasks remain  -> STALL: report blocked tasks + the failed
-                                           dependency causing it, then STOP.
-groups   = pack eligible tasks that share a file (touches and gathered context)
-            into ONE worker each, to run sequentially (the worker uses the task's `agent`)
-wave     = pick groups whose file-sets are pairwise DISJOINT, capped at maxConcurrentAgents
-            (opencode runs every task() you emit at once; a spawn past the cap
-             is denied, and a denied spawn is not a failed group: re-issue it)
-```
-
-**6. Context per group.** For each group, gather the task text, relevant plan decisions, and source context needed to implement it.
-
-**7. Spawn the wave: one assistant turn, multiple `task()` calls (they run in parallel).** For each group:
-- `subagent_type` = the task's `agent` exactly as written in `tasks.md` (e.g. `frontend-engineer.build`, `backend-engineer.fast`). It is the tier-suffixed `mode: subagent` worker created by `pc-subagent-tiers`. Worker resolution happened in step 2; a missing worker stops the stage before spawning. `fullstack-engineer`, `general`, and the lead session are not fallbacks for annotated implementation work.
-- `description` = `"<task-ids>: <short label>"` (e.g. `"2.1,2.2: RPC endpoints"`) so the subagent is legible in the left/right list and the monitor.
-- `prompt` must contain the exact task IDs and text plus the gathered context. The worker follows the Engineer workflow defined in `@pc-guardrails-generic`; do not restate it in the prompt. **Worker output discipline:** instruct each worker to return a compact summary: what it changed (file names, not contents), pass/fail status of any verification it ran, and any blockers. Workers must NOT return file contents or full diffs as their result — the lead can `git diff` if needed.
-- **Diff budget, in every prompt.** When `.opencode/scripts/check-diff.mjs` exists, the prompt says: comments stay under a tenth of the code added and only explain what the code cannot show; tests cover the public contract, about one test line per code line, and a bug fix gets one regression test; and before reporting, run `node .opencode/scripts/check-diff.mjs --paths <the group's touches, comma-separated>` and fix every finding. A worker that writes to the budget does not hand the lead a cleanup: Pliny-Bot #809's lead spent 13 of 65 minutes and fourteen `check-diff` runs trimming what its workers had written.
-- Flip each spawned task's Todo item to `in_progress` and prefix its label with `<agent>: ` (e.g. `frontend-engineer.build: 2.1 Consolidate logic`) so the running worker is visible in the Todo pane. On completion, drop the prefix and mark `completed`.
-
-**8. Collect the wave.** Each foreground `task()` returns its result to you. For each group:
-- success: `git add` the group's `touches` paths and commit `"{ids}: {summary}"` in a single tool call (`git add <paths> && git commit -m "..."`); mark its Todo items `completed`; check `[x]` in `tasks.md`.
-- error / empty: revert that group's impact: `git checkout -- <tracked paths> && git clean -f -- <paths>` (one tool call). Mark `failed` and record the reason in `tasks.md`; `.opencode/harness-run.json` is owned by the monitor plugin. Then retry once with a shorter prompt. Still failing: leave failed and surface it; do not loop.
-- A failed group only blocks its dependents; unrelated tasks keep flowing.
-- After the wave's commits, run `node .opencode/scripts/check-diff.mjs` once on the whole diff. Findings in files a task of this wave touched reopen that task for the next wave, with the findings in its prompt; do not fix them in the lead. A budget overrun caught here costs one worker turn; caught at step 10 it costs a pass over every file.
-
-**9. Progress guard.** If a full wave moved zero tasks to DONE: STOP (do not re-spawn the identical failing set). Otherwise recompute `eligible` and loop to step 5.
-
-**10. Verify.** In this (lead) session, run the project's verification (`pnpm verify` when package.json defines it, otherwise its lint, typecheck, test and build), the proposal-required validation commands, then `node .opencode/scripts/check-diff.mjs`. Every command must exit 0. Anything changed to satisfy `check-diff` is a change: run the whole verification again afterwards, so the last run is on the tree you ship. Never delete a test that covers a branch the change added to fit the test budget; a complexity or coverage gate in CI measures it. A `check-diff` failure lists file, line and fix: reopen the tasks that own those files. On failure, reopen the offending tasks (uncheck, mark failed) so they re-enter `eligible` and run another wave. When every task is checked, no eligible task remains, and every command passes, report `VERIFIED` to the caller.
-
-**11. Close.** Mark all `tasks.md` checkboxes, run `openspec status --change "<name>" --json`, and report progress (N/M tasks). The wave state in `.opencode/harness-run.json` persists for resume.
-
-Resume: re-loading this skill after any crash recomputes DONE / FAILED / eligible from `tasks.md`, git, and `harness-run.json` and continues. State is on disk, not in this conversation.
+---
+name: pc-plan-apply
+description: Implement tasks from a plan. OpenSpec-annotated tasks (from pc-plan-propose) run as parallel subagent waves; Todo pane tasks (from /plan-quick) run sequentially in-session. Load when implementing a prepared plan. Invoked by the /plan-apply command (interactive) and the plan-goal pipeline (autonomous).
+license: MIT
+---
+
+# Plan Apply
+
+## Input
+
+The caller provides (all optional):
+- A mode (see below). Default: `interactive`.
+- A `start_from` hint: `branch` (default, full protocol from step 1) or `load-plan` (the caller already created the feature branch; skip step 1).
+
+## Modes
+
+- `interactive` (default): report progress to the user and surface failures for their decision.
+- `autonomous`: there is no user to return to between waves. Loop until every task is DONE, or until the progress guard or the retry limit trips, then report to the caller, whose failure policy governs. APPLY completes by handing control back to `/plan-goal`, which has four phases left to run: `N/N tasks` is this stage's boundary, not the pipeline's.
+
+## Plan source detection
+
+1. Check if an OpenSpec change exists: inspect `openspec/changes/` for an active change folder with a `tasks.md`.
+2. If found and tasks have `<!-- agent` annotations (written by `pc-plan-propose`): OpenSpec mode. Follow the protocol below. Annotated tasks run in subagent waves. They never become sequential lead work because the task count seems small, the lead prefers direct implementation, or a worker has not yet been inspected.
+3. If no OpenSpec change exists, but there are `pending` items in the Todo pane (from `/plan-quick`): Simple mode. Follow the [simple mode](simple-mode.md) reference.
+
+## OpenSpec mode: parallel subagent waves
+
+Load `@openspec-apply-change` for change selection, status, and closing. Its own implement step does not apply here: annotated tasks are implemented only by spawning the annotated tier worker, and the lead never implements. Take that step from the protocol below instead.
+
+Referring to it by number would break silently. `@openspec-apply-change` is installed by `openspec init --force` with no version pinned, so an inserted step upstream renumbers the one being replaced, and the sequential default would then run alongside these waves.
+
+**Implement via native subagent waves.**
+
+You are the lead. You orchestrate from this session only; you spawn workers with the native `task` tool. Workers are ephemeral (one batch, then they exit) and navigable (`ctrl+x` arrow down, left/right arrows). There is no board, no claiming, no merging, no external dashboard.
+
+Core rule: push, don't pull. A worker is born with its work: every `task()` spawn prompt contains the exact task IDs and text it must do. There is no claim step, so a worker can never sit idle waiting for an assignment.
+
+**1. Branch.** Create `feature/{change-slug}` if not already on one. (Skip this step when the caller passed `start_from: load-plan`.)
+
+**2. Load the plan and workers.** Parse `tasks.md`. Each task carries `<!-- agent, depends_on, touches -->` (from `pc-plan-propose`). Read `.opencode/harness-models.json` (written by `pc-subagent-tiers` and `node .opencode/scripts/sync-agents.mjs`) for the effective model of every tier and the generated agent files. If the manifest is missing, run `node .opencode/scripts/sync-agents.mjs` once; if it still fails, stop. The tier-suffixed name in an annotation (for example, `backend-engineer.build`) is the worker to spawn; its model is the manifest's, not `harness.json`'s. `harness.user.json` overrides `harness.json`, so never report a model from `harness.json` alone. Read `.opencode/harness.json` -> `agents.maxConcurrent` (the wave cap, 1 to 5, enforced by `pc-subagent-monitor`).
+
+When `.platform/contract.yml` declares `reuse` and the change's `proposal.md` has no `## What is reused` section, stop the APPLY stage and report it: the plan never checked what the template already ships. Otherwise every spawn prompt in step 7 carries that section.
+
+When the change comes from an issue that carries a mockup (a section reading `UX mockup: intent, not a spec`, or a `mockups` branch folder for it), every spawn prompt for UI work in step 7 carries its component table and this line: the mockup states UX intent only; build with the components the table names, `DESIGN.md` and the repository's conventions, and never copy its markup, styles or `data-mockup-section` and `data-component` attributes. A `new:<Name>` entry is a component this change builds.
+
+Before hydrating the Todo board, resolve every task's annotated worker. If any task has a blank agent annotation, its base template is missing, its tier variant is unavailable, or the manifest has no effective model for its tier, stop the APPLY stage and report the task ID, expected worker, and missing file. Do not replace the worker with `fullstack-engineer`, `general`, or the lead session.
+
+**3. Hydrate the Todo board.** `todowrite` one item per task: `pending`. The Todo pane is the visible subagent board (opencode plugins cannot draw a custom pane, so the native Todo widget is the live UI). While a task is in flight, its label must carry the worker: `<agent> · <model>`, with the model read from `.opencode/harness-models.json`, so the pane shows which agent on which model is doing what. The Todo list is a projection only: never read it for recovery; rebuild it from `tasks.md` and git and `.opencode/harness-run.json`.
+
+**4. Worker context.** Before each wave, derive file-disjointness from `touches:` globs and `git diff`.
+
+<!-- PC-OPTIMIZATION-CODEGRAPH-START -->
+<!-- PC-OPTIMIZATION-CODEGRAPH-END -->
+
+<!-- PC-OPTIMIZATION-MEMORY-START -->
+<!-- PC-OPTIMIZATION-MEMORY-END -->
+
+**5. The wave loop.** Repeat until no tasks remain:
+
+```
+eligible = unchecked tasks whose every depends_on is DONE (committed/checked)
+if eligible is empty but tasks remain  -> STALL: report blocked tasks + the failed
+                                           dependency causing it, then STOP.
+groups   = pack eligible tasks that share a file (touches and gathered context)
+            into ONE worker each, to run sequentially (the worker uses the task's `agent`)
+wave     = pick groups whose file-sets are pairwise DISJOINT, capped at maxConcurrentAgents
+            (opencode runs every task() you emit at once; a spawn past the cap
+             is denied, and a denied spawn is not a failed group: re-issue it)
+```
+
+**6. Context per group.** For each group, gather the task text, relevant plan decisions, and source context needed to implement it.
+
+**7. Spawn the wave: one assistant turn, multiple `task()` calls (they run in parallel).** For each group:
+- `subagent_type` = the task's `agent` exactly as written in `tasks.md` (e.g. `frontend-engineer.build`, `backend-engineer.fast`). It is the tier-suffixed `mode: subagent` worker created by `pc-subagent-tiers`. Worker resolution happened in step 2; a missing worker stops the stage before spawning. `fullstack-engineer`, `general`, and the lead session are not fallbacks for annotated implementation work.
+- `description` = `"<task-ids>: <short label>"` (e.g. `"2.1,2.2: RPC endpoints"`) so the subagent is legible in the left/right list and the monitor.
+- `prompt` must contain the exact task IDs and text plus the gathered context. The worker follows the Engineer workflow defined in `@pc-guardrails-generic`; do not restate it in the prompt. **Worker output discipline:** instruct each worker to return a compact summary: what it changed (file names, not contents), pass/fail status of any verification it ran, and any blockers. Workers must NOT return file contents or full diffs as their result — the lead can `git diff` if needed.
+- **Diff budget, in every prompt.** When `.opencode/scripts/check-diff.mjs` exists, the prompt says: comments stay under a tenth of the code added and only explain what the code cannot show; tests cover the public contract, about one test line per code line, and a bug fix gets one regression test; and before reporting, run `node .opencode/scripts/check-diff.mjs --paths <the group's touches, comma-separated>` and fix every finding. A worker that writes to the budget does not hand the lead a cleanup: Pliny-Bot #809's lead spent 13 of 65 minutes and fourteen `check-diff` runs trimming what its workers had written.
+- Flip each spawned task's Todo item to `in_progress` and prefix its label with `<agent>: ` (e.g. `frontend-engineer.build: 2.1 Consolidate logic`) so the running worker is visible in the Todo pane. On completion, drop the prefix and mark `completed`.
+
+**8. Collect the wave.** Each foreground `task()` returns its result to you. For each group:
+- success: `git add` the group's `touches` paths and commit `"{ids}: {summary}"` in a single tool call (`git add <paths> && git commit -m "..."`); mark its Todo items `completed`; check `[x]` in `tasks.md`.
+- error / empty: revert that group's impact: `git checkout -- <tracked paths> && git clean -f -- <paths>` (one tool call). Mark `failed` and record the reason in `tasks.md`; `.opencode/harness-run.json` is owned by the monitor plugin. Then retry once with a shorter prompt. Still failing: leave failed and surface it; do not loop.
+- A failed group only blocks its dependents; unrelated tasks keep flowing.
+- After the wave's commits, run `node .opencode/scripts/check-diff.mjs` once on the whole diff. Findings in files a task of this wave touched reopen that task for the next wave, with the findings in its prompt; do not fix them in the lead. A budget overrun caught here costs one worker turn; caught at step 10 it costs a pass over every file.
+
+**9. Progress guard.** If a full wave moved zero tasks to DONE: STOP (do not re-spawn the identical failing set). Otherwise recompute `eligible` and loop to step 5.
+
+**10. Verify.** In this (lead) session, run the project's verification (`pnpm verify` when package.json defines it, otherwise its lint, typecheck, test and build), the proposal-required validation commands, then `node .opencode/scripts/check-diff.mjs`. Every command must exit 0. Anything changed to satisfy `check-diff` is a change: run the whole verification again afterwards, so the last run is on the tree you ship. Never delete a test that covers a branch the change added to fit the test budget; a complexity or coverage gate in CI measures it. A `check-diff` failure lists file, line and fix: reopen the tasks that own those files. On failure, reopen the offending tasks (uncheck, mark failed) so they re-enter `eligible` and run another wave. When every task is checked, no eligible task remains, and every command passes, report `VERIFIED` to the caller.
+
+**11. Close.** Mark all `tasks.md` checkboxes, run `openspec status --change "<name>" --json`, and report progress (N/M tasks). The wave state in `.opencode/harness-run.json` persists for resume.
+
+Resume: re-loading this skill after any crash recomputes DONE / FAILED / eligible from `tasks.md`, git, and `harness-run.json` and continues. State is on disk, not in this conversation.

package/skills/pc-plan-apply/simple-mode.md

@@ -1,21 +1,21 @@
-# Simple mode: sequential in-session
-
-When the plan lives in the Todo pane (from `/plan-quick`) and no OpenSpec change exists:
-
-1. Read the task list from the Todo pane (the `pending` items created by `/plan-quick`).
-2. Create a feature branch if not already on one: `git switch -c feature/{slug}`. (Skip when the caller passed `start_from: load-plan`.)
-3. Work through tasks one at a time, in order, directly in this session:
-   - Read the task text from the Todo item.
-   - Mark it `in_progress` via `todowrite`.
-   - Implement it (edit files, run commands as needed).
-   - Mark it `completed` via `todowrite`.
-   - Commit the change: `git add <the paths this task wrote> && git commit -m "task {id}: {summary}"`. Unscoped staging is denied (`pc-system-reminders`).
-4. After all tasks are done, run the project's verification (`pnpm verify` when package.json defines it, otherwise its typecheck/build check), then `node .opencode/scripts/check-diff.mjs`. Fix any errors until both exit 0. Anything changed to satisfy `check-diff` is a change: run the whole verification again afterwards, so the last run is on the tree you ship. Never delete a test that covers a branch the change added to fit the test budget; a complexity or coverage gate in CI measures it.
-5. Report: tasks N/N completed, commits made, branch name.
-
-Rules:
-- Work in this session only. No subagent spawning.
-- No OpenSpec commands.
-- Keep each commit focused on one task.
-- Use `todowrite` to track progress: `pending` -> `in_progress` -> `completed`.
-- Never mark a task `completed` that you did not finish. Use `cancelled` with the reason and continue with the next; a false green is invisible to whoever reads the report.
+# Simple mode: sequential in-session
+
+When the plan lives in the Todo pane (from `/plan-quick`) and no OpenSpec change exists:
+
+1. Read the task list from the Todo pane (the `pending` items created by `/plan-quick`).
+2. Create a feature branch if not already on one: `git switch -c feature/{slug}`. (Skip when the caller passed `start_from: load-plan`.)
+3. Work through tasks one at a time, in order, directly in this session:
+   - Read the task text from the Todo item.
+   - Mark it `in_progress` via `todowrite`.
+   - Implement it (edit files, run commands as needed).
+   - Mark it `completed` via `todowrite`.
+   - Commit the change: `git add <the paths this task wrote> && git commit -m "task {id}: {summary}"`. Unscoped staging is denied (`pc-system-reminders`).
+4. After all tasks are done, run the project's verification (`pnpm verify` when package.json defines it, otherwise its typecheck/build check), then `node .opencode/scripts/check-diff.mjs`. Fix any errors until both exit 0. Anything changed to satisfy `check-diff` is a change: run the whole verification again afterwards, so the last run is on the tree you ship. Never delete a test that covers a branch the change added to fit the test budget; a complexity or coverage gate in CI measures it.
+5. Report: tasks N/N completed, commits made, branch name.
+
+Rules:
+- Work in this session only. No subagent spawning.
+- No OpenSpec commands.
+- Keep each commit focused on one task.
+- Use `todowrite` to track progress: `pending` -> `in_progress` -> `completed`.
+- Never mark a task `completed` that you did not finish. Use `cancelled` with the reason and continue with the next; a false green is invisible to whoever reads the report.

package/skills/pc-plan-archive/SKILL.md

@@ -1,66 +1,66 @@
----
-name: pc-plan-archive
-description: Archive a completed OpenSpec change and update documentation. Interactive mode finds the oldest merged unarchived change and opens an archive PR; autonomous mode archives a named change in place on the current branch. Invoked by the /plan-archive command (interactive) and the plan-goal pipeline (autonomous).
-license: MIT
----
-
-# Plan Archive
-
-<!-- PC-OPTIMIZATION-MEMORY-START -->
-<!-- PC-OPTIMIZATION-MEMORY-END -->
-
-## Input
-
-The caller provides (all optional):
-- A mode (see below). Default: `interactive`.
-- In autonomous mode: the change id to archive (required in that mode; the caller knows which change it just implemented).
-
-## Modes
-
-- interactive (default): full flow below. Find the oldest unarchived change with a completed PR, confirm with the user, archive it, update docs with approval, and open an archive PR. No input required.
-- autonomous: the caller names the change to archive. Skip the working-tree prep, the PR lookup, the confirmation prompt, and the archive-PR step. Instead, archive in place on the current branch:
-  1. Archive the change by its id. Prefer the `@openspec-archive-change` skill if it is available. If it is not available, run the CLI directly, and it must be non-interactive, because there is no user to answer prompts:
-
-     ```bash
-     openspec archive "<change-id>" -y
-     ```
-
-     `-y` skips the confirmation prompt (without it the command blocks forever in an unattended run). Add `--skip-specs` only for infra/tooling/doc-only changes that produced no spec deltas. If the command reports the change is already archived, treat that as success.
-  2. Verify the archive actually moved. The change folder must no longer exist at `openspec/changes/<change-id>/`, and a dated copy must now exist under `openspec/changes/archive/` (the CLI renames it to `archive/YYYY-MM-DD-<change-id>/`):
-
-     ```bash
-     REPO_ROOT="$(git rev-parse --show-toplevel)"
-     test ! -d "$REPO_ROOT/openspec/changes/<change-id>" \
-       && ls -d "$REPO_ROOT/openspec/changes/archive/"*"<change-id>" >/dev/null 2>&1 \
-       && echo ARCHIVED_OK || echo ARCHIVE_FAILED
-     ```
-
-      If this prints `ARCHIVE_FAILED`, run the archive once more and repeat the check. If it still fails, report it to the caller as a failure; do not pretend it succeeded.
-  3. Compare the archived change's specs against `ARCHITECTURE.md` and `DESIGN.md`; apply any needed doc updates directly (no approval prompt).
-  4. If the change was a bug fix or new functionality with important impact, check if `@pc-guardrails-project` exists and update it.
-  5. Do not commit or push: the caller owns the git operations.
-   6. The ARCHIVE stage is complete. Hand control back to the caller (the `/plan-goal` pipeline) so it continues with output. Do not stop or end the turn here; archiving is not the end of the run.
-
----
-
-## Interactive flow
-
-Steps
-
-1. Prepare working tree
-
-   ```bash
-   REPO_ROOT="$(git rev-parse --show-toplevel)"
-   DEFAULT_BRANCH="$(git symbolic-ref --short refs/remotes/origin/HEAD 2>/dev/null | sed 's|^origin/||')"
-   [ -z "$DEFAULT_BRANCH" ] && DEFAULT_BRANCH="main"
-   ```
-
-   1. If the tree has uncommitted changes: `git stash push -u -m "WIP before archive"` and tell the user their work is stashed (it is restored in step 6).
-   2. Sync the default branch (skip the pull if there is no `origin` remote):
-
-   ```bash
-   git switch "$DEFAULT_BRANCH" && git pull origin "$DEFAULT_BRANCH"
-   ```
-
-<!-- PC-PLATFORM-ARCHIVE-START -->
-<!-- PC-PLATFORM-ARCHIVE-END -->
+---
+name: pc-plan-archive
+description: Archive a completed OpenSpec change and update documentation. Interactive mode finds the oldest merged unarchived change and opens an archive PR; autonomous mode archives a named change in place on the current branch. Invoked by the /plan-archive command (interactive) and the plan-goal pipeline (autonomous).
+license: MIT
+---
+
+# Plan Archive
+
+<!-- PC-OPTIMIZATION-MEMORY-START -->
+<!-- PC-OPTIMIZATION-MEMORY-END -->
+
+## Input
+
+The caller provides (all optional):
+- A mode (see below). Default: `interactive`.
+- In autonomous mode: the change id to archive (required in that mode; the caller knows which change it just implemented).
+
+## Modes
+
+- interactive (default): full flow below. Find the oldest unarchived change with a completed PR, confirm with the user, archive it, update docs with approval, and open an archive PR. No input required.
+- autonomous: the caller names the change to archive. Skip the working-tree prep, the PR lookup, the confirmation prompt, and the archive-PR step. Instead, archive in place on the current branch:
+  1. Archive the change by its id. Prefer the `@openspec-archive-change` skill if it is available. If it is not available, run the CLI directly, and it must be non-interactive, because there is no user to answer prompts:
+
+     ```bash
+     openspec archive "<change-id>" -y
+     ```
+
+     `-y` skips the confirmation prompt (without it the command blocks forever in an unattended run). Add `--skip-specs` only for infra/tooling/doc-only changes that produced no spec deltas. If the command reports the change is already archived, treat that as success.
+  2. Verify the archive actually moved. The change folder must no longer exist at `openspec/changes/<change-id>/`, and a dated copy must now exist under `openspec/changes/archive/` (the CLI renames it to `archive/YYYY-MM-DD-<change-id>/`):
+
+     ```bash
+     REPO_ROOT="$(git rev-parse --show-toplevel)"
+     test ! -d "$REPO_ROOT/openspec/changes/<change-id>" \
+       && ls -d "$REPO_ROOT/openspec/changes/archive/"*"<change-id>" >/dev/null 2>&1 \
+       && echo ARCHIVED_OK || echo ARCHIVE_FAILED
+     ```
+
+      If this prints `ARCHIVE_FAILED`, run the archive once more and repeat the check. If it still fails, report it to the caller as a failure; do not pretend it succeeded.
+  3. Compare the archived change's specs against `ARCHITECTURE.md` and `DESIGN.md`; apply any needed doc updates directly (no approval prompt).
+  4. If the change was a bug fix or new functionality with important impact, check if `@pc-guardrails-project` exists and update it.
+  5. Do not commit or push: the caller owns the git operations.
+   6. The ARCHIVE stage is complete. Hand control back to the caller (the `/plan-goal` pipeline) so it continues with output. Do not stop or end the turn here; archiving is not the end of the run.
+
+---
+
+## Interactive flow
+
+Steps
+
+1. Prepare working tree
+
+   ```bash
+   REPO_ROOT="$(git rev-parse --show-toplevel)"
+   DEFAULT_BRANCH="$(git symbolic-ref --short refs/remotes/origin/HEAD 2>/dev/null | sed 's|^origin/||')"
+   [ -z "$DEFAULT_BRANCH" ] && DEFAULT_BRANCH="main"
+   ```
+
+   1. If the tree has uncommitted changes: `git stash push -u -m "WIP before archive"` and tell the user their work is stashed (it is restored in step 6).
+   2. Sync the default branch (skip the pull if there is no `origin` remote):
+
+   ```bash
+   git switch "$DEFAULT_BRANCH" && git pull origin "$DEFAULT_BRANCH"
+   ```
+
+<!-- PC-PLATFORM-ARCHIVE-START -->
+<!-- PC-PLATFORM-ARCHIVE-END -->

package/skills/pc-plan-explore/SKILL.md

@@ -1,21 +1,22 @@
----
-name: pc-plan-explore
-description: Explore an idea or requirement before planning. Invoked by the /plan-explore command.
-license: MIT
----
-
-Explore, then hand back what you learned. `@openspec-explore` supplies the stance; this skill adds one prohibition and one handoff.
-
-## Rules
-
-- Never write, edit, or create a file while this skill is loaded, OpenSpec artifacts included. This overrides `@openspec-explore`, which says creating them is "fine". Reading, searching, and discussing are the whole job.
-- If the conversation turns toward implementation, say explore mode is active and point at `/plan-apply`.
-
-Load `@openspec-explore` for the approach.
-
-## Autonomous handoff
-
-When a caller loads this skill in autonomous mode, return `EXPLORATION_BRIEF` in memory rather than writing a file. It holds: the problem in one or two sentences, the affected paths, the approach chosen, the risks worth knowing, and anything deliberately out of scope. `pc-plan-goal` requires it before its propose phase.
-
-<!-- PC-OPTIMIZATION-MEMORY-START -->
-<!-- PC-OPTIMIZATION-MEMORY-END -->
+---
+name: pc-plan-explore
+description: Explore an idea or requirement before planning. Invoked by the /plan-explore command.
+license: MIT
+---
+
+Explore, then hand back what you learned. `@openspec-explore` supplies the stance; this skill adds one prohibition and one handoff.
+
+## Rules
+
+- Never write, edit, or create a file while this skill is loaded, OpenSpec artifacts included. This overrides `@openspec-explore`, which says creating them is "fine". Reading, searching, and discussing are the whole job.
+- If the conversation turns toward implementation, say explore mode is active and point at `/plan-apply`.
+- When the idea changes what someone sees on screen, point at `/plan-mockup` once the direction is settled: a picture settles layout questions faster than prose.
+
+Load `@openspec-explore` for the approach.
+
+## Autonomous handoff
+
+When a caller loads this skill in autonomous mode, return `EXPLORATION_BRIEF` in memory rather than writing a file. It holds: the problem in one or two sentences, the affected paths, the approach chosen, the risks worth knowing, and anything deliberately out of scope. `pc-plan-goal` requires it before its propose phase.
+
+<!-- PC-OPTIMIZATION-MEMORY-START -->
+<!-- PC-OPTIMIZATION-MEMORY-END -->