openplanr 1.25.3 → 2.0.0

package/lib/host-packages/openai/openplanr/skills/land/SKILL.md

@@ -0,0 +1,33 @@
+---
+name: land
+description: Assess release readiness and prepare or inspect an OpenPlanr landing sequence. Use after implementation and checks are complete, before merge, publication, or deployment.
+license: MIT
+---
+
+# Planr Land
+
+Use this skill after implementation and relevant checks are complete, when the
+user wants to assess readiness or prepare a clear landing sequence.
+
+1. Read the current branch, worktree status, requested target, completed checks,
+   and release constraints already available in the repository or conversation.
+2. Inspect the installed CLI help, then use `planr land prepare`, `planr land
+   show`, or `planr land status` only when that command adds useful local state.
+3. Identify blockers, missing checks, ordering constraints, recovery options,
+   and the exact merge, publication, or deployment commands the user would run.
+4. If a real release choice is missing, use the host's native structured question
+   UI; otherwise continue with the safest explicit assumption and label it.
+5. Return this concise structure:
+
+- **Readiness:** ready, conditional, or blocked, with one-sentence reasoning.
+- **Blockers:** prioritized and actionable; write `none` when empty.
+- **Landing sequence:** ordered commands or actions, including preconditions.
+- **Recovery:** rollback or retry guidance for the first meaningful failure.
+- **Next action:** the single most useful step for the user.
+
+When the OpenPlanr dashboard is running, readiness context is browsable at its
+`#/overview` and `#/list` views. This is navigation only.
+
+This skill prepares and inspects the sequence; it does not perform merge,
+publication, or deployment effects. When a local command fails, report the
+failing command, what remains known, and the shortest practical repair.

package/lib/host-packages/openai/openplanr/skills/land/agents/openai.yaml

@@ -0,0 +1,6 @@
+interface:
+  display_name: "Planr Land"
+  short_description: "Assess release readiness and prepare or inspect an OpenPlanr…"
+  default_prompt: "Use $planr:land to assess release readiness and prepare or inspect an OpenPlanr landing sequence. Use after implementation and checks are complete, before merge, publication, or deployment."
+policy:
+  allow_implicit_invocation: true

package/lib/host-packages/openai/openplanr/skills/land/openplanr.skill.json

@@ -0,0 +1,26 @@
+{
+  "kind": "openplanr-skill-package",
+  "schemaVersion": "1.0.0",
+  "protocolVersion": "1.8.0",
+  "skillId": "planr-land",
+  "skillVersion": "1.0.0",
+  "entrypoint": "SKILL.md",
+  "hosts": [
+    "claude-code",
+    "codex",
+    "chatgpt",
+    "cursor"
+  ],
+  "execution": "host-agent",
+  "resources": [
+    {
+      "path": "agents/openai.yaml",
+      "kind": "agent-metadata",
+      "hosts": [
+        "codex",
+        "chatgpt"
+      ],
+      "executable": false
+    }
+  ]
+}

package/lib/host-packages/openai/openplanr/skills/operate/SKILL.md

