@plainconceptsplatform/agent-harness 3.1.0 → 3.2.0

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-goal/branching.md

@@ -1,39 +1,39 @@
-# Branching procedure
-
-Resolve and record the branch names. If the invoking workflow already placed you on a feature branch (`feature/*`, `fix/*`, etc.), it owns the branch: do not stash, switch, pull, or rename. The sandbox hosting the workflow has no git credentials, so those commands would either corrupt the tree or hang, and the workflow has already cut the branch from the default branch. Treat its result as given.
-
-```bash
-BRANCH="$(git branch --show-current)"
-case "$BRANCH" in
-  feature/*|fix/*|chore/*|docs/*|refactor/*)
-    START_BRANCH="$BRANCH"
-    DEFAULT_BRANCH="$BRANCH"
-    GOAL_STASH="none"
-    ;;
-  *)
-    START_BRANCH="$BRANCH"
-    DEFAULT_BRANCH="$(git symbolic-ref --short refs/remotes/origin/HEAD 2>/dev/null | sed 's|^origin/||')"
-    [ -z "$DEFAULT_BRANCH" ] && DEFAULT_BRANCH="main"
-
-    # Stash uncommitted work when needed and record that the goal stash exists.
-    git stash push -u -m "goal-wip"
-    GOAL_STASH="goal-wip"
-
-    # Create the feature branch from the synchronized default branch.
-    git switch "$DEFAULT_BRANCH"
-
-    if git remote get-url origin >/dev/null 2>&1; then
-      git pull origin "$DEFAULT_BRANCH"
-    fi
-
-    git switch -c "feature/{slug}"
-    BRANCH="$(git branch --show-current)"
-    ;;
-esac
-```
-
-Record the branch name and that `feature/{slug}` was applied unconditionally, so downstream phases can restore if they move off it.
-
-Everything through archive happens on `$BRANCH`.
-
-When a later phase renames `$BRANCH` to match the canonical change slug (Phase 3 of `pc-plan-goal`), skip the rename if the workflow already fixed the name. Renaming would call `git branch -m`, which a credentialless sandbox refuses, and the workflow's `create_pull_request` is told to use the branch as named. Detect this by checking that `$BRANCH` already starts with `feature/`; if it does, keep it.
+# Branching procedure
+
+Resolve and record the branch names. If the invoking workflow already placed you on a feature branch (`feature/*`, `fix/*`, etc.), it owns the branch: do not stash, switch, pull, or rename. The sandbox hosting the workflow has no git credentials, so those commands would either corrupt the tree or hang, and the workflow has already cut the branch from the default branch. Treat its result as given.
+
+```bash
+BRANCH="$(git branch --show-current)"
+case "$BRANCH" in
+  feature/*|fix/*|chore/*|docs/*|refactor/*)
+    START_BRANCH="$BRANCH"
+    DEFAULT_BRANCH="$BRANCH"
+    GOAL_STASH="none"
+    ;;
+  *)
+    START_BRANCH="$BRANCH"
+    DEFAULT_BRANCH="$(git symbolic-ref --short refs/remotes/origin/HEAD 2>/dev/null | sed 's|^origin/||')"
+    [ -z "$DEFAULT_BRANCH" ] && DEFAULT_BRANCH="main"
+
+    # Stash uncommitted work when needed and record that the goal stash exists.
+    git stash push -u -m "goal-wip"
+    GOAL_STASH="goal-wip"
+
+    # Create the feature branch from the synchronized default branch.
+    git switch "$DEFAULT_BRANCH"
+
+    if git remote get-url origin >/dev/null 2>&1; then
+      git pull origin "$DEFAULT_BRANCH"
+    fi
+
+    git switch -c "feature/{slug}"
+    BRANCH="$(git branch --show-current)"
+    ;;
+esac
+```
+
+Record the branch name and that `feature/{slug}` was applied unconditionally, so downstream phases can restore if they move off it.
+
+Everything through archive happens on `$BRANCH`.
+
+When a later phase renames `$BRANCH` to match the canonical change slug (Phase 3 of `pc-plan-goal`), skip the rename if the workflow already fixed the name. Renaming would call `git branch -m`, which a credentialless sandbox refuses, and the workflow's `create_pull_request` is told to use the branch as named. Detect this by checking that `$BRANCH` already starts with `feature/`; if it does, keep it.

