fabrik-specify-comment

Incorporates user comment answers into an evolving GitHub issue spec during the Fabrik Specify stage.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a GitHub issue spec has open questions and users answer them in comments, someone must manually merge those answers into the spec, remove resolved questions, and detect new ambiguities. This Skill automates that review loop so the spec converges toward completeness without manual editing. ## Core Features & Use Cases - Answer Incorporation: Reads new issue comments and merges each answer into the appropriate spec section (Requirements, Scope) while removing resolved questions from the Open Questions checklist. - Follow-up Detection: Surfaces new ambiguities raised by answers as specific, actionable open questions. - Structured Spec Maintenance: Enforces a consistent issue body structure (Summary, Requirements, Scope, Open Questions, Prior Art, Risks) and emits the full updated body via FABRIK_ISSUE_UPDATE markers. - Use Case: A product manager answers three clarifying questions on a Fabrik-managed issue; the reviewer updates the spec, resolves those questions, adds one follow-up, and signals stage completion only when no questions remain. ## Quick Start Ask the agent to review the latest issue comments and update the Specify stage spec accordingly.

Frequently Asked Questions about fabrik-specify-comment

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

FAQPage Schema
How do I update a GitHub issue spec from comment answers?

Read the current issue body and stage output from .fabrik-context, merge each comment answer into the relevant spec section, remove resolved questions, and output the entire updated body between FABRIK_ISSUE_UPDATE_BEGIN and FABRIK_ISSUE_UPDATE_END markers.

What is the Fabrik Specify stage in a Claude Code workflow?

The Specify stage is a Fabrik workflow step where an issue body evolves into a complete spec. A comment reviewer incorporates user answers, maintains the spec structure, and signals completion once no open questions remain.

When does the Specify comment reviewer signal stage completion?

It outputs FABRIK_STAGE_COMPLETE only when all open questions are resolved and the spec has no remaining ambiguities that would block the Research stage. It must stop output immediately after the marker.

Why should I avoid bare #N numbering in GitHub issue comments?

GitHub interprets bare #N tokens as cross-references to issues or PRs, auto-linking unrelated work. Use bracketed forms like [1] or (1) for ordinal lists in issue or comment bodies instead.

What are the limitations of the Fabrik specify comment reviewer?

It cannot add scope or requirements unless the user's comment explicitly introduces them, makes no technical suggestions, and will not auto-complete while any open questions remain unresolved.