@@ -0,0 +1,181 @@
+---
+name: operate
+description: "Run a focused operating review across seven executive lenses and produce a decision and action brief. Use for periodic product or company-level leadership review."
+license: MIT
+---
+
+# Operate
+
+Run one useful operating review, not a ceremony. Build shared context once, fan out the five
+executive advisors, use the Challenger to test material claims, and let the Chair synthesize the
+result. Return a clean board report with decisions, actions, risks, gaps, and any real issues.
+
+## Scope the review
+
+Infer these values from the request and repository when they are clear:
+
+- **Subject** — the product, area, change, or decision under review.
+- **Window** — a date or revision range, or the current snapshot when no comparison was requested.
+- **Requested decision** — the choice the review should inform, or `periodic review`.
+- **Roster** — all seven lenses unless the user selects fewer.
+
+Use the current repository, current snapshot, periodic review, and all seven lenses as sensible
+defaults. When ownership is useful, a recommendation may suggest a person, a role, or
+`unassigned`.
+
+Ask only when an unresolved choice would materially change the sources inspected or the decision
+being answered. Use the host's native structured-question UI when available, offering a
+recommended choice and short alternatives. Otherwise ask one concise chat question at a time.
+Never present the scope fields as a prose questionnaire.
+
+Preserve the user's wording in `cycle.md`, followed by the effective scope used by the lenses.
+Do not claim a trend from a current snapshot; describe current state and name any missing baseline.
+
+## Create the cycle workspace
+
+Use a short subject slug and today's ISO date. Choose the first unused path;
+when the base path exists, append `-02`, `-03`, and so on. Reuse an existing
+cycle only when the user explicitly asks to resume it and its recorded scope
+matches. Never overwrite a prior cycle implicitly.
+
+```text
+.planr/operate/<date>-<slug>/
+  cycle.md
+  brief.md
+  <selected-lens-notes>.md
+  board-report.md
+```
+
+`cycle.md` records the effective scope, roster, repository revision when relevant, and the outcome
+of each lens. If the directory is ignored by Git, continue locally and mention that in the report;
+do not ask the user to change ignore rules. Report an exact filesystem error only when the cycle
+workspace cannot be created or written.
+
+## Build shared context once
+
+Write `brief.md` as a compact orientation aid, not a conclusion. Include:
+
+- effective subject, window, requested decision, and roster;
+- current revision and working-tree state when relevant;
+- the requested range and a short change summary when the review is historical;
+- paths to relevant planning, product, customer, financial, operational, delivery, architecture,
+  incident, and metric sources;
+- important context that was searched for but not found.
+
+Open enough of the repository to make these pointers useful. Keep observations separate from
+interpretation so every lens can reach its own conclusion. The brief is a starting point; lenses
+may inspect other relevant project sources.
+
+## Run the selected lenses (seven by default)
+
+Dispatch only the selected independent advisors, in parallel when subagents are
+available:
+
+| Lens | Skill | Output |
+|---|---|---|
+| Strategy and finance | `planr-ceo-review` | `ceo.md` |
+| Technology and delivery risk | `planr-cto-review` | `cto.md` |
+| Product and activation | `planr-cpo-review` | `cpo.md` |
+| Growth and market | `planr-cmo-review` | `cmo.md` |
+| Operations and customer health | `planr-coo-review` | `coo.md` |
+
+Give each selected advisor the brief path, its output path, and the effective
+scope. Do not invoke or create note files for advisor lenses omitted by the
+roster. After the selected advisor work finishes:
+
+1. If Challenger is selected, run `planr-challenger-review` over the available
+   advisor notes to surface only material exceptions, alternatives, and downside.
+2. If Chair is selected, run `planr-chair-review` over the available selected
+   notes to produce the decision queue and action plan.
+3. If Challenger or Chair is omitted, record `omitted by scope` in review
+   coverage. Assemble the board report from the available selected notes without
+   inventing the omitted lens; when Chair is absent, clearly label the result as
+   an unsynthesized lens summary rather than a Chair recommendation.
+
+Missing or malformed lens output is an issue, not a reason to fabricate that lens or discard all
+other useful work. Record the problem, its effect on confidence, and the smallest next action.
+
+## Assemble `board-report.md`
+
+Use these sections in this order:
+
+```markdown
+# Operating board report — <subject>
+
+> **Contract:** operate-review-quality-contract@2.0.0
+
+## Scope
+- **Subject:** <effective subject>
+- **Window:** <effective window>
+- **Requested decision:** <decision or periodic review>
+- **Custody:** local-only | repository-trackable
+
+## Executive summary
+<overall signal and the two or three points that matter most>
+
+## Decision queue
+### D1 — [P0|P1|P2|unranked] <decision>
+- **Recommendation:** <clear choice>
+- **Why now:** <consequence or opportunity>
+- **Suggested owner:** <person, role, or unassigned>
+- **Confidence:** high | medium | low — <reason>
+- **Alternative:** <credible alternative and trade-off>
+- **First step:** <smallest concrete start>
+- **Expected result:** <observable result>
+- **Check:** <how to assess the result>
+- **Dependencies:** <IDs or none>
+- **Revisit when:** <observable condition>
+- **Sources:** <note IDs and direct project paths>
+- **Dissent:** <material exception or none>
+
+## Action plan
+| ID | Priority | Action | Suggested owner | First step | Success measure | Check | Depends on |
+|---|---|---|---|---|---|---|---|
+| A1 | P0 | ... | ... | ... | ... | ... | D1 |
+
+## Risks and dissent
+<only items that could change a decision or priority>
+
+## Decision-changing gaps
+<at most five; use `None.` when empty>
+
+## Review coverage
+| Lens | Outcome | Note | Informed |
+|---|---|---|---|
+| ... | reported / no material finding / unavailable / omitted by scope | `file.md` or `—` | D1 / watch / none |
+
+## Issues
+- **I1 — <problem>:** <impact and practical next action>
+<or `None.`>
+```
+
+When Chair is selected, copy decisions and actions from `chair.md`; do not create a new executive
+opinion during assembly. When Chair is omitted, summarize only the available selected notes,
+label the report as an unsynthesized lens summary, and use `No decision-ready proposal was
+established.` plus `No proposed actions.` unless those notes already state a directly supported
+proposal. Never present that result as Chair synthesis. Keep at most five decisions, seven actions,
+and five decision-changing gaps. When no decision is ready, say so plainly and retain the strongest
+watch items and the context needed to improve the next review.
+
+## Optional quality check
+
+The packaged [note validator](scripts/validate-note.mjs) can identify missing sections, fields, or limits:
+
+```sh
+node "<skill-root>/scripts/validate-note.mjs" "<absolute-advisor-output>" --profile advisor --contract-version 2.0.0
+node "<skill-root>/scripts/validate-note.mjs" "<absolute-challenger-output>" --profile challenger --contract-version 2.0.0
+node "<skill-root>/scripts/validate-note.mjs" "<absolute-chair-output>" --profile chair --contract-version 2.0.0
+node "<skill-root>/scripts/validate-note.mjs" "<absolute-board-report-path>" --profile board-report --contract-version 2.0.0
+```
+
+Use their diagnostics as editing help. Include unresolved structural problems under `Issues` with
+their impact and next action while preserving the useful parts of the report.
+
+Return the absolute `board-report.md` path, overall signal, decision count, action count, and a
+one-line issues summary.
+
+When the OpenPlanr dashboard is running, the operating cycle is browsable at
+`#/operate/cycles/<id>`, the completed review index at `#/operate/cycles`, and the latest
+completed review at `#/operate/today`. The standalone dashboard presents these local reports
+read-only and refreshes them automatically. Inbox, actions, evidence, outcomes, recovery, and
+all mutations require an actor-bound governed Operate session.