package/skills/pc-plan-goal/output.md

@@ -1,71 +1,71 @@
-# Output procedure
-
-Before output, require `verify`, `archive`, a clean working tree, no active change directory, and an archive directory for `{change-id}`.
-
-## Restore stash
-
-If the goal created `goal-wip`, restore it after the mode-specific operation. When restoration conflicts, leave the stash intact, report its `git stash list` reference, and do not drop user work.
-
-## Default mode
-
-Synchronize the default branch, merge, delete the feature branch, then restore the stash:
-
-```bash
-git switch "$DEFAULT_BRANCH"
-
-if git remote get-url origin >/dev/null 2>&1; then
-  git pull origin "$DEFAULT_BRANCH"
-fi
-
-git merge --no-ff "$BRANCH" -m "goal: {title} ({change-id})"
-git branch -d "$BRANCH"
-```
-
-If the merge conflicts, abort it and use the failure policy. Do not push the default branch.
-
-## Push mode
-
-Push the feature branch:
-
-```bash
-git push -u origin "$BRANCH"
-```
-
-Restore the stash and leave the branch available.
-
-## PR mode
-
-Push the feature branch, then load `pc-ops-ship` to create a PR into `$DEFAULT_BRANCH`. Supply title, change id, functional summary, delivered acceptance criteria, task count, verification result, archive path, and commits. Do not merge the PR.
-
-Restore the stash.
-
-## Branch mode
-
-Leave `$BRANCH` in place with its commits. Merge nothing, push nothing, delete nothing.
-
-Restore the stash.
-
-## Final report
-
-Print:
-
-```text
-Goal: {title}
-Change ID: {change-id}
-Scope classification: focused | standard | complex
-Functional outcome: {one-sentence result}
-Branch: {branch}
-Tasks: {completed}/{total}
-Acceptance criteria: {passed}/{total}
-Commits: {proposal, apply, archive}
-Verification: passed | failed
-Archived: yes | no
-Archive path: {path or none}
-Output mode: default | push | pr | branch
-Final state: merged locally | pushed branch | PR URL | branch preserved | branch preserved after failure
-Stash restoration: not needed | restored | preserved after conflict
-```
-
-## External gate
-
-An unattended caller must verify `openspec list --json` is empty and run the project's lint and typecheck commands before any later git operation.
+# Output procedure
+
+Before output, require `verify`, `archive`, a clean working tree, no active change directory, and an archive directory for `{change-id}`.
+
+## Restore stash
+
+If the goal created `goal-wip`, restore it after the mode-specific operation. When restoration conflicts, leave the stash intact, report its `git stash list` reference, and do not drop user work.
+
+## Default mode
+
+Synchronize the default branch, merge, delete the feature branch, then restore the stash:
+
+```bash
+git switch "$DEFAULT_BRANCH"
+
+if git remote get-url origin >/dev/null 2>&1; then
+  git pull origin "$DEFAULT_BRANCH"
+fi
+
+git merge --no-ff "$BRANCH" -m "goal: {title} ({change-id})"
+git branch -d "$BRANCH"
+```
+
+If the merge conflicts, abort it and use the failure policy. Do not push the default branch.
+
+## Push mode
+
+Push the feature branch:
+
+```bash
+git push -u origin "$BRANCH"
+```
+
+Restore the stash and leave the branch available.
+
+## PR mode
+
+Push the feature branch, then load `pc-ops-ship` to create a PR into `$DEFAULT_BRANCH`. Supply title, change id, functional summary, delivered acceptance criteria, task count, verification result, archive path, and commits. Do not merge the PR.
+
+Restore the stash.
+
+## Branch mode
+
+Leave `$BRANCH` in place with its commits. Merge nothing, push nothing, delete nothing.
+
+Restore the stash.
+
+## Final report
+
+Print:
+
+```text
+Goal: {title}
+Change ID: {change-id}
+Scope classification: focused | standard | complex
+Functional outcome: {one-sentence result}
+Branch: {branch}
+Tasks: {completed}/{total}
+Acceptance criteria: {passed}/{total}
+Commits: {proposal, apply, archive}
+Verification: passed | failed
+Archived: yes | no
+Archive path: {path or none}
+Output mode: default | push | pr | branch
+Final state: merged locally | pushed branch | PR URL | branch preserved | branch preserved after failure
+Stash restoration: not needed | restored | preserved after conflict
+```
+
+## External gate
+
+An unattended caller must verify `openspec list --json` is empty and run the project's lint and typecheck commands before any later git operation.

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

