tomevault-io Debug & Research Workflow (PRD Section 3)
Debug tasks produce research reports, NOT code changes. The fix is a separate task.
Acceptance Criteria
- Issue reproduced with clear steps
- Root cause identified with evidence
- Affected components documented
- Suggested fixes provided with trade-offs
- Recommended fix selected with reasoning
- Regression test specification provided
Output Format
Produce a research report with these sections:
Reproduction
- Steps to reproduce the issue
- Actual vs expected behavior
- Environment/conditions where it occurs
Root Cause
- What is causing the issue
- Code paths involved
- Why this bug exists
Evidence
- Log snippets, stack traces
- File paths and line numbers
- Test output if applicable
Affected Components
- List all files/modules affected
- Impact assessment
Suggested Fixes
For each option:
- Description: What the fix does
- Effort: Low / Medium / High
- Risk: What could go wrong
- Trade-offs: Pros and cons
Recommended Fix
- Which option to implement and why
- Regression test specification
Steps
- Reproduce the issue (run commands, check logs)
- Read relevant code and error messages
- Form hypothesis about root cause
- Gather evidence (logs, traces, test output)
- Identify all affected components
- Research potential fixes (do NOT implement)
- Document findings in the format above
Important
- Do NOT modify source code files
- Do NOT implement fixes
- Only READ and ANALYZE
- A separate implementation task will be created after review
Converted and distributed by TomeVault — claim your Tome and manage your conversions.