@plainconceptsplatform/agent-harness 2.0.0

package/src/content/AGENTS.md

@@ -0,0 +1,71 @@
+# AGENTS.md
+
+<!-- PC-NOT-INITIALIZED -->
+
+# Agent operating guide
+
+This guide defines the common operating contract for AI agents in this repository.
+It is agent-agnostic and works with OpenCode, Claude Code, Codex, Gemini, and other agents.
+
+## Purpose and scope
+
+Use this file for repository-wide workflow rules. Keep product architecture, security constraints, and design rules in their source documents rather than duplicating them here.
+
+## Session context
+
+Before a non-trivial change, read these documents in order:
+
+1. `AGENTS.md` for workflow and repository rules.
+2. `ARCHITECTURE.md` for boundaries, dependencies, and component interactions.
+3. `DESIGN.md` for UI and design-system work.
+4. The active OpenSpec change or the relevant specification for the area being changed.
+
+Read each document once per session unless it changes or the task moves into a different area.
+
+Command aliases: OpenSpec skills may reference `/opsx-propose`, `/opsx-apply`, `/opsx-archive`, or `/opsx-explore`. Always substitute them with the `pc-plan-propose`, `pc-plan-apply`, `pc-plan-archive`, and `pc-plan-explore` skills respectively. User-facing command names are `/plan-propose`, `/plan-apply`, `/plan-archive`, and `/plan-explore`. Never mention the `opsx-` names to the user.
+
+## Workflow ownership
+
+<!-- PC-PLATFORM-WORKFLOW-START -->
+<!-- PC-PLATFORM-WORKFLOW-END -->
+
+## Planning and execution
+
+- Plan before delegating work. Use OpenSpec when the change needs explicit scope, decisions, or sequenced tasks.
+- Keep changes focused. Do not combine unrelated refactors with requested work.
+- Do not guess when requirements, architecture, or security constraints are unclear. Ask before proceeding.
+- Prefer the project's established patterns and source documents over introducing new conventions.
+
+## Engineer selection
+
+Inspect `.opencode/agents/*.md` before spawning. Prefer the most specialized custom engineer. `fullstack-engineer` is `mode: primary`, the planning agent, and is not a spawned worker. If no specialist matches, tell the user to create one with `/make-engineer`. Spawn only engineers present in that directory.
+
+The `pc-plan-apply` skill is authoritative for subagent waves, dependency ordering, retries, and concurrency. Read `agents.maxConcurrent` from `.opencode/harness.json` before spawning workers.
+
+## Tool and repository safety
+
+- Never expose or commit secrets, credentials, tokens, or production data.
+- Read before editing. Respect repository ownership, generated files, and existing local changes.
+- Run only commands appropriate to the task. Do not bypass checks, weaken tests, or silence lint rules to get a green result.
+- Commit, push, create pull requests, alter dependencies, or change deployment configuration only with the user's explicit approval and the repository's stated process.
+
+## Verification and completion
+
+- Run the applicable tests, lint, typecheck, and build before reporting completion.
+- A bug fix needs a test that would have caught the defect when practical.
+- Update specifications, architecture, or design documentation when the change makes their current statements inaccurate.
+- Report changed files, checks run, and any remaining risk or follow-up work.
+
+## Communication
+
+- Keep updates concise and factual.
+- State blockers early and explain the decision needed.
+- Use the repository's language and writing conventions for source, documentation, issues, commits, and pull requests.
+- Comments explain non-obvious reasons, constraints, or invariants. Do not add comments that restate code.
+
+## Skills
+
+Skills live in `.agents/skills/`. Always installed: `@pc-guardrails-generic`, `@pc-guardrails-project`, and `@browser-automation`. The always-installed `pc-system-reminders` plugin loads each agent's `## Abilities` before work, guardrails first. Skills can require mandatory transitive loads. Keep `## Abilities` complete and do not treat entries as passive references.
+
+<!-- PC-PLATFORM-SKILLS-GUIDE-START -->
+<!-- PC-PLATFORM-SKILLS-GUIDE-END -->

package/src/content/ARCHITECTURE.md

