fabrik-implement

Executes planned implementation tasks by writing, testing, committing, and pushing code on a feature branch.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When an AI agent implements a feature autonomously, it can lose progress on interruption, diverge from the agreed plan, skip tests, or break downstream automation by creating pull requests incorrectly. This Skill operationalizes the Implement stage of the Fabrik SDLC pipeline so code changes are committed incrementally, tested, pushed, and handed off to the engine in a predictable format. ## Core Features & Use Cases - Plan-driven execution: Reads the task checklist from .fabrik-context/stage-Plan.md and works through tasks in order, resuming from prior commits instead of restarting. - Disciplined Git workflow: Enforces one Conventional Commit per task, frequent pushes, and task check-off in the Plan stage comment via the GitHub CLI. - Engine-coordinated PR creation: Signals pull request creation through a FABRIK_PR_CREATE_BEGIN/END marker instead of calling gh pr create, so the engine owns the Closes #N line. - Safe long-running verification: Prescribes foreground, timeout-bounded test and dev-server patterns so no orphaned processes outlive the stage. - Use Case: An issue planned by the Fabrik Plan stage is picked up; the agent implements each task with tests, commits and pushes incrementally, updates the checklist comment, emits the PR marker, and finishes with FABRIK_STAGE_COMPLETE. ## Quick Start Invoke this skill as the Fabrik Implement stage agent to execute the plan in .fabrik-context and produce committed, tested, pushed code on the issue branch.

Frequently Asked Questions about fabrik-implement

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

FAQPage Schema
How does the Fabrik Implement stage execute an implementation plan?

It reads the task checklist from .fabrik-context/stage-Plan.md and works through tasks in order: implement, compile, test, commit with a Conventional Commit message, push, and check off the task in the Plan stage comment. The plan is authoritative and must not be redesigned.

How do I create a pull request in a Fabrik stage without gh pr create?

Emit a FABRIK_PR_CREATE_BEGIN/END marker block with a TITLE line and reviewer-oriented body. The engine reads the block, prepends the Closes #N line, and calls gh pr create itself, so agents never write closing keywords or call gh pr create directly.

Can the Implement agent run a dev server or long test suite in the background?

No. Backgrounded processes detach via setsid and outlive the stage as orphaned processes holding ports. Use one-shot build commands, bracket servers with trap-based teardown in a single command, or bound them with timeouts, and always run tests with framework timeout flags.

What happens if the Implement stage hits the turn limit or fails?

The engine creates a partial-progress commit of uncommitted changes and pushes them, preserving work for the next attempt. On retry, the agent resumes by checking git status, git log, and the checked-off tasks rather than starting over.

Why must stage output not be posted to GitHub with gh issue comment?

Directly posted comments bypass the engine's formatting, create duplicates, and trigger a self-review loop because the engine treats them as new user input. All stage output goes to stdout, which the engine posts as a formatted Fabrik stage comment.