@@ -1,46 +1,46 @@
----
-name: pc-plan-quick
-description: "Quick plan: analyze the codebase and create a task checklist using the Todo pane. No files, no OpenSpec. Invoked by the /plan-quick command."
-license: MIT
----
-
-Lightweight planning for a change that is already clear: read the codebase, write the task list to the Todo pane, stop. Use `/plan-explore` then `/plan-propose` instead when the idea is half-formed, the alternatives need thinking through, or the result should outlive the session.
-
-## Rules
-
-- Never write, edit, or create a file. The only artefacts are Todo items and one question, so there is nothing to review afterwards and nothing to undo.
-- Never start the work, and never invoke `/plan-apply` or `/plan-propose` on the user's behalf. The question at the end is where they choose.
-
-## Contracts
-
-One Todo item per task, in dependency order, each one action naming the files it touches:
-
-```json
-{
-  "todos": [
-    { "content": "Add Project model to src/types.ts", "status": "pending", "priority": "high" },
-    { "content": "Add projectId field to LoopOptions in src/types.ts", "status": "pending", "priority": "high" },
-    { "content": "Create Project RPC endpoints in src/rpc/project/", "status": "pending", "priority": "medium" },
-    { "content": "Build Accept page UI in src/board/components/CreateForm.tsx", "status": "pending", "priority": "medium" },
-    { "content": "Run typecheck and fix errors", "status": "pending", "priority": "low" }
-  ]
-}
-```
-
-Then ask:
-
-```json
-{
-  "questions": [
-    {
-      "header": "What next",
-      "question": "What next?",
-      "options": [
-        { "label": "/plan-apply", "description": "Implement these tasks now (creates a feature branch and works through them)." },
-        { "label": "/plan-propose", "description": "Turn this into a full OpenSpec proposal with agent assignments." },
-        { "label": "Start on specific tasks", "description": "Tell me which tasks to start on." }
-      ]
-    }
-  ]
-}
-```
+---
+name: pc-plan-quick
+description: "Quick plan: analyze the codebase and create a task checklist using the Todo pane. No files, no OpenSpec. Invoked by the /plan-quick command."
+license: MIT
+---
+
+Lightweight planning for a change that is already clear: read the codebase, write the task list to the Todo pane, stop. Use `/plan-explore` then `/plan-propose` instead when the idea is half-formed, the alternatives need thinking through, or the result should outlive the session.
+
+## Rules
+
+- Never write, edit, or create a file. The only artefacts are Todo items and one question, so there is nothing to review afterwards and nothing to undo.
+- Never start the work, and never invoke `/plan-apply` or `/plan-propose` on the user's behalf. The question at the end is where they choose.
+
+## Contracts
+
+One Todo item per task, in dependency order, each one action naming the files it touches:
+
+```json
+{
+  "todos": [
+    { "content": "Add Project model to src/types.ts", "status": "pending", "priority": "high" },
+    { "content": "Add projectId field to LoopOptions in src/types.ts", "status": "pending", "priority": "high" },
+    { "content": "Create Project RPC endpoints in src/rpc/project/", "status": "pending", "priority": "medium" },
+    { "content": "Build Accept page UI in src/board/components/CreateForm.tsx", "status": "pending", "priority": "medium" },
+    { "content": "Run typecheck and check-diff, fix errors", "status": "pending", "priority": "low" }
+  ]
+}
+```
+
+Then ask:
+
+```json
+{
+  "questions": [
+    {
+      "header": "What next",
+      "question": "What next?",
+      "options": [
+        { "label": "/plan-apply", "description": "Implement these tasks now (creates a feature branch and works through them)." },
+        { "label": "/plan-propose", "description": "Turn this into a full OpenSpec proposal with agent assignments." },
+        { "label": "Start on specific tasks", "description": "Tell me which tasks to start on." }
+      ]
+    }
+  ]
+}
+```