egregore-labs/egregore / .codex/skills/ingest-user-interview
ingest-user-interview
UnverifiedAnalyze a user interview from Granola, pasted text, or a file into an evidence-backed briefing, journey insights, product findings, patterns, and actions. Use for /ingest user-interview, onboarding interviews, research calls, or requests to process user feedback.
Egregore ingest-user-interview Adapter
This adapter runs the canonical Egregore workflow for ingest-user-interview. Its one
maintained body is .claude/skills/ingest-user-interview/SKILL.md; read that file completely and follow it here.
Use the project shell and filesystem directly. Do not invoke Claude Code
commands. Translate interactive choices to structured Codex question tooling
when it is available; otherwise render compact numbered choices with an
Other: option and wait for the user.
Structured UX parity
This workflow has a Claude skill with user-visible structured output. After
reading .claude/skills/ingest-user-interview/SKILL.md, reproduce the same visible UX in Codex:
- Preserve TUI boxes, markdown tables, rich cards, browser artifact rendering, exact confirmation blocks, and "no preamble" rules from the source skill.
- Use the source skill's frame width, section order, labels, status footer, and examples as the contract for the final response.
- Never replace a required box/table/card/artifact view with a prose summary unless the user explicitly asks for a summary.
- When the source says to output a TUI box directly, paste that box as the
visible response, preferably in a
textfenced block. - If the canonical body says the command's stdout is the card and must not
be repeated, that rule assumes a host that displays command output in full;
in Codex, paste the card once as the visible response in a
textfenced block and do not print it a second time. - Never show raw JSON, raw command output, or unformatted script output when the source skill requires formatted status or rendered output.
- Read
.claude/skills/ingest-user-interview/SKILL.mdfor the workflow details. - Run the referenced
bin/scripts directly from Codex. - Treat graph and publish steps as best-effort unless that workflow explicitly says they are required.
- For every external notification, follow
.claude/context/notification-consent.md: plan without sending, then show a separate exact Send / Edit / Cancel checkpoint. Never infer notification consent from the workflow request or a batch approval. - Keep local-mode behavior filesystem-first and avoid graph or notification
calls when
egregore.jsondeclares"mode": "local". - Never call the deprecated
egregore-handoffCLI for Egregore project handoffs.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| add-product-e2e-evalpaperclipai/paperclipAdd or extend a Paperclip full-stack runner E2E workflow, fixture, matcher, or report evidence path for local or Daytona execution. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| add-runner-evalpaperclipai/paperclipAdd or extend a Paperclip Runner protocol evaluation definition, roster, assertion, or report fixture with provenance and narrow validation. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| diagnose-why-work-stoppedpaperclipai/paperclipCompatibility entry point for failed, stalled, looping, or over-recovered Paperclip work. Use fix-failed-paperclip-run for the full diagnosis, regression, repair, real verification, and green-PR workflow; honor an explicitly requested diagnosis-only scope. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| fix-failed-paperclip-runpaperclipai/paperclipDiagnose and fix failed, stuck, slow, or incorrectly blocked Paperclip tasks and runs. Use with a task/run URL or failure report to trace the root cause, prove a regression red then green, check second-order effects, verify the real workflow, and deliver a PR with passing checks. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |