fabrik-plan-comment

Revises implementation plans and task checklists based on user feedback in GitHub issue comments.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When users review an implementation plan posted as a GitHub issue comment and request changes, someone must carefully incorporate that feedback into the plan without losing structure or introducing scope creep. This Skill acts as the Plan stage comment reviewer in a Fabrik-driven workflow, updating the approach, task checklist, and documented decisions in response to user feedback. ## Core Features & Use Cases - Feedback Incorporation: Reads each new user comment and adjusts the implementation strategy, task ordering, and documented decisions accordingly. - Plan Structure Maintenance: Produces a complete, coherent updated plan with approach, numbered task checklist, decisions, and constraints that the engine writes back to the Plan stage comment. - Safe GitHub Formatting: Avoids bare #N ordinals that GitHub would auto-link to unrelated issues, using bracketed numbering instead. - Use Case: A user comments on issue #42 asking to swap a library choice and reorder two tasks; this Skill reads the current plan from .fabrik-context/stage-Plan.md, applies the changes, and outputs the full updated plan for the stage comment. ## Quick Start Ask the agent to review the latest plan feedback comments and produce an updated implementation plan reflecting the requested changes.

Frequently Asked Questions about fabrik-plan-comment

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

FAQPage Schema
How do I update an implementation plan based on GitHub issue comments?

Read the current plan from .fabrik-context/stage-Plan.md, apply each piece of user feedback to the approach, task checklist, and decisions, then output the complete updated plan. The Fabrik engine writes your output back to the Plan stage comment.

How does the Fabrik Plan stage handle user feedback?

The engine clears the paused and awaiting-input labels when a human comments, then invokes the plan comment reviewer. The reviewer revises the plan content and signals completion with FABRIK_STAGE_COMPLETE once the plan is concrete enough for implementation.

Why should I avoid #1 style 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 task and decision numbering instead.

Can the Plan comment reviewer modify code or the issue body?

No. Plan is a read-only stage: no code changes are committed, and FABRIK_ISSUE_UPDATE markers are not used because plan content lives in the stage comment, not the issue body.

When should the plan reviewer not signal completion?

Do not emit FABRIK_STAGE_COMPLETE if the plan still has ambiguities, unresolved questions, vague tasks, or if the user is clearly still providing feedback. Output after the marker risks leaving the issue stuck.