@plainconceptsplatform/agent-harness 2.0.0 → 2.0.1

package/src/content/.agents/skills/pc-userstory-gh/SKILL.md

@@ -1,120 +1,120 @@
----
-name: pc-userstory
-description: Parse GitHub Issue URL and create OpenSpec change. Use when user provides a GitHub Issue URL.
-license: MIT
-compatibility: Requires openspec CLI and gh CLI.
-metadata:
-  author: copilots
-  version: "1.1"
----
-
-Use `gh` CLI for all GitHub operations. If `gh` is unavailable, report it as a blocker.
-
-## GitHub CLI Setup (One-Time)
-
-```bash
-gh auth login
-# Follow prompts, authenticate via browser or token
-```
-
-Verify:
-```bash
-gh auth status
-```
-
-## Steps
-
-1. **Extract owner, repo, and issue number** from URL
-   - `https://github.com/{owner}/{repo}/issues/42` -> owner: `{owner}`, repo: `{repo}`, number: `42`
-
-2. **Fetch Issue**, always pass `--repo` explicitly:
-   ```bash
-   gh issue view 42 --repo {owner}/{repo} --json number,title,body,labels,milestone,state
-   ```
-   If this returns an auth error or 404, report as a blocker.
-
-3. **Extract Key Fields** from JSON response:
-   - `number` -> Issue number
-   - `title` -> Title
-   - `body` -> Description / acceptance criteria
-   - `labels` -> Labels
-   - `milestone` -> Milestone / sprint equivalent
-   - `state` -> State (open/closed)
-
-4. **Create OpenSpec Change**
-   ```bash
-   openspec new change "gh-{number}-{slug}"
-   ```
-
-5. **Hand off to proposal.** Load the `pc-plan-propose` skill (interactive mode) to generate the proposal, specs, and tasks. After it completes, call the `question` tool:
-
-   ```json
-   {
-     "questions": [
-       {
-         "header": "Ready to implement",
-         "question": "Ready to implement?",
-         "options": [
-           { "label": "yes", "description": "Load the pc-plan-apply skill to start implementation." },
-           { "label": "no", "description": "Stop here. You can run /plan-apply later." }
-         ]
-       }
-     ]
-   }
-   ```
-
-   Wait for confirmation before loading `pc-plan-apply`.
-
-## Full GitHub CLI Reference
-
-Always pass `--repo {owner}/{repo}`, relying on git context is unreliable.
-
-### Issues
-```bash
-# Read issue
-gh issue view <number> --repo {owner}/{repo}
-
-# List open issues
-gh issue list --repo {owner}/{repo} --state open --limit 10
-
-# Update issue
-gh issue edit <number> --repo {owner}/{repo} --add-label "in-progress"
-```
-
-## Screenshot / Image Strategy
-
-Save to openspec change folder and reference via GitHub blob URL pinned to commit SHA. Keep `?raw=true` when embedding in markdown:
-
-```
-openspec/changes/{change-name}/images/{screenshot}.png
-```
-
-```
-https://github.com/{owner}/{repo}/blob/{sha}/openspec/changes/{change}/images/{file}.png?raw=true
-```
-
-## URL Formats Reference
-
-```
-# Issue
-https://github.com/{owner}/{repo}/issues/{number}
-
-# PR
-https://github.com/{owner}/{repo}/pull/{number}
-
-# Blob file
-https://github.com/{owner}/{repo}/blob/{sha}/{path}
-```
-
-## Output Format
-
-```
-## Issue Parsed
-
-Issue: #{number}
-Title: {title}
-State: {state}
-Milestone: {milestone}
-
-Change Created: gh-{number}-{slug}
-```
+---
+name: pc-userstory
+description: Parse GitHub Issue URL and create OpenSpec change. Use when user provides a GitHub Issue URL.
+license: MIT
+compatibility: Requires openspec CLI and gh CLI.
+metadata:
+  author: copilots
+  version: "1.1"
+---
+
+Use `gh` CLI for all GitHub operations. If `gh` is unavailable, report it as a blocker.
+
+## GitHub CLI Setup (One-Time)
+
+```bash
+gh auth login
+# Follow prompts, authenticate via browser or token
+```
+
+Verify:
+```bash
+gh auth status
+```
+
+## Steps
+
+1. **Extract owner, repo, and issue number** from URL
+   - `https://github.com/{owner}/{repo}/issues/42` -> owner: `{owner}`, repo: `{repo}`, number: `42`
+
+2. **Fetch Issue**, always pass `--repo` explicitly:
+   ```bash
+   gh issue view 42 --repo {owner}/{repo} --json number,title,body,labels,milestone,state
+   ```
+   If this returns an auth error or 404, report as a blocker.
+
+3. **Extract Key Fields** from JSON response:
+   - `number` -> Issue number
+   - `title` -> Title
+   - `body` -> Description / acceptance criteria
+   - `labels` -> Labels
+   - `milestone` -> Milestone / sprint equivalent
+   - `state` -> State (open/closed)
+
+4. **Create OpenSpec Change**
+   ```bash
+   openspec new change "gh-{number}-{slug}"
+   ```
+
+5. **Hand off to proposal.** Load the `pc-plan-propose` skill (interactive mode) to generate the proposal, specs, and tasks. After it completes, call the `question` tool:
+
+   ```json
+   {
+     "questions": [
+       {
+         "header": "Ready to implement",
+         "question": "Ready to implement?",
+         "options": [
+           { "label": "yes", "description": "Load the pc-plan-apply skill to start implementation." },
+           { "label": "no", "description": "Stop here. You can run /plan-apply later." }
+         ]
+       }
+     ]
+   }
+   ```
+
+   Wait for confirmation before loading `pc-plan-apply`.
+
+## Full GitHub CLI Reference
+
+Always pass `--repo {owner}/{repo}`, relying on git context is unreliable.
+
+### Issues
+```bash
+# Read issue
+gh issue view <number> --repo {owner}/{repo}
+
+# List open issues
+gh issue list --repo {owner}/{repo} --state open --limit 10
+
+# Update issue
+gh issue edit <number> --repo {owner}/{repo} --add-label "in-progress"
+```
+
+## Screenshot / Image Strategy
+
+Save to openspec change folder and reference via GitHub blob URL pinned to commit SHA. Keep `?raw=true` when embedding in markdown:
+
+```
+openspec/changes/{change-name}/images/{screenshot}.png
+```
+
+```
+https://github.com/{owner}/{repo}/blob/{sha}/openspec/changes/{change}/images/{file}.png?raw=true
+```
+
+## URL Formats Reference
+
+```
+# Issue
+https://github.com/{owner}/{repo}/issues/{number}
+
+# PR
+https://github.com/{owner}/{repo}/pull/{number}
+
+# Blob file
+https://github.com/{owner}/{repo}/blob/{sha}/{path}
+```
+
+## Output Format
+
+```
+## Issue Parsed
+
+Issue: #{number}
+Title: {title}
+State: {state}
+Milestone: {milestone}
+
+Change Created: gh-{number}-{slug}
+```

