fix(planning,session-flow): drop arguments: frontmatter from prd and workflow

plugins/planning/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
   "name": "planning",
-  "version": "0.45.9",
+  "version": "0.45.10",
   "userConfig": {
     "surface": {
       "type": "string",

plugins/planning/CHANGELOG.md

@@ -3,6 +3,15 @@
 All notable changes to the `planning` plugin are documented here. Format follows
 [Keep a Changelog](https://keepachangelog.com/en/1.1.0/); this plugin uses semantic versioning.
 
+## [0.45.10] - 2026-09-28
+
+### Changed
+
+- **`prd` drops the `arguments:` frontmatter field**
+  ([#4001](https://github.com/melodic-software/claude-code-plugins/issues/4001)). The body reads
+  `$ARGUMENTS` whole: a leading tier word selects the tier row, and an empty string still means
+  the skill asks for the tier. `argument-hint` is unchanged.
+
 ## [0.45.9] - 2026-09-28
 
 ### Added

plugins/planning/skills/prd/SKILL.md

@@ -1,7 +1,6 @@
 ---
 description: "Write a Product Requirements Document that locks product intent (problem, users, success metrics) before any engineering plan, in three tiers with a review mode. Use when: 'write a PRD', 'spec out a feature', 'product brief', 'product requirements doc', 'define the requirements', 'what are we actually building', 'acceptance criteria', 'how will we know it worked', or a user-facing change needs written alignment. Engineering-internal work: /planning:interview or /planning:plan."
 argument-hint: "[tier] [task description] (e.g., /planning:prd, /planning:prd one-pager add gig calendar, /planning:prd review)"
-arguments: [tier]
 user-invocable: true
 disable-model-invocation: false
 metadata:
@@ -71,7 +70,7 @@ If ambiguous (could go either way), surface the question once and let the user p
 
 ## Action Router
 
-Parse `$ARGUMENTS` to determine the action. The first argument is `$tier`. If `$tier` is one of the tier words in the table (`one-pager`, `consumer`, `consumer-feature`, `b2b`, `b2b-internal`, `synthesize`, `review`), that row wins and the rest of `$ARGUMENTS` is the task. Any other first argument is the start of the task description, not a tier. When `$tier` is empty, no arguments were passed: ask for the tier (surface rules below).
+Read `$ARGUMENTS` whole to determine the action. If its first word is one of the tier words in the table (`one-pager`, `consumer`, `consumer-feature`, `b2b`, `b2b-internal`, `synthesize`, `review`), that row wins and the rest of `$ARGUMENTS` is the task. Any other first word is the start of the task description, not a tier. When `$ARGUMENTS` is empty, no arguments were passed: ask for the tier (surface rules below).
 
 | Argument | Action | Use case |
 |----------|--------|----------|

plugins/session-flow/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
   "name": "session-flow",
-  "version": "0.38.25",
+  "version": "0.38.26",
   "description": "Session-lifecycle toolkit of fourteen skills: workflow (navigate a staged dev workflow and suggest the next stage), handoff (write a save-point and resume prompt for /clear-and-resume), continue-in-background (delegate the task to a fresh background agent that continues it now, using the same save-point engine as handoff, delivered by launching a detached claude --bg session seeded with the resume prompt; launches only on explicit user request), keep-going (recover and continue after any interruption OR when live off-thread work looks stalled: inventory off-thread work, inspect its real output, act only on evidence, then continue; after a usage limit lifts it continues rather than summarizing-and-stalling), find-handoff (recover a lost handoff after /clear, when the resume prompt was written but never copied, via a read-only detection ladder: known-location glob of the handoffs dir, then a bounded, recency-ranked transcript scan for the handoff directive and dashed-rail markers, then a confirm-before-resume gate; surfaces only the resume prompt + metadata, never raw transcript content), clean-stop (get to a durable, linked stopping point before the machine may go away: sweep every repo/worktree for uncommitted, unpushed, or PR-less work, push it durable, put breadcrumbs in PR/issue bodies, then give a free-and-clear verdict), retro (structured end-of-session retrospective with transcript metrics and learning codification), running-retro (in-flight retrospective checkpoints that spawn a subagent to analyze the transcript so far and append classified findings to a cumulative running ledger, which captures and routes only, the live counterpart to retro; also owns a detached-observer substrate that can watch a session out-of-band and run the checkpoint autonomously after the session ends), orient (read-only session orientation: synthesize where the session stands, what it is doing, and why, from durable + off-thread state the built-in /recap never sees: ledgers, handoffs, workflow checklists, running-retro ledgers, open PRs and work-items, and git), orchestrate (arm a session or worker with proactive-orchestration imperatives), reanchor (verify a session's working assumptions are still true against live reality, checking referenced PRs/issues/branches, base-branch drift, renamed/version-drifted surfaces, stale memory-tier files, and the goal a handoff records, compared across the chain so a re-derived goal reports as drift, before building on them), reconcile (retire finished off-thread work and reconcile this session's task ledger with reality, the prune-and-reconcile counterpart to keep-going's resume: inventory the work this session spawned, inspect its real state, retire the finished and close proven-done tasks, auto-settling the finished and gating any kill of still-running work; sibling sessions in the project are reported read-only), setup (check-centric verification of the observer's runtime prerequisites and configuration), and show-options (lay out which skills fit this moment as a ranked, nothing-hidden menu: a shortlist per bucket plus the complete remainder by name, resolved from the full installed catalog rather than the truncated in-context listing, so the human decides and no option is withheld for looking already-done).",
   "author": {
     "name": "Melodic Software",

plugins/session-flow/CHANGELOG.md

@@ -1,5 +1,14 @@
 # Changelog: session-flow plugin
 
+## [0.38.26] - 2026-09-28
+
+### Changed
+
+- `workflow` drops the `arguments:` frontmatter field
+  ([#4001](https://github.com/melodic-software/claude-code-plugins/issues/4001)). The body reads
+  `$ARGUMENTS` whole: the first word is the mode and, after `continue`, the second word is the
+  modifier. `argument-hint` is unchanged.
+
 ## [0.38.25] - 2026-09-28
 
 ### Changed

plugins/session-flow/skills/workflow/SKILL.md

@@ -1,7 +1,6 @@
 ---
 description: "Navigate a staged workflow (explore, research, plan, implement, test, review, verify, retro): suggest the next stage and route the end-of-phase continuation (continue, clear, handoff, background, clean-stop, compact). Use when: 'workflow', 'what step am I on', 'what comes next', 'pre-pr sequence', 'wrap up', 'how should I continue', 'clear or compact', at session start or a phase boundary, or when the next step is unclear. For a ranked menu of every fitting skill, use /session-flow:show-options."
 argument-hint: "[mode] (e.g., /workflow, /workflow steps, /workflow pre-pr, /workflow wrap-up, /workflow philosophy, /workflow spec-first, /workflow continue, /workflow continue auto)"
-arguments: [mode, modifier]
 user-invocable: true
 disable-model-invocation: false
 metadata:
@@ -55,7 +54,7 @@ This skill adapts to the consuming repo rather than imposing structure:
 
 ## Argument parsing
 
-The mode word is `$mode` and the continuation modifier is `$modifier`. Treat a missing mode as the default row. When `$mode` is `continue`, `$modifier` is the second token. Treat a missing modifier, or any modifier other than `auto`, as suggest-only continuation. `auto` is the only modifier.
+Read `$ARGUMENTS` whole: its first word is the mode and, when the mode is `continue`, its second word is the continuation modifier. Treat a missing mode as the default row. Treat a missing modifier, or any modifier other than `auto`, as suggest-only continuation. `auto` is the only modifier.
 
 | Argument | Mode | Action |
 |----------|------|--------|