openplanr 2.1.1 → 2.2.0

package/lib/host-packages/cursor/openplanr/rules/planr-sprint.mdc

@@ -0,0 +1,180 @@
+---
+description: "Refine every open backlog item against the code and the calendar, refute the picks, and select a sprint that fits capacity and the release cut. Use before a cut or sprint; not for decomposing one specification or reporting status."
+alwaysApply: false
+---
+
+# Planr Sprint
+
+Backlog refinement followed by sprint selection. **Refine** reads every open
+item in full and judges it against the default branch and the calendar.
+**Select** fits the surviving items to the stated capacity and the next release
+cut, refutes the picks with three independent lenses, and writes the sprint.
+Perform the reasoning in this session; never delegate it to a model subprocess.
+The CLI (`planr sprint …`) stores what this skill decides. It is optional: when
+it is unavailable, write the same files by hand in the shapes given in
+[sprint formats](references/sprint-formats.md).
+
+Use `planr-plan` to decompose one specification, `planr-status` to report
+without judging, and `planr-operate` for an executive decision queue. This skill
+never implements work and never chains into `planr-ship`.
+
+`--refine-only` runs the refine phase (steps 1 to 4 for the blocked and
+close-or-demote buckets) and writes the refinement note without creating a
+sprint. Any run can be repeated and diffed against the previous one.
+
+## Inputs are tiers, not gates
+
+Every input except the backlog is optional. A missing tier removes one
+capability; it never blocks the run. Name every degraded input in `Issues`.
+
+| Input | If present | If absent |
+| --- | --- | --- |
+| Open backlog and quick tasks (`.planr/backlog/`, `.planr/quick/`, open spec tasks) | The core: read, score, bucket | The only hard requirement; zero items means "nothing to refine" |
+| Git history and the code paths items cite | Evidence lens: stale, already fixed, premise false | Buckets rest on the items' own dates; say "not verified against code" |
+| Release profile (`.release/profile.md`: cut date, cadence, freezes) | Size the In-progress bucket to the cut; the sprint gets `releaseCut` | Ask once for a horizon; default to a two-week sprint from today |
+| Capacity (engineers × working days) | Fit the list and name the overflow | Ask once; default 1 engineer × 10 days, stated in the return |
+| Previous sprint or refinement note (`.planr/sprints/SPRINT-NNN/refinement.json`) | Carry `leftovers`; `planr sprint diff` is possible | First run, no diff |
+| Last Operate cycle | Rank its unfinished actions alongside | Skipped silently |
+| Linear or GitHub connector | Push statuses on approval, read PR state | Local files only; report the external step as not run |
+
+## Step 0: Frame the run
+
+Before reading the backlog, ask through the host's structured question surface
+(Claude Code `AskUserQuestion`, the Codex equivalent), never through free text
+when a structured surface exists.
+
+- One call, at most three questions, each with mutually exclusive options and
+  a recommended default; the user can always answer "Other".
+- Ask only what the repository cannot answer: capacity and horizon when no
+  profile and no argument supplies them; a focus (one product or area, or
+  everything); what to do with items judged dead (close, demote, or list only);
+  refine only, or refine and select.
+- Never ask about facts derivable from files (the cut date in the profile, the
+  last sprint, the open item count). Never ask mid-run.
+- With `--yes` or no structured surface, take the defaults and list the ones
+  taken in `Issues`.
+
+The only other question is the approval at the end (step 6).
+
+## Step 1: Read the calendar and capacity
+
+Next cut and freezes from `.release/profile.md`; capacity from the framing
+question or argument; `leftovers` from the previous sprint's `refinement.json`;
+unfinished actions from the last Operate cycle. Record the git revision the run
+judges against (`git rev-parse --short HEAD` on the default branch).
+
+## Step 2: Read every open item in full
+
+Backlog items, quick tasks and open spec tasks: the whole file, not the title.
+For each item record the fields in the
+[refinement contract](references/refinement-contract.md): what it claims, the
+latest dated evidence, the code path it names and whether that path still
+exists on the default branch as described, what blocks it (partner, team
+decision, another item, nothing), an effort class (`hours`, `day`, `days`,
+`week+`), and a score: production impact this month × tractability now.
+
+Read the code an item names before believing its claim. `git log -S`, `git
+log -- <path>` and the merged pull requests since the item's evidence date are
+the cheapest refutations.
+
+## Step 3: Rank into four buckets
+
+- **In progress now**: fits capacity to the cut, in execution order, grouped
+  into PR batches by product or into sessions. Each batch carries a title and
+  an effort in days.
+- **Plan next**: real, but after the cut.
+- **Blocked**: the named blocker and the one question that unblocks it.
+- **Close or demote**: with the evidence (`file:line`, PR number or date) and
+  the target status or priority in the repository's own vocabulary.
+
+Carry the previous Operate cycle's unfinished actions explicitly. Include the
+release cut itself as work; when it has no artifact yet, file it with
+`planr quick create "Release cut <date>"` so the sprint contains only artifact
+ids.
+
+## Step 4: Refute the In-progress bucket
+
+Before the bucket is shown, run three independent lenses over every pick:
+
+1. **Evidence**: still real on the default branch; premise not false; not
+   already fixed.
+2. **Capacity and sequencing**: fits the days; migrations, partner
+   dependencies, PR batching and CI cost per PR are accounted for.
+3. **User impact**: who is hit this month if it is not done, and which
+   higher-impact item was omitted for it.
+
+A pick that fails moves or drops, and the reason is kept in `refuted[]` with its
+lens. The list must fit the stated capacity; when it does not, say what was cut.
+
+## Step 5: Write the sprint, the note and the JSON, then stop
+
+Write the three durable outputs (formats in
+[sprint formats](references/sprint-formats.md)); the chat return is a view of
+them.
+
+```bash
+planr sprint create --data sprint.json --json                  # name, releaseCut, capacityDays, startDate
+planr sprint refinement SPRINT-NNN --data refinement.json --json # validates, stores the note and JSON, fills the sprint body
+planr sprint diff SPRINT-MMM SPRINT-NNN                          # when a previous run exists
+```
+
+`refinement.json` must satisfy [the schema](schemas/refinement.schema.json); the
+CLI rejects an inconsistent document with `$`-rooted diagnostics. Fix the
+document, never the validation. With `--refine-only`, skip `sprint create` and
+record the refinement against the current active sprint, or write only the note
+and JSON when none exists.
+
+Then stop. Ask the approval question through the structured surface: apply the
+write-back, or leave the proposal as written.
+
+## Step 6: On approval, apply
+
+```bash
+planr sprint apply SPRINT-NNN --dry-run          # show the status and priority changes
+planr sprint apply SPRINT-NNN --yes --commit     # one commit: chore(planr): refine backlog for SPRINT-NNN
+```
+
+Where a connector is configured, push each changed item afterwards
+(`planr linear push <id>`, `planr github push <id>`) and report the ones that
+were not pushed. When the CLI is unavailable, apply the same status changes with
+the repository's own vocabulary and commit them with the same message.
+
+Close a finished sprint with `planr sprint close SPRINT-NNN`; it records the
+leftovers the next run carries.
+
+## Rules from production use
+
+- Never move an item to In progress on its own priority label; a months-old P0
+  or P1 is often dead. Evidence date beats label.
+- Never accept an item's claim of impact without reading the code path it names.
+- Items blocked on a partner or a team decision are never In progress; they get
+  the question that unblocks them.
+- The list must fit the stated capacity; if it does not, say what was cut.
+- No new migration in a hand deploy unless the sprint says so explicitly.
+- Use the repository's own status vocabulary (`planr update --help` lists it);
+  never introduce a second one.
+- The note and the JSON are the durable output; the chat return is a view of
+  them. That is what keeps the third run from re-arguing the first two.
+
+## Return
+
+- **Outcome:** `proposed` (sprint written, nothing else changed) or `applied`
+  (status changes written on approval), plus capacity used vs available in
+  engineer-days.
+- **Sprint:** the sprint id and path, and the cut it targets.
+- **Buckets:** four lists, one line per row: `ID · title · effort · why`.
+  In-progress rows sit under their batch heading in execution order. Blocked
+  rows carry the blocker and the unblocking question. Close-or-demote rows carry
+  the evidence.
+- **Refuted:** every pick a refuter changed, with the lens and the change.
+- **Issues:** degraded inputs, items that could not be read or judged, defaults
+  taken, or `none`.
+
+`planr status` shows the active sprint with its cut and progress; the dashboard
+(`planr-dashboard`) renders the sprint from the same frontmatter and checkboxes.
+
+## Reference files
+
+- [Refinement contract](references/refinement-contract.md): item record, scoring, effort classes, buckets, refuter lenses, `refinement.json` fields
+- [Sprint formats](references/sprint-formats.md): sprint artifact, refinement note, chat return, hand-written fallback
+- [Refinement schema](schemas/refinement.schema.json): the JSON Schema the CLI validates against

