design-chain
Run one design round through the design chain: vision, owners, brief with verbatim anchors, three directions, craft manifest,…
Advance the active PRD to `approved` (blocked by pending findings)
> /plugin marketplace add assafkip/kipi-systemHow it fires
How this command gets triggered: by you, by Claude, or both.
/prd-approveContext preview
What this command does when you run it.
Advance the active PRD to `approved` (blocked by pending findings)
description: Advance the active PRD to `approved` (blocked by pending findings) allowed-tools: Bash
Approve the active PRD. The runner's findings gate blocks approval when any finding is still `pending` or the findings JSONL contains an invalid line.
Do not bypass by editing the findings file. If the gate blocks, run `/prd-triage` to set dispositions, then retry this command.
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/prd_runner.py" advance approvedOn success, tell the author the next step is `/prd-split` to materialize the PRD's issue manifest into one issue spec per entry.
On block, surface stderr verbatim. The runner names the offending finding ids.
Give your AI the right knowledge, at the moment it needs it. Kipi turns the scattered knowledge around your work into context that follows you across AI sessions: decisions, conversations, projects, people, commitments, lessons, documents, history.
Run one design round through the design chain: vision, owners, brief with verbatim anchors, three directions, craft manifest,…
Create the queued Linear projects and issues that shell scripts captured offline.
Scaffold a new RCA document from the canonical template, ready to fill.
Synthesize the previous assistant response to audio; autoplays locally with controls.
Run the full voice review on one draft by hand (bands, shapes, echo, gate roster, channel rules).