What problem does it solve? Review cycles on planning documents leave scattered inline comment threads that must each be addressed, answered, or escalated. Manually tracking which threads are resolved, rejected, or still open across markdown and HTML docs is error-prone and loses decision history. ## Core Features & Use Cases - Thread Triage: Parses review comment threads in markdown (HTML comment blocks) and HTML (pd-thread/pd-comment elements) planning docs, then resolves, rejects, or leaves each thread unresolved with an author reply. - Append-Only History: Preserves full decision history by never deleting prior comments, updating only thread status labels (RESOLVED, REJECTED, UNRESOLVED) and appending AUTHOR replies. - Use Case: After a reviewer leaves P1/P2 comments on plan.html and context.md in docs/tasks/042-auth-redesign/, run this skill to fix valid concerns in place, reject inapplicable ones with cited rationale, and get a summary of threads still needing human input. ## Quick Start Resolve all review comments left on the planning docs for task 042 and summarize which threads were resolved, rejected, or still need my input.