package/lib/host-packages/openai/openplanr/.openplanr-content.json

@@ -3,7 +3,7 @@
   "schemaVersion": "1.0.0",
   "protocolVersion": "1.8.0",
   "host": "openai",
-  "skillCount": 26,
+  "skillCount": 27,
   "roleCount": 0,
   "files": [
     {
@@ -368,7 +368,7 @@
     },
     {
       "path": "skills/design-loop/scripts/runtime/packages/protocol/package.json",
-      "digest": "sha256:9a11f3b5e52bb2bd3f2310a9cbc1276b62b1b08e401279769228d5bfd8567995"
+      "digest": "sha256:d3a009b9b304680df08d3ec30bccea5b0baf7444fee4f65e90708125535d8773"
     },
     {
       "path": "skills/design-loop/scripts/runtime/packages/protocol/registry/artifact-theme.json",
@@ -540,7 +540,7 @@
     },
     {
       "path": "skills/design-review/scripts/runtime/packages/protocol/package.json",
-      "digest": "sha256:9a11f3b5e52bb2bd3f2310a9cbc1276b62b1b08e401279769228d5bfd8567995"
+      "digest": "sha256:d3a009b9b304680df08d3ec30bccea5b0baf7444fee4f65e90708125535d8773"
     },
     {
       "path": "skills/design-review/scripts/runtime/packages/protocol/registry/artifact-theme.json",
@@ -712,7 +712,7 @@
     },
     {
       "path": "skills/design/scripts/runtime/packages/protocol/package.json",
-      "digest": "sha256:9a11f3b5e52bb2bd3f2310a9cbc1276b62b1b08e401279769228d5bfd8567995"
+      "digest": "sha256:d3a009b9b304680df08d3ec30bccea5b0baf7444fee4f65e90708125535d8773"
     },
     {
       "path": "skills/design/scripts/runtime/packages/protocol/registry/artifact-theme.json",
@@ -860,7 +860,7 @@
     },
     {
       "path": "skills/openplanr/SKILL.md",
-      "digest": "sha256:0796e0cce4d8fdf6f5b8cca86ef7c96fd02150493b609d08e74bb78045fcb2dd"
+      "digest": "sha256:f1e2daabc532519e6e9b83e49bddae8948d234bdf1be0e858528c2d0ecf65bc5"
     },
     {
       "path": "skills/operate/agents/openai.yaml",
@@ -972,7 +972,7 @@
     },
     {
       "path": "skills/plan/scripts/runtime/packages/protocol/package.json",
-      "digest": "sha256:9a11f3b5e52bb2bd3f2310a9cbc1276b62b1b08e401279769228d5bfd8567995"
+      "digest": "sha256:d3a009b9b304680df08d3ec30bccea5b0baf7444fee4f65e90708125535d8773"
     },
     {
       "path": "skills/plan/scripts/runtime/packages/protocol/registry/artifact-theme.json",
@@ -1118,6 +1118,30 @@
       "path": "skills/spec/SKILL.md",
       "digest": "sha256:a046aed2e39c309173c47f66ca9d6182ca2a7dc0d34b1a7cc04e4fae67dfeb27"
     },
+    {
+      "path": "skills/sprint/agents/openai.yaml",
+      "digest": "sha256:37d78cf09ed49e07dc2246f17d3a4aab61979d073735e7c36efa52460ca94fe1"
+    },
+    {
+      "path": "skills/sprint/openplanr.skill.json",
+      "digest": "sha256:8083ebeb2c89a73d127b99fc299e6ee4d2891b56740c4e266b52450f55a01794"
+    },
+    {
+      "path": "skills/sprint/references/refinement-contract.md",
+      "digest": "sha256:0e2e621c0aa735b756187f28310f265be6a0330c790ecf71e27c527bad13cdcd"
+    },
+    {
+      "path": "skills/sprint/references/sprint-formats.md",
+      "digest": "sha256:fc9620515dd2cfa1ecf9319c949bc491c620de9450e33f4e2ce08483023333c2"
+    },
+    {
+      "path": "skills/sprint/schemas/refinement.schema.json",
+      "digest": "sha256:591bcd9bb94bbcbae0e3494f2e7f42a7ea953c90076254c1b290fa399901b690"
+    },
+    {
+      "path": "skills/sprint/SKILL.md",
+      "digest": "sha256:8ffa44b0f3ce532cada1841ad781294c5b6c9c84c87caa9e4c8aa9f259946c9f"
+    },
     {
       "path": "skills/status/agents/openai.yaml",
       "digest": "sha256:08055207da8033bdd60f2c7bec5b80b0da6905ba010251fbbe5590bb15e0f7d1"
@@ -1147,5 +1171,5 @@
       "digest": "sha256:53698324b62f43b672ce8fe1654c526c96fb202e313442f09c6fc1e72268677e"
     }
   ],
