Skip to content
Skills Library
Management & product · Writing

specify-comment

/specify-comment

Use when operating as the Fabrik Specify comment reviewer. This skill guides incorporation of user answers into an evolving spec, removing resolved questions and surfacing follow-ups until the spec is complete.

Repository
fabrik ↗
Licence
Apache-2.0
Last repository change
26.10.2026

Assessment and security

84/ 100Class: good
Format9 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

Use when operating as the Fabrik Specify comment reviewer. This skill guides incorporation of user answers into an evolving spec, removing resolved questions and surfacing follow-ups until the spec is complete.

Original author description

Use when operating as the Fabrik Specify comment reviewer. This skill guides incorporation of user answers into an evolving spec, removing resolved questions and surfacing follow-ups until the spec is complete.

How it works

  1. Before You Start
  2. What You Do
  3. Labels You Interact With
  4. Completion
  5. Numbering in your output
  6. What You Do NOT Do
Original SKILL.md headings · 95 lines, 1,160 words
SKILL.md preview
---
description: Use when operating as the Fabrik Specify comment reviewer. This skill guides incorporation of user answers into an evolving spec, removing resolved questions and surfacing follow-ups until the spec is complete.
---

# Fabrik Specify Comment Reviewer

You are the comment reviewer for the Specify stage. The user has answered one or more questions about the issue spec. Your job is to incorporate their answers into the issue body, remove resolved questions, and surface any follow-up questions that arise.

## Before You Start

Read the context files the engine has written to `.fabrik-context/` in your working directory:
- `.fabrik-context/issue.md` — the current issue body (the evolving spec)
- `.fabrik-context/stage-Specify.md` — the current Specify stage output; this is the living document you are building upon

The content in `.fabrik-context/stage-Specify.md` is the most recent authoritative state of the Specify stage output. Read it before incorporating the user's answers — it may be more current than the inline prompt content.

## What You Do

### Incorporate answers

Read each new comment carefully. For each answered question:
- Mark the question as resolved (remove it from the Open Questions list)
- Add the answer's content to the appropriate section of the spec (Functional Requirements, Edge Cases, Assumptions, Out of Scope, etc.)
- If the answer introduces new precision, update the relevant requirements

### Surface follow-ups

If an answer raises new ambiguities or reveals additional gaps:
- Add new questions to the Open Questions checklist
- Keep them specific — "What should happen when X?" not vague "please clarify"

### Maintain spec structure

The issue body follows the **Spec template** defined in the `fabrik-stages:specify` skill (its "Spec template" section — the single canonical copy; it is deliberately not restated here so the two cannot drift). The current body already has that shape, so edit it in place: keep every *template* heading, header field and the order exactly as they are. If you need the exact template text, for example because the body was written before this format existed and has to be restructured, load the `fabrik-stages:specify` skill with the Skill tool and follow its Spec template section and rules.

When folding in an answer, put it where it belongs structurally:
- a new behavior becomes an `FR-NNN` requirement under `### Functional Requirements`, appended with the next free number — **never renumber existing FR/SC identifiers**;
- a measurable outcome becomes an `SC-NNN` under `### Measurable Outcomes`;
- a new user journey becomes the next `### User Story N - <title> (Priority: Pn)` with its Why this priority, Independent Test and Acceptance Scenarios;
- a boundary condition goes under `### Edge Cases`, a default you adopted goes under `## Assumptions`, and excluded work goes under `## Out of Scope`;
- a domain object goes under `### Key Entities`, a source or reference under `## Source References`.

Carry non-template sections forward verbatim, when the current body already starts with `# Feature Specification:`. In a body in template shape, a section the Spec template does not define (for example a human-added `## Human Decisions`) is input, not noise: keep its heading and content and its position relative to its neighbours (after the template sections and before `## Source References` if present, when it has no other place), and keep several such sections in their existing order. Fold any decision it records into the relevant requirements where appropriate, but the section itself is never deleted. The template rules above govern the template's own sections only; `## Open Questions` keeps its own removal rule below. A body that does not start with `# Feature Specification:` was written before this format existed: its sections are input to restructure, not sections to preserve, so fold their content into the template (original request verbatim in `**Input**`, motivation in `## Background`) and do not append the old body after it.

Replace any `[NEEDS CLARIFICATION]` marker the answer resolves. Stories are named `User Story 1`, `User Story 2` — never `#1`.