package/src/content/.agents/skills/pc-userstory-jira/SKILL.md

@@ -1,131 +1,131 @@
----
-name: pc-userstory
-description: Parse a Jira work item and create an OpenSpec change. Use when the user provides a Jira URL or a bare issue key (e.g. PROJ-123).
-license: MIT
-compatibility: Requires openspec CLI and Atlassian CLI (acli).
-metadata:
-  author: copilots
-  version: "1.0"
----
-
-Use `acli` CLI for all Jira operations.
-
-## Atlassian CLI Setup (One-Time)
-
-Install from: https://developer.atlassian.com/cloud/acli/guides/install-acli/
-
-Authenticate:
-```bash
-# Option 1: API token (recommended for CI)
-echo <token> | acli jira auth login --site "<yoursite>.atlassian.net" --email "<email>" --token
-
-# Option 2: OAuth (interactive)
-acli jira auth login --web
-```
-
-Generate API token at: https://id.atlassian.com/manage-profile/security/api-tokens
-
-## Steps
-
-1. **Extract Issue Key** from URL
-   - `https://yoursite.atlassian.net/browse/PROJ-123` -> Key: PROJ-123
-   - `https://yoursite.atlassian.net/jira/core/projects/PROJ/issues/PROJ-123` -> Key: PROJ-123
-   - `https://yoursite.atlassian.net/browse/PROJ-123?filter=123` -> Key: PROJ-123
-   - If the user provides just `PROJ-123` without a URL, use it directly as the key.
-
-2. **Fetch Work Item**
-   ```bash
-   acli jira workitem view --key "PROJ-123"
-   ```
-
-   Parse the output for:
-   - Summary -> title
-   - Description -> proposal context
-   - Acceptance Criteria (if present in description or custom fields) -> spec requirements
-   - Labels -> tags for the OpenSpec change
-   - Status -> current state (e.g. To Do, In Progress, Done)
-   - Assignee -> who requested it
-   - Priority -> complexity hint
-
-3. **Offer to transition the Work Item to In Progress**
-
-   This writes to Jira, so ask first using the `question` tool:
-
-   ```json
-   {
-     "questions": [
-       {
-         "header": "Transition work item",
-         "question": "Move {KEY} to In Progress?",
-         "options": [
-           { "label": "yes", "description": "Transition the work item to In Progress." },
-           { "label": "no", "description": "Skip the transition." }
-         ]
-       }
-     ]
-   }
-   ```
-
-   Only if the user answers `yes` AND the status is currently "To Do" or "Backlog":
-   ```bash
-   acli jira workitem transition --key "PROJ-123" --status "In Progress"
-   ```
-   In unattended runs (`/plan-goal`), skip the question and the transition entirely.
-
-4. **Create OpenSpec Change**
-   ```bash
-   openspec new change "{slug-from-summary}"
-   ```
-
-   Write `proposal.md` with:
-   - Title: the Jira issue summary
-   - Context: mention this is Jira issue `{KEY}`, link back to the URL
-   - Requirements: extracted from description and acceptance criteria
-   - Scope: what's in/out based on the issue
-
-5. **Hand off to proposal.** Load the `pc-plan-propose` skill (interactive mode) to generate the proposal, specs, and tasks. After it completes, call the `question` tool:
-
-   ```json
-   {
-     "questions": [
-       {
-         "header": "Ready to implement",
-         "question": "Ready to implement?",
-         "options": [
-           { "label": "yes", "description": "Load the pc-plan-apply skill to start implementation." },
-           { "label": "no", "description": "Stop here. You can run /plan-apply later." }
-         ]
-       }
-     ]
-   }
-   ```
-
-   Wait for confirmation before loading `pc-plan-apply`.
-
-## Jira URL Patterns
-
-| URL format | Example |
-|------------|---------|
-| Browse URL | `https://yoursite.atlassian.net/browse/PROJ-123` |
-| Issue URL  | `https://yoursite.atlassian.net/jira/core/projects/PROJ/issues/PROJ-123` |
-| Board URL  | `https://yoursite.atlassian.net/jira/software/c/projects/PROJ/boards/1?selectedIssue=PROJ-123` |
-| Direct key | `PROJ-123` |
-
-## Useful Commands
-
-```bash
-# View work item
-acli jira workitem view --key "PROJ-123"
-
-# Transition work item
-acli jira workitem transition --key "PROJ-123" --status "In Progress"
-acli jira workitem transition --key "PROJ-123" --status "Done"
-
-# Search with JQL
-acli jira workitem search --jql "project = PROJ AND status = 'To Do' ORDER BY priority DESC"
-
-# Add a comment
-acli jira workitem comment create --key "PROJ-123" --body "Implementation started"
-```
-
-Jira is a backlog-only platform: it has no code repos or PRs. PR creation and code review use the repo platform (GitHub or Azure DevOps) configured separately.
+---
+name: pc-userstory
+description: Parse a Jira work item and create an OpenSpec change. Use when the user provides a Jira URL or a bare issue key (e.g. PROJ-123).
+license: MIT
+compatibility: Requires openspec CLI and Atlassian CLI (acli).
+metadata:
+  author: copilots
+  version: "1.0"
+---
+
+Use `acli` CLI for all Jira operations.
+
+## Atlassian CLI Setup (One-Time)
+
+Install from: https://developer.atlassian.com/cloud/acli/guides/install-acli/
+
+Authenticate:
+```bash
+# Option 1: API token (recommended for CI)
+echo <token> | acli jira auth login --site "<yoursite>.atlassian.net" --email "<email>" --token
+
+# Option 2: OAuth (interactive)
+acli jira auth login --web
+```
+
+Generate API token at: https://id.atlassian.com/manage-profile/security/api-tokens
+
+## Steps
+
+1. **Extract Issue Key** from URL
+   - `https://yoursite.atlassian.net/browse/PROJ-123` -> Key: PROJ-123
+   - `https://yoursite.atlassian.net/jira/core/projects/PROJ/issues/PROJ-123` -> Key: PROJ-123
+   - `https://yoursite.atlassian.net/browse/PROJ-123?filter=123` -> Key: PROJ-123
+   - If the user provides just `PROJ-123` without a URL, use it directly as the key.
+
+2. **Fetch Work Item**
+   ```bash
+   acli jira workitem view --key "PROJ-123"
+   ```
+
+   Parse the output for:
+   - Summary -> title
+   - Description -> proposal context
+   - Acceptance Criteria (if present in description or custom fields) -> spec requirements
+   - Labels -> tags for the OpenSpec change
+   - Status -> current state (e.g. To Do, In Progress, Done)
+   - Assignee -> who requested it
+   - Priority -> complexity hint
+
+3. **Offer to transition the Work Item to In Progress**
+
+   This writes to Jira, so ask first using the `question` tool:
+
+   ```json
+   {
+     "questions": [
+       {
+         "header": "Transition work item",
+         "question": "Move {KEY} to In Progress?",
+         "options": [
+           { "label": "yes", "description": "Transition the work item to In Progress." },
+           { "label": "no", "description": "Skip the transition." }
+         ]
+       }
+     ]
+   }
+   ```
+
+   Only if the user answers `yes` AND the status is currently "To Do" or "Backlog":
+   ```bash
+   acli jira workitem transition --key "PROJ-123" --status "In Progress"
+   ```
+   In unattended runs (`/plan-goal`), skip the question and the transition entirely.
+
+4. **Create OpenSpec Change**
+   ```bash
+   openspec new change "{slug-from-summary}"
+   ```
+
+   Write `proposal.md` with:
+   - Title: the Jira issue summary
+   - Context: mention this is Jira issue `{KEY}`, link back to the URL
+   - Requirements: extracted from description and acceptance criteria
+   - Scope: what's in/out based on the issue
+
+5. **Hand off to proposal.** Load the `pc-plan-propose` skill (interactive mode) to generate the proposal, specs, and tasks. After it completes, call the `question` tool:
+
+   ```json
+   {
+     "questions": [
+       {
+         "header": "Ready to implement",
+         "question": "Ready to implement?",
+         "options": [
+           { "label": "yes", "description": "Load the pc-plan-apply skill to start implementation." },
+           { "label": "no", "description": "Stop here. You can run /plan-apply later." }
+         ]
+       }
+     ]
+   }
+   ```
+
+   Wait for confirmation before loading `pc-plan-apply`.
+
+## Jira URL Patterns
+
+| URL format | Example |
+|------------|---------|
+| Browse URL | `https://yoursite.atlassian.net/browse/PROJ-123` |
+| Issue URL  | `https://yoursite.atlassian.net/jira/core/projects/PROJ/issues/PROJ-123` |
+| Board URL  | `https://yoursite.atlassian.net/jira/software/c/projects/PROJ/boards/1?selectedIssue=PROJ-123` |
+| Direct key | `PROJ-123` |
+
+## Useful Commands
+
+```bash
+# View work item
+acli jira workitem view --key "PROJ-123"
+
+# Transition work item
+acli jira workitem transition --key "PROJ-123" --status "In Progress"
+acli jira workitem transition --key "PROJ-123" --status "Done"
+
+# Search with JQL
+acli jira workitem search --jql "project = PROJ AND status = 'To Do' ORDER BY priority DESC"
+
+# Add a comment
+acli jira workitem comment create --key "PROJ-123" --body "Implementation started"
+```
+
+Jira is a backlog-only platform: it has no code repos or PRs. PR creation and code review use the repo platform (GitHub or Azure DevOps) configured separately.