@@ -0,0 +1,16 @@
+> NOT GENERATED YET
+>
+> This file has not been populated yet. It is intentionally empty.
+>
+> **If this is a greenfield project** (no codebase exists yet): skip this for now.
+> Come back and run `/make-architecture` once you have meaningful code, structure, or infrastructure in place.
+>
+> **If this is a brownfield project** (existing codebase): run this command now to generate the architecture documentation:
+>
+> ```
+> /make-architecture
+> ```
+>
+> This command analyzes your folder structure, config files, routes, data models, integrations, and build setup,
+> then writes a complete ARCHITECTURE.md covering components, data flow, tech stack, deployment, and more.
+> It is safe to rerun any time the architecture changes significantly.

package/src/content/DESIGN.md

@@ -0,0 +1,16 @@
+> NOT GENERATED YET
+>
+> This file has not been populated yet. It is intentionally empty.
+>
+> **If this is a greenfield project** (no UI exists yet): skip this for now.
+> Come back and run `/make-design` once you have a design system, UI components, or styles in place.
+>
+> **If this is a brownfield project** (existing UI/styles): run this command now to generate the design documentation:
+>
+> ```
+> /make-design
+> ```
+>
+> This command analyzes your CSS, Tailwind config, component files, and design tokens,
+> then writes a complete DESIGN.md with structured YAML tokens and written design intent.
+> It is safe to rerun any time your design system changes.

package/src/content/opencode.jsonc

@@ -0,0 +1,31 @@
+{
+  "$schema": "https://opencode.ai/config.json",
+  "instructions": [
+    "AGENTS.md"
+  ],
+  "plugin": [
+    "@different-ai/opencode-browser@4.6.1",
+    "@mohak34/opencode-notifier@0.2.8"
+  ],
+  "experimental": {
+    "mcp_timeout": 300000
+  },
+  "compaction": {
+    "auto": true,
+    "prune": true,
+    "reserved": 10000
+  },
+  "permission": {
+    "question": "allow",
+    "todowrite": "allow",
+    "skill": "allow"
+  },
+  "skills": {
+    "paths": [".agents/skills"]
+  },
+  "default_agent": "fullstack-engineer",
+  "agent": {
+    "build": { "disable": true },
+    "plan": { "disable": true }
+  }
+}

package/src/content/openspec/config.yaml

@@ -0,0 +1,20 @@
+schema: spec-driven
+
+# Project context (optional)
+# This is shown to AI when creating artifacts.
+# Add your tech stack, conventions, style guides, domain knowledge, etc.
+# Example:
+#   context: |
+#     Tech stack: TypeScript, React, Node.js
+#     We use conventional commits
+#     Domain: e-commerce platform
+
+# Per-artifact rules (optional)
+# Add custom rules for specific artifacts.
+# Example:
+#   rules:
+#     proposal:
+#       - Keep proposals under 500 words
+#       - Always include a "Non-goals" section
+#     tasks:
+#       - Break tasks into chunks of max 2 hours

package/src/content/skills-lock.json

@@ -0,0 +1,17 @@
+{
+  "version": 1,
+  "skills": {
+    "find-skills": {
+      "source": "vercel-labs/skills",
+      "sourceType": "github",
+      "skillPath": "skills/find-skills/SKILL.md",
+      "computedHash": "781bd6d3f9b19f8c9af6b53d8d0e4876d0183841b565db34ca7092ffa412d111"
+    },
+    "user-story": {
+      "source": "deanpeters/product-manager-skills",
+      "sourceType": "github",
+      "skillPath": "skills/user-story/SKILL.md",
+      "computedHash": "user-story-placeholder"
+    }
+  }
+}

package/src/fragments/archive/az.md