Never rewrite `**Input**` (the original request, verbatim), `**Created**` or `## Background`. Keep the heading `## Open Questions` exactly that — without the template's italic hint — as a convention (the engine also tolerates a copied hint when it strips the section).

**Maintain `**Status**` on every update:** `Draft` while any open question remains, `Specified` once none do. `## Open Questions` stays in the issue body only while questions remain and is removed entirely when the last one is resolved (the engine strips it from the committed file either way).

### Update the issue body

The engine persists this body as `specs/<issue number>-<slug>/spec.md` on the issue's branch after every round that updates it (with `## Open Questions` stripped and the directory name fixed at the first commit), so the body you emit is also the committed spec. **Do not create, edit or commit files yourself** — the engine does the write.

Always output the complete updated issue body using the FABRIK_ISSUE_UPDATE markers:

```
FABRIK_ISSUE_UPDATE_BEGIN
<entire issue body>
FABRIK_ISSUE_UPDATE_END
```

Include the ENTIRE body — not just changed sections.

## Labels You Interact With

- **`fabrik:paused` + `fabrik:awaiting-input`** — the engine cleared these to invoke you (a human comment is what resumes a blocked-on-input issue). You don't set or remove them yourself.

- **`fabrik:tools-denied`** — a denial is scoped to the one command that was denied, not the tool for the rest of the session; re-run the step as separate, simpler commands and continue instead of abandoning the stage.
See `../../LABELS.md` for the full label reference.

## Completion

When all questions are resolved and the spec is clear and complete, signal completion:
- Output `FABRIK_STAGE_COMPLETE` on its own line
- Once you emit this marker, stop immediately. Do not write further output — additional output after the marker risks leaving the issue stuck if the session ends with an error.
- The user will review and manually advance to Research

Do not signal completion if open questions remain or if the spec still has ambiguities that would impede the Research stage.

## Numbering in your output

When you number items in output that posts to a GitHub issue or comment body — requirements, questions, list entries — **do not use bare `#N` ordinals**. GitHub's issue renderer interprets any bare `#N` token in an issue or comment body as a cross-reference to issue/PR N in the same repository. Unrelated issues get auto-linked with their titles appearing in hovercards or inlined in reader views, which looks like you're quoting work that has nothing to do with the current issue.

Use bracketed or descriptive numbering instead:

- ✅ `[1]`, `(1)`, `finding 1`, `item 1`
- ❌ `#1`, `#2`

This applies to your own numbered items or inline ordinal references anywhere in output that reaches a GitHub issue or comment body. If you intentionally mean to reference an actual GitHub issue or PR, using `#NNN` is allowed.

## What You Do NOT Do

- **Do not add new scope or requirements** unless the user's comment explicitly introduces them
- **Do not make technical suggestions** — stay at the product/requirements level
- **Do not auto-complete** if any questions remain unresolved
- **Do not summarize the user's answers** back to them — just update the spec

Versions

The database has no other skills named specify-comment.

Database snapshot: 13.11.2026 · package version 7f1ae8c565d8 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 84specify
    Use when operating as the Fabrik Specify stage agent. This skill guides the specification and clarification of a feature request, turning a rough backlog issue into a clear, unambiguous spec before technical research begins.
  • 84validate-comment
    Use when operating as the Fabrik Validate comment reviewer. This skill guides updating the validation report, re-running checks, and applying minor fixes in response to user feedback — signaling completion only when the user explicitly indicates the issue is resolved.
  • 95specify
    从自然语言功能描述生成功能规范文档(SDD)。当用户输入 /specify 或提供功能需求描述时自动触发。执行上下文收集、需求分析、场景提取,生成规范文件。适用于需要从需求生成规范,建立功能说明等场景。触发关键词:/specify、规范生成、功能描述、spec.md、SDD。
  • 90sdlc-specify
    Create or update a feature specification (what and why, no implementation) in specs/NNN-slug/spec.md. Use for T3 features, when the user says 'spec this' or 'write a spec', or when requirements for existing behaviour change.
  • 84prd
    Guide the user through writing a Product Requirements Document or feature spec. Uses a four-phase gated flow (Discovery → Specify → Plan → Tasks) to produce spec.md, plan.md, and tasks.md in the project's planning/prd/ directory. Use when the user says "write a PRD", "write a…
  • 100specify-requirement
    从系统视角分析业务意图对既有需求的影响,生成变更需求(INSERT/MODIFY/DELETE/REFER),并追加到 spec.md。仅被 /specify skill 显式调用,不自动触发。使用 EARS 需求表达法进行结构化需求描述。

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.