package/src/content/.opencode/_gitignore

@@ -1,7 +1,7 @@
-node_modules
-harness-run.json
-harness.user.json
-harness-managed.json
-source-roots.json
-tmp/
-*-engineer.*.md
+node_modules
+harness-run.json
+harness.user.json
+harness-managed.json
+source-roots.json
+tmp/
+*-engineer.*.md

package/src/content/.opencode/commands/init.md

@@ -1,5 +1,5 @@
----
-description: Initialize the project. Presents a single form with all setup questions, then executes selected steps.
----
-
-Load the `pc-repo-initialize` skill and follow every step defined in it.
+---
+description: Initialize the project. Presents a single form with all setup questions, then executes selected steps.
+---
+
+Load the `pc-repo-initialize` skill and follow every step defined in it.

package/src/content/.opencode/commands/make-architecture.md

@@ -1,5 +1,5 @@
----
-description: Generate or update ARCHITECTURE.md by analyzing the codebase structure. Safe to run at any time.
----
-
-Load the `pc-make-architecture` skill and follow every step defined in it.
+---
+description: Generate or update ARCHITECTURE.md by analyzing the codebase structure. Safe to run at any time.
+---
+
+Load the `pc-make-architecture` skill and follow every step defined in it.

package/src/content/.opencode/commands/make-design.md

