initial commit

plugins/harness-engineering/.codex-plugin/plugin.json

@@ -0,0 +1,22 @@
+{
+  "name": "harness-engineering",
+  "version": "1.0.0",
+  "description": "Repo-local Harness Engineering slash commands for Codex.",
+  "interface": {
+    "displayName": "Harness Engineering",
+    "shortDescription": "Harness planning and review prompts for this repo",
+    "longDescription": "Optional local plugin that exposes Harness Engineering slash commands while the core workflow remains in repo-native AGENTS, skills, custom agents, and hooks.",
+    "developerName": "Local Repository",
+    "category": "Productivity",
+    "capabilities": [
+      "Interactive",
+      "Read",
+      "Write"
+    ],
+    "defaultPrompt": [
+      "Use Harness Engineering to plan a new phase for this repository.",
+      "Review my changes against the Harness docs and rules."
+    ],
+    "brandColor": "#2563EB"
+  }
+}

plugins/harness-engineering/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "Harness Engineering"
+  short_description: "Use Harness slash commands in this repository"
+  default_prompt: "Use Harness Engineering to plan a phase or review changes in this repository."

plugins/harness-engineering/commands/harness.md

@@ -0,0 +1,43 @@
+---
+description: Run the Harness Engineering planning workflow for this repository.
+---
+
+# /harness
+
+## Preflight
+
+- Read `/AGENTS.md`, `/docs/PRD.md`, `/docs/ARCHITECTURE.md`, `/docs/ADR.md`, and `/docs/UI_GUIDE.md` if they exist.
+- Confirm whether the user wants discussion only, a draft plan, or file generation under `phases/`.
+- Note whether the user explicitly asked for subagents; only then consider `phase_planner` or built-in explorers/workers.
+
+## Plan
+
+- State what will be created or updated before editing files.
+- If a plan already exists under `phases/`, say whether you are extending it or replacing part of it.
+- Keep each proposed step small, self-contained, and independently executable.
+
+## Commands
+
+- Invoke `$harness-workflow` and follow it.
+- When file generation is requested, create or update:
+  - `phases/index.json`
+  - `phases/{phase}/index.json`
+  - `phases/{phase}/stepN.md`
+- Use `python scripts/execute.py <phase>` as the runtime target when you need to reference execution.
+
+## Verification
+
+- Re-read the generated phase files for consistency.
+- Check that step numbering, phase names, and acceptance commands line up.
+- If the repo has a validator, prefer `python scripts/validate_workspace.py` as the default acceptance command unless the user specified a narrower command.
+
+## Summary
+
+## Result
+- **Action**: planned or generated Harness phase files
+- **Status**: success | partial | failed
+- **Details**: phase name, step count, and any blockers
+
+## Next Steps
+
+- Suggest the next natural command, usually `python scripts/execute.py <phase>` or a focused edit to one generated step.

plugins/harness-engineering/commands/review.md

@@ -0,0 +1,38 @@
+---
+description: Review local changes against Harness repository rules and docs.
+---
+
+# /review
+
+## Preflight
+
+- Read `/AGENTS.md`, `/docs/ARCHITECTURE.md`, `/docs/ADR.md`, and `/docs/UI_GUIDE.md` if they exist.
+- Identify the changed files or generated `phases/` artifacts that need review.
+- If the user wants a delegated review, use the read-only custom agent `harness_reviewer` only when they explicitly asked for subagents.
+
+## Plan
+
+- State what evidence will be checked: docs, changed files, generated phase files, and validation output if available.
+- Prioritize correctness, architecture drift, CRITICAL rule violations, and missing tests over style commentary.
+
+## Commands
+
+- Invoke `$harness-review`.
+- Use Codex built-in `/review` when the user specifically wants a code-review style pass over the working tree or git diff.
+- If validation is relevant, run `python scripts/validate_workspace.py` or explain why it was not run.
+
+## Verification
+
+- Confirm that every finding is tied to a file and an actual rule or behavioral risk.
+- If no findings remain, say so explicitly and mention residual risks or missing evidence.
+
+## Summary
+
+## Result
+- **Action**: reviewed Harness changes
+- **Status**: success | partial | failed
+- **Details**: findings, docs checked, and validation status
+
+## Next Steps
+
+- Suggest the smallest follow-up: fix the top finding, rerun validation, or execute a pending phase.