reflect

Interviews the user one question at a time to stress-test plans and designs.

20|2|Updated May 16, 2026
One-click install
npx skills add https://github.com/reddb-io/red-skills --skill reflect-reddb-io
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reflect
Source: https://github.com/reddb-io/red-skills/tree/main/plugins/dev/skills/productivity/reflect
Command: npx skills add https://github.com/reddb-io/red-skills --skill reflect-reddb-io

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Plans and designs often contain hidden assumptions and unresolved decision branches that only surface during implementation. This Skill systematically interviews you about a plan until every branch of the decision tree is understood and resolved. ## Core Features & Use Cases - Structured Interviewing: Asks one question per turn with a recommended answer and a one-sentence reason, never stacking questions. - Decision Tree Resolution: Walks each branch of the plan's decision tree, resolving dependencies between decisions one by one. - Codebase-Grounded Questions: Explores the codebase to answer questions itself instead of asking when the answer is discoverable in code. - Use Case: Before starting a large refactor, run a reflection session to pressure-test the migration plan, resolve open design questions, and land the agreed decisions in documentation. ## Quick Start Ask the agent to reflect on your current plan or design and answer its interview questions one at a time.

Frequently Asked Questions about reflect

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I stress-test a plan before implementing it?▼

Run a reflection session where the agent interviews you one question per turn about your plan. Each question includes a recommended answer with reasoning, and the session continues until every branch of the decision tree is resolved.

How to resolve design decisions with an AI assistant?▼

Use an interview-style approach where the assistant asks focused questions sequentially rather than listing everything at once. Dependencies between decisions are resolved one by one, and answers discoverable in the codebase are looked up instead of asked.

Does the reflect skill ask all questions at once?▼

No, it strictly asks one question per turn and waits for your reply before proceeding. This cadence prevents stacked questions and ensures each decision branch is fully resolved before moving ahead.

When should I not use an interview-based plan review?▼

Avoid it for trivial tasks with no open design questions or when you need immediate execution rather than deliberation. The skill is designed for plans with meaningful decision branches that benefit from explicit resolution.

What happens when a reflection session ends?▼

The skill runs a shared doc-landing finalizer before exiting, which lands the outcomes of the session into documentation. This ensures resolved decisions are captured rather than lost when the conversation ends.