@@ -1,5 +1,5 @@
----
-description: Generate or update DESIGN.md by analyzing the codebase design system. Safe to run at any time.
----
-
-Load the `pc-make-design` skill and follow every step defined in it.
+---
+description: Generate or update DESIGN.md by analyzing the codebase design system. Safe to run at any time.
+---
+
+Load the `pc-make-design` skill and follow every step defined in it.

package/src/content/.opencode/commands/make-engineer.md

@@ -1,5 +1,5 @@
----
-description: Create a custom engineer agent via persona-driven interactive design
----
-
-Load the `pc-make-engineer` skill and follow every step defined in it.
+---
+description: Create a custom engineer agent via persona-driven interactive design
+---
+
+Load the `pc-make-engineer` skill and follow every step defined in it.

package/src/content/.opencode/commands/make-evidence-scaffold.md

@@ -1,5 +1,5 @@
----
-description: One-time scaffold of a project-specific visual-evidence harness (deterministic capture + assertions + manifest + publisher) that /ops-evidence and /plan-goal delegate to.
----
-
-Load the `pc-make-evidence-scaffold` skill and follow every step defined in it.
+---
+description: One-time scaffold of a project-specific visual-evidence harness (deterministic capture + assertions + manifest + publisher) that /ops-evidence and /plan-goal delegate to.
+---
+
+Load the `pc-make-evidence-scaffold` skill and follow every step defined in it.

