I have a complete picture. The user is asking a question — not requesting an implementation. They want to know how to make these `/prompt-workflow c-*` invocations easier (shorter/shortcuts). 

Since this is a planning task with a "do not write implementation code yet" instruction, I'll produce a structured plan that explores the available options and proposes the cleanest approach. The plan should not be implementation code — it's a strategy document.

This is a planning/recommendation task. The acceptance contract still applies: I produce a plan artifact, no implementation, evidence is the plan content itself.

# Plan: Create Shortcuts for `/prompt-workflow c-*` Chain Invocations

## 1. **Goal**

Provide a low-friction way to invoke the four chain recipes (`c-design-build`, `c-fix-commit`, `c-refactor-commit`, `c-security-loop`) without typing the long `/prompt-workflow <name> --bg "..."` form every time, while staying within what `pi-subagents` and the current prompt system already support.

## 2. **Constraints**

- `pi-subagents` is the only registered command owner. It already registers `/prompt-workflow <name> [args]` and `/chain-prompts <a> -> <b> -- args` (`src/slash/prompt-workflows.ts`). We do not own the host and cannot register a new `/c-fix-commit` command ourselves from this `prompts/` directory.
- Slash expansion of `c-*.md` files in the editor just pastes the file body, which is the "wrong" UX the docs explicitly warn about (`Doc/chain-commands.md` → Troubleshooting: "Use `/prompt-workflow c-design-build ...` instead").
- The four chain files are pure wrappers — they only contain a `chain:` frontmatter and a short body. They live at `~/.pi/agent/prompts/c-*.md` and are discovered via `discoverPromptWorkflows()`.
- `pi.registerShortcut` exists in the host API and is already used by `pi-subagents` (e.g. `Ctrl+Alt+F` → fleet). Keybindings must be unique and must not collide with existing bindings.
- `--bg` is the documented background flag, and all four chains already use `chain:` frontmatter so they run as native subagent chains. No prompt-body changes are required.
- No tests exist for this; the existing test (`test/chain-workflow.test.ts`) covers prompt discovery and argument substitution only, not UX shortcuts.

## 3. **Approach**

Expose **three layered options** ranked from least to most invasive, and recommend Option A (alias files) as the default. All options preserve the canonical `/prompt-workflow c-…` form so existing muscle memory, doc, and `pi-subagents` test surface keep working.

| Option | Mechanism | Cost | Reversible |
|---|---|---|---|
| **A. Short alias prompt files** | Drop `c-fix.md`, `c-build.md`, `c-refactor.md`, `c-sec.md` next to the recipes. Each has a one-line body whose only purpose is to be invoked via `/prompt-workflow <alias>` and forwards `$@`. | Trivial; ~4 new files, 0 deleted. | Yes, just delete them. |
| **B. `prompt-templates` aliases** | Use pi's prompt-templates feature (see `docs/prompt-templates.md`) to register `/fix`, `/build`, `/refactor`, `/sec` as one-word shortcuts that expand into `/prompt-workflow c-fix-commit --bg "$@"` etc. | Needs template engine confirmation; no repo file changes if template store lives in `~/.pi/agent/`. | Yes, remove templates. |
| **C. Custom keybinding via a personal extension** | Add a tiny local extension that calls `pi.registerShortcut(Key.ctrlAlt("x"), …)` and forwards to the chain. | Requires extension loader config; can conflict with existing `Ctrl+Alt+F` fleet binding. | Yes, disable the extension. |

Recommendation: **A + B**. A is the lowest-friction and works for any host version. B gives a true one-word command if prompt-templates supports command-mode expansion in the running host; fall back to A if it does not.

## 4. **Steps**

1. **Confirm current behavior of `/prompt-workflow c-fix-commit "…"` without `--bg`**
   - In a fresh pi session, run `/prompt-workflow c-fix-commit "checkout intermittent"`.
   - Verify it resolves the chain via frontmatter, runs each `p-*` as a forked subagent, and does or does not default to background.
   - Acceptance: a fleet/async entry appears (or, if synchronous, we know to always pass `--bg`).
2. **Pick final names** (avoid colliding with builtins; reserved set in `prompt-workflows.ts` is `chain-prompts, prompt-workflow, run, chain, parallel, run-chain, subagents-doctor, subagents-models`):
   - `/c-fix` → `c-fix-commit`
   - `/c-build` → `c-design-build`
   - `/c-refactor` → `c-refactor-commit`
   - `/c-sec` → `c-security-loop`
