Qrspi New

---
name: qrspi-new
description: Codex CLI: bootstrap a QRSPI task — create thoughts/<task-id>/ from the phase templates and run the Questions phase. Use only when the user invokes it by name — `$qrspi:qrspi-new` — never because a prompt resembles it; in Claude Code the same command is /qrspi:new.
argument-hint: <TASK-ID> [ticket text, URL, or nothing]
disable-model-invocation: true
user-invocable: false
---

# Bootstrap a QRSPI task

> **Codex CLI form of `/qrspi:new`, invoked as `$qrspi:qrspi-new`.** Same steps, same gates. Plugin paths below
> — `../qrspi/references/…`, `$SKILL_DIR` in shell snippets — are relative to the
> directory holding this `SKILL.md` (Codex tells you where the skill lives; substitute
> the absolute path). `thoughts/…` is relative to the repository you are working in.
> Codex skills carry no tool allowlist: Codex's own approval mode and sandbox govern
> what runs.

Arguments: whatever follows `$qrspi:qrspi-new` in the user's message.

The first token is the task ID (e.g. `ENG-1234`). Everything after it, if present, is
the ticket text or a ticket URL.

## Steps

1. **Derive the directory name.** `thoughts/<TASK-ID>-<slug>/`, where `<slug>` is a
   2-4 word kebab-case summary of the ticket. If no ticket text was given, use the
   task ID alone and ask the user for the ticket before continuing to step 4.

2. **Create it and copy the six artifact templates:**

   ```bash
   mkdir -p thoughts/<dir>
   cp "$SKILL_DIR/../qrspi/references/"{00-questions,01-research,\
02-design,03-structure,04-plan,99-progress}.md thoughts/<dir>/
   ```

   Not `*.md`: `05-implement.md` is a prompt, not an artifact.

3. **Strip and fill each copy.** In every copied file, delete the `> **PROMPT`
   blockquote at the top — the plugin keeps it, and `$qrspi:qrspi-next` prints it when
   needed — and replace `<TASK-ID> <title>` in the H1. In `00-questions.md`, also
   replace the `## Ticket` placeholders with the real ID, link, title, and body.

4. **Run the Questions phase now.** Follow the `> PROMPT` block in
   `../qrspi/references/00-questions.md`, then fill in the
   `## Questions` section of `thoughts/<dir>/00-questions.md`. Constraints, restated
   because they are the whole point of this phase:
   - Do NOT propose solutions. Do NOT explore the codebase. Do NOT read any source file.
   - Max 10 questions, ordered by descending risk. More than 10 means the ticket
     needs splitting — say so instead of writing 15 questions.
   - Every question carries a **default assumption**, so the phase never blocks.

5. **Stop.** Report the created path and the questions that need human answers. Then
   tell the user, verbatim:

   > Answer the questions in `thoughts/<dir>/00-questions.md` (or accept the default
   > assumptions), then **start a fresh session** and run `$qrspi:qrspi-next <dir>`.
   > Research must not inherit this session's context — or the ticket text.

Do not continue into Research in this session. Rule 1 is not negotiable: a fresh
session at every phase boundary.