@@ -0,0 +1,95 @@
+2. **Find the oldest change with a completed PR**
+
+   List unarchived changes (top-level only, excludes `archive/`):
+
+   ```bash
+   find "$REPO_ROOT/openspec/changes" -mindepth 1 -maxdepth 1 -type d -not -name 'archive' | sort
+   ```
+
+   If empty, report a blocker and stop.
+
+   List completed PRs:
+
+   ```bash
+   az repos pr list --repository {repo} --status completed --query "sort_by(@, &closedDate)[].{name:title,sourceRefName:sourceRefName,closedDate:closedDate,pullRequestId:pullRequestId}"
+   ```
+
+   Match each change to a completed PR using its ID and slug as search hints:
+   - No match → skip (record as blocked: `no merged PR found`).
+   - One match → eligible.
+   - Multiple matches → ask the user which PR belongs to that change.
+
+   If nothing is eligible, report a blocker and stop. Otherwise select the eligible change with the **oldest** PR `closedDate` as the candidate.
+
+3. **Confirm the candidate**
+
+   Show the candidate (ID, title, PR ID, merged date) and any blocked changes, then ask:
+
+   ```text
+   Oldest unarchived merged change found:
+     ID: {change-id}
+     Title: {title from resolved PR}
+     PR ID: {pullRequestId}
+     Merged: {closedDate}
+
+   Proceed with archiving? [yes/no]
+   ```
+
+   Stop if the user does not confirm.
+
+4. **Archive the change**
+
+   ```bash
+   git checkout -b archive/{change-id}
+   ```
+
+   Load `@openspec-archive-change` skill and follow it to archive the change.
+
+5. **Update docs**
+
+   Compare the archived change's specs against `ARCHITECTURE.md` and `DESIGN.md`. If updates are needed, show them and get user approval before applying.
+
+6. **Create the archive PR**
+
+   ```bash
+   git add -A
+   git commit -m "archive: {title} ({change-id})"
+   git push origin archive/{change-id}
+
+   az repos pr create \
+     --repository {repo} \
+     --source-branch refs/heads/archive/{change-id} \
+     --target-branch "refs/heads/$DEFAULT_BRANCH" \
+     --title "archive: {title} ({change-id})" \
+     --description "Archive SDD artifacts for {change-id} after merge of {sourceRefName}." \
+     --auto-complete
+   ```
+
+   If work was stashed in step 1, restore it after the PR is created unless the user opts out.
+
+7. **Report**
+
+   Display:
+
+   ```text
+   Archive complete
+
+     Change ID: {change-id}
+     Title: {title}
+     Original PR: {original-pr-link}
+     Archive PR: {archive-pr-link}
+
+     Documentation updates:
+     - ARCHITECTURE.md: {count} changes applied
+     - DESIGN.md: {count} changes applied
+   ```
+
+## Rules
+
+- All OpenSpec paths resolve from `git rev-parse --show-toplevel`. Never use `/openspec/...`.
+- Only process top-level directories in `$REPO_ROOT/openspec/changes/`; exclude `archive/`.
+- Use change ID and slug only as search hints; do not assume the source branch name.
+- The oldest eligible merged change is the only candidate: never ask the user which change to archive (but do ask which PR if multiple match one change).
+- Never proceed if the selected PR is not completed.
+- Never use browser tools or direct web requests for Azure DevOps. Use `az` CLI only.
+- Never invent or guess PR, branch, or merge metadata.

package/src/fragments/archive/gh.md