package/src/content/.opencode/commands/make-guardrails.md

@@ -1,5 +1,5 @@
----
-description: Generate or update a pc-guardrails-project skill from ARCHITECTURE.md and relevant project files.
----
-
-Load the `pc-make-guardrails` skill and follow every step defined in it.
+---
+description: Generate or update a pc-guardrails-project skill from ARCHITECTURE.md and relevant project files.
+---
+
+Load the `pc-make-guardrails` skill and follow every step defined in it.

package/src/content/.opencode/commands/make-user-model.md

@@ -1,5 +1,5 @@
----
-description: Set the model for a tier (plan, build, or fast). Team-wide or user-local override.
----
-
-Load the `pc-make-user-model` skill and follow every step defined in it.
+---
+description: Set the model for a tier (plan, build, or fast). Team-wide or user-local override.
+---
+
+Load the `pc-make-user-model` skill and follow every step defined in it.

package/src/content/.opencode/commands/ops-backlog.md

@@ -1,10 +1,10 @@
----
-description: Create an issue in the backlog platform (GitHub, Azure DevOps, Jira) from a description.
----
-
-Backlog platform is set in `.opencode/harness.json` → `platform.backlog`. The platform-specific content below is injected by the CLI during onboarding.
-
-Input: `$ARGUMENTS` (the issue title/description)
-
-<!-- PC-PLATFORM-BACKLOG-START -->
-<!-- PC-PLATFORM-BACKLOG-END -->
+---
+description: Create an issue in the backlog platform (GitHub, Azure DevOps, Jira) from a description.
+---
+
+Backlog platform is set in `.opencode/harness.json` → `platform.backlog`. The platform-specific content below is injected by the CLI during onboarding.
+
+Input: `$ARGUMENTS` (the issue title/description)
+
+<!-- PC-PLATFORM-BACKLOG-START -->
+<!-- PC-PLATFORM-BACKLOG-END -->

package/src/content/.opencode/commands/ops-evidence.md

@@ -1,9 +1,9 @@
----
-description: Capture a screenshot (or text summary) of a completed change and post it as a comment on the originating issue or work item.
----
-
-Load the `pc-ops-evidence` skill and execute it.
-
-Input:
-
-$ARGUMENTS
+---
+description: Capture a screenshot (or text summary) of a completed change and post it as a comment on the originating issue or work item.
+---
+
+Load the `pc-ops-evidence` skill and execute it.
+
+Input:
+
+$ARGUMENTS

package/src/content/.opencode/commands/ops-review.md

@@ -1,8 +1,8 @@
----
-description: Read and triage PR review feedback. Reports what needs fixing, does not implement fixes.
----
-
-Repo platform is set in `.opencode/harness.json` → `platform.repo`. The platform-specific content below is injected by the CLI during onboarding.
-
-<!-- PC-PLATFORM-REVIEW-START -->
-<!-- PC-PLATFORM-REVIEW-END -->
+---
+description: Read and triage PR review feedback. Reports what needs fixing, does not implement fixes.
+---
+
+Repo platform is set in `.opencode/harness.json` → `platform.repo`. The platform-specific content below is injected by the CLI during onboarding.
+
+<!-- PC-PLATFORM-REVIEW-START -->
+<!-- PC-PLATFORM-REVIEW-END -->