framework/engineering/skills/flowai-diagnose-benchmark-failure/acceptance-tests/md-prior-bullets/fixture/framework/engineering/skills/flowai-conduct-qa-session/SKILL.md
How to conduct a Q&A session with the user. Canonical reference for FR-UNIVERSAL.QA-FORMAT.
npx skillsauth add korchasa/flow flowai-conduct-qa-sessionInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
When prompting the user to choose, use the exact transcript shape shown below. Imitate the assistant lines verbatim — only swap placeholder text. Do NOT rewrite the structure into your usual markdown habits: bullets or dashes for option choices are wrong in this skill.
For a multi-select prompt, the option list MUST end with two extra service
options literally named all and agent's choice appended after the real
choices, in that order.
1.,
2., …- option,
* option, — option.all, agent's choice).
Single-select does not.tools
Delegate a task to another AI IDE's CLI (codex / claude / opencode / cursor-agent) through an isolated-context subagent. Triggers on "delegate to <ide>", "have <ide> do <task>", "execute <task> in <ide>", "offload to <ide>". For one-shot relay or fan-out comparison use `ai-ide-runner` instead.
tools
Run prompts in Claude Code, OpenCode, Cursor, or Codex CLIs from the current session — pick one IDE, fan out across several, or compare models. You are a courier that relays the other runtime's stdout verbatim, do not synthesise your own answer. Use on "run in <ide>", "compare <ide> vs <ide>", "try on <model>", "which IDE handles X better", "run across models".
tools
Recommend which LLM model to use for a task. Use when asked "which model / best LLM for X", "pick a model for this task", or for a model shortlist ranked by live leaderboard evidence (coding, reasoning, agentic, tool-use, price, speed). Live-fetches public leaderboards and ranks models with per-axis rationale and citations.
development
Produce a comprehensive Product Requirements Document (PRD). Use when the user asks to write a PRD or formalize a feature's scope, goals, and success metrics.