@@ -0,0 +1,94 @@
+2. **Find the oldest change with a completed PR**
+
+   List unarchived changes (top-level only, excludes `archive/`):
+
+   ```bash
+   find "$REPO_ROOT/openspec/changes" -mindepth 1 -maxdepth 1 -type d -not -name 'archive' | sort
+   ```
+
+   If empty, report a blocker and stop.
+
+   List completed PRs:
+
+   ```bash
+   gh pr list --repo {owner}/{repo} --state merged --json title,headRefName,mergedAt,number --jq 'sort_by(.mergedAt) | .[] | {name: .title, sourceRefName: .headRefName, mergedAt: .mergedAt, pullRequestId: .number}'
+   ```
+
+   Match each change to a completed PR using its ID and slug as search hints:
+   - No match → skip (record as blocked: `no merged PR found`).
+   - One match → eligible.
+   - Multiple matches → ask the user which PR belongs to that change.
+
+   If nothing is eligible, report a blocker and stop. Otherwise select the eligible change with the **oldest** PR `mergedAt` as the candidate.
+
+3. **Confirm the candidate**
+
+   Show the candidate (ID, title, PR ID, merged date) and any blocked changes, then ask:
+
+   ```text
+   Oldest unarchived merged change found:
+     ID: {change-id}
+     Title: {title from resolved PR}
+     PR ID: {pullRequestId}
+     Merged: {mergedAt}
+
+   Proceed with archiving? [yes/no]
+   ```
+
+   Stop if the user does not confirm.
+
+4. **Archive the change**
+
+   ```bash
+   git checkout -b archive/{change-id}
+   ```
+
+   Load `@openspec-archive-change` skill and follow it to archive the change.
+
+5. **Update docs**
+
+   Compare the archived change's specs against `ARCHITECTURE.md` and `DESIGN.md`. If updates are needed, show them and get user approval before applying.
+
+6. **Create the archive PR**
+
+   ```bash
+   git add -A
+   git commit -m "archive: {title} ({change-id})"
+   git push origin archive/{change-id}
+
+   gh pr create \
+      --repo {owner}/{repo} \
+      --base "$DEFAULT_BRANCH" \
+      --head archive/{change-id} \
+      --title "archive: {title} ({change-id})" \
+      --body "Archive SDD artifacts for {change-id} after merge."
+   ```
+
+   If work was stashed in step 1, restore it after the PR is created unless the user opts out.
+
+7. **Report**
+
+   Display:
+
+   ```text
+   Archive complete
+
+     Change ID: {change-id}
+     Title: {title}
+     Original PR: {original-pr-link}
+     Archive PR: {archive-pr-link}
+
+     Documentation updates:
+     - ARCHITECTURE.md: {count} changes applied
+     - DESIGN.md: {count} changes applied
+   ```
+
+## Rules
+
+- All OpenSpec paths resolve from `git rev-parse --show-toplevel`. Never use `/openspec/...`.
+- Only process top-level directories in `$REPO_ROOT/openspec/changes/`; exclude `archive/`.
+- Use change ID and slug only as search hints; do not assume the source branch name.
+- The oldest eligible merged change is the only candidate: never ask the user which change to archive (but do ask which PR if multiple match one change).
+- Never proceed if the selected PR is not completed.
+- Never use browser tools or direct web requests for GitHub. Use `gh` CLI only.
+- Never invent or guess PR, branch, or merge metadata.

package/src/fragments/archive/gl.md

@@ -0,0 +1,94 @@
+2. **Find the oldest change with a completed MR**
+
+   List unarchived changes (top-level only, excludes `archive/`):
+
+   ```bash
+   find "$REPO_ROOT/openspec/changes" -mindepth 1 -maxdepth 1 -type d -not -name 'archive' | sort
+   ```
+
+   If empty, report a blocker and stop.
+
+   List completed merge requests:
+
+   ```bash
+   glab mr list --repo {owner}/{repo} --merged --output json --jq 'sort_by(.merged_at) | .[] | {name: .title, sourceRefName: .source_branch, mergedAt: .merged_at, mergeRequestId: .iid}'
+   ```
+
+   Match each change to a completed MR using its ID and slug as search hints:
+   - No match → skip (record as blocked: `no merged MR found`).
+   - One match → eligible.
+   - Multiple matches → ask the user which MR belongs to that change.
+
+   If nothing is eligible, report a blocker and stop. Otherwise select the eligible change with the **oldest** MR `merged_at` as the candidate.
+
+3. **Confirm the candidate**
+
+   Show the candidate (ID, title, MR ID, merged date) and any blocked changes, then ask:
+
+   ```text
+   Oldest unarchived merged change found:
+     ID: {change-id}
+     Title: {title from resolved MR}
+     MR ID: {iid}
+     Merged: {merged_at}
+
+   Proceed with archiving? [yes/no]
+   ```
+
+   Stop if the user does not confirm.
+
+4. **Archive the change**
+
+   ```bash
+   git checkout -b archive/{change-id}
+   ```
+
+   Load `@openspec-archive-change` skill and follow it to archive the change.
+
+5. **Update docs**
+
+   Compare the archived change's specs against `ARCHITECTURE.md` and `DESIGN.md`. If updates are needed, show them and get user approval before applying.
+
+6. **Create the archive MR**
+
+   ```bash
+   git add -A
+   git commit -m "archive: {title} ({change-id})"
+   git push origin archive/{change-id}
+
+   glab mr create \
+      --repo {owner}/{repo} \
+      --source-branch "archive/{change-id}" \
+      --target-branch "$DEFAULT_BRANCH" \
+      --title "archive: {title} ({change-id})" \
+      --description "Archive SDD artifacts for {change-id} after merge."
+   ```
+
+   If work was stashed in step 1, restore it after the MR is created unless the user opts out.
+
+7. **Report**
+
+   Display:
+
+   ```text
+   Archive complete
+
+     Change ID: {change-id}
+     Title: {title}
+     Original MR: {original-mr-link}
+     Archive MR: {archive-mr-link}
+
+     Documentation updates:
+     - ARCHITECTURE.md: {count} changes applied
+     - DESIGN.md: {count} changes applied
+   ```
+
+## Rules
+
+- All OpenSpec paths resolve from `git rev-parse --show-toplevel`. Never use `/openspec/...`.
+- Only process top-level directories in `$REPO_ROOT/openspec/changes/`; exclude `archive/`.
+- Use change ID and slug only as search hints; do not assume the source branch name.
+- The oldest eligible merged change is the only candidate: never ask the user which change to archive (but do ask which MR if multiple match one change).
+- Never proceed if the selected MR is not completed.
+- Never use browser tools or direct web requests for GitLab. Use `glab` CLI only.
+- Never invent or guess MR, branch, or merge metadata.

