help

Enforce reflection-first root-cause analysis before changes in Convex development.

3|Updated May 23, 2026

Search Tags:#development #problem-solving #guidelines #best-practices #convex #reflect

Ready to run

npx skills add https://github.com/waynesutton/finder9 --skill help-waynesutton

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: help
Source: https://github.com/waynesutton/finder9/tree/main/.codex/skills/help
Command: npx skills add https://github.com/waynesutton/finder9 --skill help-waynesutton

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reflection-first problem-solving methodology for Convex development ensures decisions are grounded, reducing guesswork and rework.

Core Features & Use Cases

Structured reasoning: Enforces a clear root-cause analysis before implementing any change.
Risk reduction: Improves code confidence and minimizes scope creep during mutations.
Use Case: Teams debugging Convex apps or designing features can apply the guidelines to verify assumptions and constraints before coding.

Quick Start

Begin every task by applying the five-step reflection process before coding.

Frequently Asked Questions about help

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

FAQPage Schema

How do I prevent decision paralysis when debugging or building features in Convex?▼

Reflection-first problem-solving methodology prevents decision paralysis by enforcing root-cause analysis before implementing any Convex changes. This structured reasoning approach reduces guesswork and minimizes rework during debugging and feature design.

What is the reflection-first process for Convex full-stack development?▼

Reflection-first problem-solving for Convex is a structured reasoning methodology that enforces root-cause analysis before implementing any code changes. It requires completing a five-step reflection process at the start of every task to verify assumptions and constraints.

How do I apply root-cause analysis before writing code for Convex mutations?▼

Apply root-cause analysis for Convex mutations by beginning every task with a five-step reflection process before coding. This structured approach verifies assumptions and constraints, reducing scope creep and improving code confidence.

Does a guided reflection methodology work for Convex code reviews and documentation?▼

Guided reflection works for Convex code reviews and documentation by applying structured reasoning to verify assumptions and constraints across the full project lifecycle. It ensures decisions remain grounded, improving review confidence and documentation accuracy.

Why should I use a reflection-first approach instead of directly modifying Convex code?▼

Use a reflection-first approach instead of directly modifying Convex code to reduce risk and minimize scope creep during mutations. Enforcing root-cause analysis before changes improves code confidence and prevents the guesswork that leads to rework.