Meta-Issue: [Problem Title]

Navigation: Home > Getting Started > Manual Workflows > Templates

Domain: [architecture | performance | data | debugging] Scope: [version-range or "ongoing"] Created: YYYY-MM-DD Status: [Investigating | Resolved | Abandoned] Current Understanding: [One-sentence current belief about root cause]

---

Navigation

• Problem Description — Living document (updated as understanding evolves)
• Implementation Log — All attempts chronologically
• Test Cases — Validation scenarios
• Attempts — Numbered folders with detailed results
• Analysis — Root cause evolution, timeline, lessons

---

Quick Summary

Problem: [One paragraph describing the core issue]

Current Status:

• Attempts: [N] ([X] failed, [Y] successful, [Z] in progress)
• Latest Understanding: [Current root cause hypothesis]
• Next Steps: [What's being tried next]

---

Attempts

[Auto-populated from implementation-log.md]

1. 001-baseline — [Status] — [Brief outcome]
2. 002-approach — [Status] — [Brief outcome]

---

Key Insights

[Cross-references to KG entries and lessons]

• Pattern discovered
• Gotcha identified
• Lesson learned

---

Related Issues

• GitHub #XXX — [Context]
• Local issue-YYY — [Context]

---

How to Use This Meta-Issue

1. Add attempt: Create new attempts/NNN-name/ folder from attempt-template
2. Update understanding: Edit analysis/root-cause-evolution.md when beliefs shift
3. Log progress: Update implementation-log.md with each attempt
4. Extract lessons: Create lessons-learned when patterns emerge
5. Sync to KG: Run /kmgraph:update-graph to extract insights

---

Learn More

Concepts & Guides:

• Concepts Guide - Term explanations
• META-ISSUE-GUIDE.md - Full meta-issue guide

Resources:

• Real Examples - Real-world samples