package/src/fragments/archive/none.md

@@ -0,0 +1,73 @@
+2. **Find the oldest unarchived change**
+
+   List unarchived changes (top-level only, excludes `archive/`):
+
+   ```bash
+   find "$REPO_ROOT/openspec/changes" -mindepth 1 -maxdepth 1 -type d -not -name 'archive' | sort
+   ```
+
+   If empty, report a blocker and stop. Otherwise select the **oldest** change (by directory creation/sort order) as the candidate.
+
+   This mode has no platform PR integration, so completion is judged from local state only. Do not look up remote PRs or work items.
+
+3. **Confirm the candidate**
+
+   Show the candidate (ID, title) and any other unarchived changes, then ask:
+
+   ```text
+   Oldest unarchived change found:
+     ID: {change-id}
+     Title: {title from proposal.md}
+
+   Proceed with archiving? [yes/no]
+   ```
+
+   Stop if the user does not confirm.
+
+4. **Archive the change**
+
+   ```bash
+   git checkout -b archive/{change-id}
+   ```
+
+   Load `@openspec-archive-change` skill and follow it to archive the change.
+
+5. **Update docs**
+
+   Compare the archived change's specs against `ARCHITECTURE.md` and `DESIGN.md`. If updates are needed, show them and get user approval before applying.
+
+6. **Commit the archive**
+
+   ```bash
+   git add -A
+   git commit -m "archive: {title} ({change-id})"
+   ```
+
+   No PR is created in this mode. Leave the `archive/{change-id}` branch for the user to merge or push manually if they choose.
+
+   If work was stashed in step 1, restore it after the commit unless the user opts out.
+
+7. **Report**
+
+   Display:
+
+   ```text
+   Archive complete
+
+     Change ID: {change-id}
+     Title: {title}
+     Archive branch: archive/{change-id}
+
+     Documentation updates:
+     - ARCHITECTURE.md: {count} changes applied
+     - DESIGN.md: {count} changes applied
+   ```
+
+## Rules
+
+- All OpenSpec paths resolve from `git rev-parse --show-toplevel`. Never use `/openspec/...`.
+- Only process top-level directories in `$REPO_ROOT/openspec/changes/`; exclude `archive/`.
+- Use change ID and slug only as search hints; do not assume the source branch name.
+- The oldest unarchived change is the only candidate: never ask the user which change to archive.
+- This mode has no GitHub or Azure DevOps integration. Never call `gh` or `az`, and never use browser tools or direct web requests for PR/work-item lookups.
+- Never invent or guess PR, branch, or merge metadata.

package/src/fragments/guardrails/codegraph.md

@@ -0,0 +1,7 @@
+## CodeGraph
+
+- **Use `codegraph_explore` INSTEAD OF grep, glob, or read.** It is always available. Do not assume it might be missing.
+  - One call returns the relevant symbols' verbatim, line-numbered source plus the call paths between them, use it as a full replacement for Read, Grep, and file-reading sub-tasks when working with indexed code.
+  - If you instinctively reach for grep or read to find or understand code, STOP: call `codegraph_explore` instead with the symbol name, file path, or a natural-language question. It covers the same ground in one call instead of a dozen.
+- **Fall back to grep/glob/read ONLY when `codegraph_explore` returns no results** or the query is for something codegraph does not index (config files, plain-text docs, `.env` patterns, raw string searches). When you do fall back, you MUST state that codegraph returned nothing.
+- Do NOT run `codegraph` in bash: it is an MCP server, not a CLI tool.