-  "contentDigest": "sha256:ebec93efd22f8e04e5f6dce3b933fedc54b51a69809ef85de2080c79349b0fb1"
+  "contentDigest": "sha256:313e4909a57b70aded41d61e44acd9cf625e2934885e06792f3dddcad82f0986"
 }

package/lib/host-packages/openai/openplanr/skills/design/scripts/runtime/packages/protocol/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@openplanr/protocol",
-  "version": "0.3.0",
+  "version": "0.4.0",
   "type": "module",
   "description": "Canonical OpenPlanr schemas, registries, typed errors, and portable contract validation",
   "license": "MIT",

package/lib/host-packages/openai/openplanr/skills/design-loop/scripts/runtime/packages/protocol/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@openplanr/protocol",
-  "version": "0.3.0",
+  "version": "0.4.0",
   "type": "module",
   "description": "Canonical OpenPlanr schemas, registries, typed errors, and portable contract validation",
   "license": "MIT",

package/lib/host-packages/openai/openplanr/skills/design-review/scripts/runtime/packages/protocol/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@openplanr/protocol",
-  "version": "0.3.0",
+  "version": "0.4.0",
   "type": "module",
   "description": "Canonical OpenPlanr schemas, registries, typed errors, and portable contract validation",
   "license": "MIT",

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

