fabrik-research-comment

Incorporates user comment answers into Fabrik Research stage findings on GitHub issues.

22|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/handarbeit/fabrik --skill fabrik-research-comment-handarbeit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fabrik-research-comment
Source: https://github.com/handarbeit/fabrik/tree/main/plugin/fabrik-workflows/skills/fabrik-research-comment
Command: npx skills add https://github.com/handarbeit/fabrik --skill fabrik-research-comment-handarbeit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a Fabrik-managed GitHub issue is paused awaiting input during the Research stage, user replies arrive as issue comments that must be merged into the living research findings. Manually reconciling answers, resolved questions, and new follow-ups into the stage comment is error-prone and can leave issues stuck. ## Core Features & Use Cases - Answer Incorporation: Reads .fabrik-context/issue.md and .fabrik-context/stage-Research.md, then merges each user answer into the relevant findings and removes resolved questions from the Open Questions list. - Follow-up Surfacing: Detects new ambiguities or contradictions revealed by answers and adds focused follow-up questions to the findings. - Stage Completion Signaling: Emits FABRIK_STAGE_COMPLETE only when all open questions are resolved and research is sufficient for the Plan stage; otherwise keeps the research loop open. - GitHub-Safe Formatting: Avoids bare #N ordinals in comment output to prevent unintended issue cross-references. - Use Case: A user replies to three open research questions on issue #42; the skill produces the full updated Research stage comment with two questions resolved, one finding updated, and one new follow-up question added. ## Quick Start Ask the agent to review the latest user comment on the issue and update the Research stage findings accordingly.

Frequently Asked Questions about fabrik-research-comment

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

FAQPage Schema
How do I update research findings from GitHub issue comments?

Read the current stage output from .fabrik-context/stage-Research.md, merge each user answer into the relevant finding, remove resolved questions from Open Questions, and output the complete updated findings so the engine can rewrite the stage comment.

What is the Fabrik Research stage in a GitHub issue workflow?

The Research stage is a read-only phase where findings, decisions, and open questions about an issue are gathered before planning. Its output lives in a stage comment on the issue, not in the issue body, which remains the untouched spec.

When should FABRIK_STAGE_COMPLETE be emitted?

Emit FABRIK_STAGE_COMPLETE on its own line only when all open questions are resolved and the research is sufficient for the Plan stage. If answers are partial or new questions arise, do not signal completion and stop output immediately after the marker when you do.

Why avoid bare #N numbering in GitHub comment output?

GitHub interprets any bare #N token in a comment body as a cross-reference to issue or PR N, auto-linking unrelated issues. Use bracketed forms like [1] or (1) for ordinals, reserving #NNN only for intentional issue references.

Can the Research stage modify code or the issue body?

No. Research is a read-only stage: it does not commit code changes and does not use FABRIK_ISSUE_UPDATE markers. Findings are written only to the Research stage comment, and the issue body stays unchanged as the spec.