briefops 1.0.0

package/plugins/briefops-codex/skills/briefops-continue-worker/SKILL.md

@@ -0,0 +1,22 @@
+---
+name: briefops-continue-worker
+description: Use when continuing a persistent BriefOps worker in a fresh Codex thread with a handoff, resume prompt, or portable pack
+---
+
+# BriefOps Continue Worker
+
+The BriefOps plugin is a local CLI helper. It does not require network access, does not publish to a marketplace, and should not auto-approve memory or skill patches.
+
+Use `--export-policy shared-only` before copying context outside the local workspace.
+
+Use this workflow when the user wants a fresh Codex thread to continue prior work with the same worker identity, project constraints, memory, and risks.
+
+Prepare a resume prompt and optional portable pack:
+
+```bash
+briefops continue --worker <worker> --task "<next task>" --pack
+```
+
+If BriefOps reports pending memory proposals, surface the review command before continuing. Do not apply memory automatically.
+
+Use portable packs only as explicit local user artifacts. They may include private local memory and should be reviewed before sharing.

package/plugins/briefops-codex/skills/briefops-finish-task/SKILL.md

@@ -0,0 +1,22 @@
+---
+name: briefops-finish-task
+description: Use when finishing a Codex task to record the outcome, propose durable memory, and prepare the next thread without auto-approving memory
+---
+
+# BriefOps Finish Task
+
+The BriefOps plugin is a local CLI helper. It does not require network access, does not publish to a marketplace, and should not auto-approve memory or skill patches.
+
+Use `--export-policy shared-only` before copying context outside the local workspace.
+
+Use BriefOps at the end of meaningful work so future Codex threads do not spend tokens rediscovering the same decisions, risks, and lessons.
+
+Run a scoped finish command with the actual result and any durable candidates:
+
+```bash
+briefops finish --worker <worker> --task "<task>" --result "<result>" --lesson "<lesson>" --next-step "<next step>"
+```
+
+Only include lessons, decisions, incidents, open risks, and next steps that will help future work. Do not store secrets or personal data.
+
+If a memory proposal is created, ask the user to review it. Never run `briefops approve` without explicit user confirmation.

package/plugins/briefops-codex/skills/briefops-prime-context/SKILL.md

@@ -0,0 +1,24 @@
+---
+name: briefops-prime-context
+description: Use when starting work in any Codex project or fresh thread to load the smallest useful BriefOps context before reading large history files
+---
+
+# BriefOps Prime Context
+
+The BriefOps plugin is a local CLI helper. It does not require network access, does not publish to a marketplace, and should not auto-approve memory or skill patches.
+
+Use `--export-policy shared-only` before copying context outside the local workspace.
+
+Use BriefOps before broad repo/history inspection when a `.briefops` workspace exists or may exist.
+
+Run:
+
+```bash
+briefops prime --format codex --task "<current user task>" --max-tokens 800
+```
+
+If the command reports that no workspace exists, keep the response short and suggest `briefops init`.
+
+Never apply memory automatically. If pending proposals exist, show the review command.
+
+Treat the prime output as a compact routing brief, not as permission to skip relevant code inspection.

package/plugins/briefops-codex/skills/briefops-review-memory/SKILL.md

@@ -0,0 +1,27 @@
+---
+name: briefops-review-memory
+description: Use when BriefOps reports pending memory proposals or skill patches that need human review before becoming durable local memory
+---
+
+# BriefOps Review Memory
+
+The BriefOps plugin is a local CLI helper. It does not require network access, does not publish to a marketplace, and should not auto-approve memory or skill patches.
+
+Use `--export-policy shared-only` before copying context outside the local workspace.
+
+BriefOps memory is human-approved. Pending proposals are local drafts until the user accepts or rejects them.
+
+Inspect proposals before applying:
+
+```bash
+briefops memory proposal-show latest
+briefops inbox
+```
+
+Apply only after explicit user confirmation:
+
+```bash
+briefops approve latest
+```
+
+Reject inaccurate, duplicate, sensitive, or overly broad proposals instead of carrying noisy context into future threads.