@@ -27,6 +27,7 @@ Claude Code and `$planr:plan` in Codex). Do not perform the routed work here.
 | Create or check an architecture, process, sequence, or data diagram | `planr-diagram` |
 | Share, import, or export an HTML artifact review | `planr-artifact` |
 | Know what is done, pending, blocked, or next | `planr-status` |
+| Refine the open backlog and select the sprint for the next release cut | `planr-sprint` |
 | See planning or Operate state in the browser | `planr-dashboard` |
 | Check artifacts for graph, status, or schema drift | `planr-sync` |
 | Judge release readiness or prepare a landing sequence | `planr-land` |

package/lib/host-packages/openai/openplanr/skills/plan/scripts/runtime/packages/protocol/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@openplanr/protocol",
-  "version": "0.3.0",
+  "version": "0.4.0",
   "type": "module",
   "description": "Canonical OpenPlanr schemas, registries, typed errors, and portable contract validation",
   "license": "MIT",

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

@@ -0,0 +1,181 @@
+---
+name: sprint
+description: Refine every open backlog item against the code and the calendar, refute the picks, and select a sprint that fits capacity and the release cut. Use before a cut or sprint; not for decomposing one specification or reporting status.
+license: MIT
+---
+
+# Planr Sprint
+
+Backlog refinement followed by sprint selection. **Refine** reads every open
+item in full and judges it against the default branch and the calendar.
+**Select** fits the surviving items to the stated capacity and the next release
+cut, refutes the picks with three independent lenses, and writes the sprint.
+Perform the reasoning in this session; never delegate it to a model subprocess.
+The CLI (`planr sprint …`) stores what this skill decides. It is optional: when
+it is unavailable, write the same files by hand in the shapes given in
+[sprint formats](references/sprint-formats.md).
+
+Use `planr-plan` to decompose one specification, `planr-status` to report
+without judging, and `planr-operate` for an executive decision queue. This skill
+never implements work and never chains into `planr-ship`.
+
+`--refine-only` runs the refine phase (steps 1 to 4 for the blocked and
+close-or-demote buckets) and writes the refinement note without creating a
+sprint. Any run can be repeated and diffed against the previous one.
+
+## Inputs are tiers, not gates
+
+Every input except the backlog is optional. A missing tier removes one
+capability; it never blocks the run. Name every degraded input in `Issues`.
+
+| Input | If present | If absent |
+| --- | --- | --- |
+| Open backlog and quick tasks (`.planr/backlog/`, `.planr/quick/`, open spec tasks) | The core: read, score, bucket | The only hard requirement; zero items means "nothing to refine" |
+| Git history and the code paths items cite | Evidence lens: stale, already fixed, premise false | Buckets rest on the items' own dates; say "not verified against code" |
+| Release profile (`.release/profile.md`: cut date, cadence, freezes) | Size the In-progress bucket to the cut; the sprint gets `releaseCut` | Ask once for a horizon; default to a two-week sprint from today |
+| Capacity (engineers × working days) | Fit the list and name the overflow | Ask once; default 1 engineer × 10 days, stated in the return |
+| Previous sprint or refinement note (`.planr/sprints/SPRINT-NNN/refinement.json`) | Carry `leftovers`; `planr sprint diff` is possible | First run, no diff |
+| Last Operate cycle | Rank its unfinished actions alongside | Skipped silently |
+| Linear or GitHub connector | Push statuses on approval, read PR state | Local files only; report the external step as not run |
+
+## Step 0: Frame the run
+
+Before reading the backlog, ask through the host's structured question surface
+(Claude Code `AskUserQuestion`, the Codex equivalent), never through free text
+when a structured surface exists.
+
+- One call, at most three questions, each with mutually exclusive options and
+  a recommended default; the user can always answer "Other".
+- Ask only what the repository cannot answer: capacity and horizon when no
+  profile and no argument supplies them; a focus (one product or area, or
+  everything); what to do with items judged dead (close, demote, or list only);
+  refine only, or refine and select.
+- Never ask about facts derivable from files (the cut date in the profile, the
+  last sprint, the open item count). Never ask mid-run.
+- With `--yes` or no structured surface, take the defaults and list the ones
+  taken in `Issues`.
+
+The only other question is the approval at the end (step 6).
+
+## Step 1: Read the calendar and capacity
+
+Next cut and freezes from `.release/profile.md`; capacity from the framing
+question or argument; `leftovers` from the previous sprint's `refinement.json`;
+unfinished actions from the last Operate cycle. Record the git revision the run
+judges against (`git rev-parse --short HEAD` on the default branch).
+
+## Step 2: Read every open item in full
+
+Backlog items, quick tasks and open spec tasks: the whole file, not the title.
+For each item record the fields in the
+[refinement contract](references/refinement-contract.md): what it claims, the
+latest dated evidence, the code path it names and whether that path still
+exists on the default branch as described, what blocks it (partner, team
+decision, another item, nothing), an effort class (`hours`, `day`, `days`,
+`week+`), and a score: production impact this month × tractability now.
+
+Read the code an item names before believing its claim. `git log -S`, `git
+log -- <path>` and the merged pull requests since the item's evidence date are
+the cheapest refutations.
+
+## Step 3: Rank into four buckets
+
+- **In progress now**: fits capacity to the cut, in execution order, grouped
+  into PR batches by product or into sessions. Each batch carries a title and
+  an effort in days.
+- **Plan next**: real, but after the cut.
+- **Blocked**: the named blocker and the one question that unblocks it.
+- **Close or demote**: with the evidence (`file:line`, PR number or date) and
+  the target status or priority in the repository's own vocabulary.
+
+Carry the previous Operate cycle's unfinished actions explicitly. Include the
+release cut itself as work; when it has no artifact yet, file it with
+`planr quick create "Release cut <date>"` so the sprint contains only artifact
+ids.
+
+## Step 4: Refute the In-progress bucket
+
+Before the bucket is shown, run three independent lenses over every pick:
+
+1. **Evidence**: still real on the default branch; premise not false; not
+   already fixed.
+2. **Capacity and sequencing**: fits the days; migrations, partner
+   dependencies, PR batching and CI cost per PR are accounted for.
+3. **User impact**: who is hit this month if it is not done, and which
+   higher-impact item was omitted for it.
+
+A pick that fails moves or drops, and the reason is kept in `refuted[]` with its
+lens. The list must fit the stated capacity; when it does not, say what was cut.
+
+## Step 5: Write the sprint, the note and the JSON, then stop
+
+Write the three durable outputs (formats in
+[sprint formats](references/sprint-formats.md)); the chat return is a view of
+them.
+
+```bash
+planr sprint create --data sprint.json --json                  # name, releaseCut, capacityDays, startDate
+planr sprint refinement SPRINT-NNN --data refinement.json --json # validates, stores the note and JSON, fills the sprint body
+planr sprint diff SPRINT-MMM SPRINT-NNN                          # when a previous run exists
+```
+
+`refinement.json` must satisfy [the schema](schemas/refinement.schema.json); the
+CLI rejects an inconsistent document with `$`-rooted diagnostics. Fix the
+document, never the validation. With `--refine-only`, skip `sprint create` and
+record the refinement against the current active sprint, or write only the note
+and JSON when none exists.
+
+Then stop. Ask the approval question through the structured surface: apply the
+write-back, or leave the proposal as written.
+
+## Step 6: On approval, apply
+
+```bash
+planr sprint apply SPRINT-NNN --dry-run          # show the status and priority changes
+planr sprint apply SPRINT-NNN --yes --commit     # one commit: chore(planr): refine backlog for SPRINT-NNN
+```
+
+Where a connector is configured, push each changed item afterwards
+(`planr linear push <id>`, `planr github push <id>`) and report the ones that
+were not pushed. When the CLI is unavailable, apply the same status changes with
+the repository's own vocabulary and commit them with the same message.
+
+Close a finished sprint with `planr sprint close SPRINT-NNN`; it records the
+leftovers the next run carries.
+
+## Rules from production use
+
+- Never move an item to In progress on its own priority label; a months-old P0
+  or P1 is often dead. Evidence date beats label.
+- Never accept an item's claim of impact without reading the code path it names.
+- Items blocked on a partner or a team decision are never In progress; they get
+  the question that unblocks them.
+- The list must fit the stated capacity; if it does not, say what was cut.
+- No new migration in a hand deploy unless the sprint says so explicitly.
+- Use the repository's own status vocabulary (`planr update --help` lists it);
+  never introduce a second one.
+- The note and the JSON are the durable output; the chat return is a view of
+  them. That is what keeps the third run from re-arguing the first two.
+
+## Return
+
+- **Outcome:** `proposed` (sprint written, nothing else changed) or `applied`
+  (status changes written on approval), plus capacity used vs available in
+  engineer-days.
+- **Sprint:** the sprint id and path, and the cut it targets.
+- **Buckets:** four lists, one line per row: `ID · title · effort · why`.
+  In-progress rows sit under their batch heading in execution order. Blocked
+  rows carry the blocker and the unblocking question. Close-or-demote rows carry
+  the evidence.
+- **Refuted:** every pick a refuter changed, with the lens and the change.
+- **Issues:** degraded inputs, items that could not be read or judged, defaults
+  taken, or `none`.
+
+`planr status` shows the active sprint with its cut and progress; the dashboard
+(`planr-dashboard`) renders the sprint from the same frontmatter and checkboxes.
+
+## Reference files
+
+- [Refinement contract](references/refinement-contract.md): item record, scoring, effort classes, buckets, refuter lenses, `refinement.json` fields
+- [Sprint formats](references/sprint-formats.md): sprint artifact, refinement note, chat return, hand-written fallback
+- [Refinement schema](schemas/refinement.schema.json): the JSON Schema the CLI validates against

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