package/lib/host-packages/openai/openplanr/skills/operate/agents/openai.yaml

@@ -0,0 +1,6 @@
+interface:
+  display_name: "Planr Operate"
+  short_description: "Run a focused operating review across seven executive lenses and…"
+  default_prompt: "Use $planr:operate to run a focused operating review across seven executive lenses and produce a decision and action brief. Use for periodic product or company-level leadership review."
+policy:
+  allow_implicit_invocation: true

package/lib/host-packages/openai/openplanr/skills/operate/openplanr.skill.json

@@ -0,0 +1,70 @@
+{
+  "kind": "openplanr-skill-package",
+  "schemaVersion": "1.0.0",
+  "protocolVersion": "1.8.0",
+  "skillId": "planr-operate",
+  "skillVersion": "2.1.0",
+  "entrypoint": "SKILL.md",
+  "hosts": [
+    "claude-code",
+    "codex",
+    "chatgpt",
+    "cursor"
+  ],
+  "execution": "host-agent",
+  "resources": [
+    {
+      "path": "scripts/validate-note.mjs",
+      "kind": "script",
+      "hosts": [
+        "claude-code",
+        "codex",
+        "chatgpt",
+        "cursor"
+      ],
+      "executable": true
+    },
+    {
+      "path": "scripts/operate-review-note.mjs",
+      "kind": "script",
+      "hosts": [
+        "claude-code",
+        "codex",
+        "chatgpt",
+        "cursor"
+      ],
+      "executable": false
+    },
+    {
+      "path": "scripts/operate-review-contract.mjs",
+      "kind": "script",
+      "hosts": [
+        "claude-code",
+        "codex",
+        "chatgpt",
+        "cursor"
+      ],
+      "executable": false
+    },
+    {
+      "path": "scripts/errors.mjs",
+      "kind": "script",
+      "hosts": [
+        "claude-code",
+        "codex",
+        "chatgpt",
+        "cursor"
+      ],
+      "executable": false
+    },
+    {
+      "path": "agents/openai.yaml",
+      "kind": "agent-metadata",
+      "hosts": [
+        "codex",
+        "chatgpt"
+      ],
+      "executable": false
+    }
+  ]
+}

package/lib/host-packages/openai/openplanr/skills/operate/scripts/errors.mjs

@@ -0,0 +1,8 @@
+export class SkillRuntimeError extends Error {
+  constructor(code, message, details = {}) {
+    super(message);
+    this.name = 'SkillRuntimeError';
+    this.code = code;
+    this.details = details;
+  }
+}