debug-manual

A manual debug loop guides you through investigate-fix iterations with human verification at each step. You create a DEBUG.md file to track status and collect user feedback to validate visual fixes before proceeding.

A manual debug loop is a structured investigate-fix cycle that relies on human verification to validate each fix. It is best used for UI bugs and visual issues where automated verification cannot easily confirm the resolution.

Start a Belmont debug session by setting up a base path and creating a DEBUG.md file. This file structures the problem framing, tracks iteration status, and prepares prompts to dispatch sub-agents for each cycle.

Manual debugging applies to any issue where human verification speeds resolution. While commonly used for UI bugs, the iterate-fix loop works for any problem where automated test verification is unavailable or insufficient.

No, manual debugging does not require automated testing frameworks or external dependencies. It relies entirely on a DEBUG.md workflow, an iteration-logging structure, and disciplined prompts to coordinate human verification.

Manual debug loops depend on human verification for each iteration, which can slow down resolution compared to automated testing. They require disciplined prompt usage and active user feedback to prevent untracked or incomplete fix cycles.