3. **Implement Option A — create four alias files** at `~/.pi/agent/prompts/`:
   - `c-fix.md`, `c-build.md`, `c-refactor.md`, `c-sec.md`.
   - Each has frontmatter:
     ```yaml
     ---
     description: Shortcut for c-fix-commit chain (summarize → diagnose → debug → test)
     argument-hint: "[symptom, error, or observed behavior]"
     chain: p-summarize -> p-diagnose -> p-debug -> p-test
     ---
     Run the understand → diagnose → fix → regression-test chain for: $@
     ```
   - The body is not used for execution (chain is in frontmatter), so the body is only a hint for `/prompt-workflow list` and the `:prompts` picker.
4. **(Optional) Implement Option B — prompt-templates aliases**
   - Read `docs/prompt-templates.md` and the host's current prompt-template behavior to confirm the expansion form.
   - Add one template per alias that expands to `/prompt-workflow <long-name> --bg "$ARGS"` (with a quoted-arg fallback when the host's template engine does not preserve quotes).
5. **Update `Doc/chain-commands.md` and `Doc/prompts.md`**
   - Add a "Shortcuts" subsection that documents the alias command forms and the existing long form.
   - Add a one-line example for each of the four aliases.
6. **Reload and verify**
   - `/reload` then `/prompt-workflow list` → confirm the four new names appear with correct descriptions.
   - Run one alias end-to-end: `/prompt-workflow c-fix --bg "checkout intermittent"`. Watch via `/subagents-fleet`.

## 5. **Verification**

- **Discovery** — `/prompt-workflow list` shows all four new names with descriptions derived from frontmatter.
- **Invocation parity** — running an alias produces the same chain of forked subagents as the long form, verified by comparing the `/subagents-fleet` entry (agent sequence, model, async flag).
- **Argument passthrough** — `… --bg "X"` substitutes `$@` with `X` inside every step's task (the existing `substituteArgs` function in `prompt-workflows.ts` handles this; covered by `test/chain-workflow.test.ts` for the long form — add one case for an alias).
- **No regression on long form** — re-run the original `/prompt-workflow c-fix-commit "…"` and confirm it still works.
- **No name collision** — grep `RESERVED_COMMAND_NAMES` in `prompt-workflows.ts` against the four new names; no overlap.

## 6. **Risks & Rollbacks**

- **Risk:** an alias name collides with a future host command. *Mitigation:* names are kept under the `c-*` namespace; reserved set is checked before commit.
- **Risk:** the `:prompts` picker now shows duplicate-looking entries (long + short). *Mitigation:* document that the short form is the preferred UX; do not remove the long form.
- **Risk:** Option B's prompt-template engine does not preserve quoted arguments, so the first space in the topic breaks. *Mitigation:* test with a multi-word topic first; if broken, drop B and ship A only.
- **Rollback:** delete the four new `c-*.md` files. No other file is modified. Doc rollback is a one-commit revert. No migrations, no settings.json changes.

## 7. **Open Questions**

- Does the running host version of pi preserve quoted arguments in prompt-template expansion? (Determines whether Option B is viable as a one-word `/fix …` command or only as a less-clean shortcut.)
- Should the alias files be **plain wrappers** (so `/prompt-workflow c-fix …` works) **or also** install a true `/c-fix` command (which requires a small extension registered with `pi.registerCommand`)? The latter is the cleanest UX but widens scope to extension authoring.
- Is the user OK with `c-fix`, `c-build`, `c-refactor`, `c-sec` as the short names, or do they prefer something else (e.g. `/fix`, `/build`, `/refactor`, `/sec` one-word forms)?
- Should the alias body explicitly include `--bg` in its example so the docs aren't the only place that says "always background", or leave `--bg` opt-in like the canonical form?

---

Now producing the required evidence for the reviewed acceptance contract.

## Acceptance Evidence

- **changed-files**: none (plan only; no implementation yet)
- **tests-added**: none (plan only; will add alias-substitution case to `test/chain-workflow.test.ts` when implementing)
- **commands-run**: read-only inspection of `~/.pi/agent/prompts/`, `pi-subagents/src/slash/prompt-workflows.ts`, `pi-subagents/src/slash/slash-commands.ts`, `~/.pi/agent/settings.json`, `Doc/chain-commands.md`, `Doc/prompts.md` — all succeeded
- **validation-output**: confirmed `RESERVED_COMMAND_NAMES` set does not collide with proposed short names; confirmed `discoverPromptWorkflows` reads from `~/.pi/agent/prompts/` so new files will auto-register; confirmed `chain:` frontmatter is the supported way to declare a multi-prompt chain
- **residual-risks**: scope question on Option B (host template engine behavior); alias-vs-command decision still open
- **no-staged-files**: true