@@ -0,0 +1,6 @@
+interface:
+  display_name: "Planr Sprint"
+  short_description: "Refine every open backlog item against the code and the…"
+  default_prompt: "Use $planr:sprint to refine every open backlog item against the code and the calendar, refute the picks, and select a sprint that fits capacity and the release cut. Use before a cut or sprint; not for decomposing one specification or reporting status."
+policy:
+  allow_implicit_invocation: true

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

@@ -0,0 +1,59 @@
+{
+  "kind": "openplanr-skill-package",
+  "schemaVersion": "1.0.0",
+  "protocolVersion": "1.8.0",
+  "skillId": "planr-sprint",
+  "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
+    },
+    {
+      "path": "references/refinement-contract.md",
+      "kind": "reference",
+      "hosts": [
+        "claude-code",
+        "codex",
+        "chatgpt",
+        "cursor"
+      ],
+      "executable": false
+    },
+    {
+      "path": "references/sprint-formats.md",
+      "kind": "reference",
+      "hosts": [
+        "claude-code",
+        "codex",
+        "chatgpt",
+        "cursor"
+      ],
+      "executable": false
+    },
+    {
+      "path": "schemas/refinement.schema.json",
+      "kind": "schema",
+      "hosts": [
+        "claude-code",
+        "codex",
+        "chatgpt",
+        "cursor"
+      ],
+      "executable": false
+    }
+  ]
+}