package/src/fragments/guardrails/humanizer.md

@@ -0,0 +1,4 @@
+## Humanizer (optimization skill — MANDATORY LOAD)
+
+- **You MUST call `skill("humanizer")` via the skill tool before writing any prose** (commit messages, PR descriptions, docs, proposals) to remove AI writing patterns and sound more natural.
+- Do NOT apply humanizer to code, config files, or terminal output: only to prose.

package/src/fragments/guardrails/memory.md

@@ -0,0 +1,4 @@
+## Agentmemory
+
+- Use agentmemory MCP tools (`memory_smart_search`, `memory_save`, `memory_sessions`, `memory_governance_delete`) for cross-session context: `memory_smart_search` for prior decisions before implementing unfamiliar areas, `memory_save` for architecture decisions and cross-agent context.
+- Do NOT run `agentmemory` in bash: it is an MCP server. Start the server with `agentmemory` in a separate terminal, then use MCP tools.

package/src/fragments/guardrails/rtk.md

@@ -0,0 +1,3 @@
+## RTK
+
+- Prefix ALL CLI commands with `rtk` (e.g. `rtk git diff`, `rtk pnpm test`). Read-only commands like `cat`, `ls`, `Get-Content` are exempt.

package/src/fragments/guardrails/simple-english.md

@@ -0,0 +1,4 @@
+## Simple English (optimization skill - MANDATORY LOAD)
+
+- **You MUST call `skill("simple-english")` via the skill tool before responding.** This is not optional. Apply Simplified Technical English to all prose responses.
+- Keep code blocks, identifiers, CLI commands, file paths, quoted errors, and product names exact.

package/src/fragments/ops-backlog/az.md

@@ -0,0 +1,29 @@
+**Browser MCP tools are FORBIDDEN for all Azure DevOps operations.**
+
+---
+
+### Step 1: Parse input
+
+`$ARGUMENTS` is the work item title/description. If it contains a title and body separated by a newline or `---`, split them. Otherwise use the full text as the title with an empty body.
+
+### Step 2: Create work item
+
+```bash
+az boards work-item create \
+  --title "{title}" \
+  --description "{body}" \
+  --type "User Story"
+```
+
+### Step 3: Report
+
+```text
+Work item created
+  ID: {id}
+  Title: {title}
+  URL: {work-item-url}
+```
+
+Tell the user: "Use `/plan-propose {work-item-url}` to turn this into a plan."
+
+---

package/src/fragments/ops-backlog/gh.md

@@ -0,0 +1,30 @@
+**ALL GitHub data MUST come from `gh` CLI. NEVER use webfetch, HTTP requests, or browser MCP tools for GitHub operations, even if gh CLI fails. If `gh` is unavailable, report as a blocker.**
+Always pass `--repo {owner}/{repo}` explicitly, never rely on git context to resolve the repo.
+
+---
+
+### Step 1: Parse input
+
+`$ARGUMENTS` is the issue title/description. If it contains a title and body separated by a newline or `---`, split them. Otherwise use the full text as the title with an empty body.
+
+### Step 2: Create issue
+
+```bash
+gh issue create \
+  --repo {owner}/{repo} \
+  --title "{title}" \
+  --body "{body}"
+```
+
+### Step 3: Report
+
+```text
+Issue created
+  URL: {issue-url}
+  Number: #{number}
+  Title: {title}
+```
+
+Tell the user: "Use `/plan-propose {issue-url}` to turn this into a plan."
+
+---

package/src/fragments/ops-backlog/jira.md

@@ -0,0 +1,29 @@
+**NEVER use browser tools to navigate to atlassian.net: use `acli` CLI only.**
+
+---
+
+### Step 1: Parse input
+
+`$ARGUMENTS` is the issue title/description. If it contains a title and body separated by a newline or `---`, split them. Otherwise use the full text as the title with an empty body.
+
+### Step 2: Create issue
+
+```bash
+acli jira issue create \
+  --summary "{title}" \
+  --description "{body}" \
+  --type "Story"
+```
+
+### Step 3: Report
+
+```text
+Issue created
+  Key: {key}
+  Title: {title}
+  URL: {issue-url}
+```
+
+Tell the user: "Use `/plan-propose {issue-url}` to turn this into a plan."
+
+---