gf-work

Execute approved GuanFu plan slices and log verification evidence.

Updated Apr 25, 2026
One-click install
npx skills add https://github.com/Sailfishc/guanfu --skill gf-work
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gf-work
Source: https://github.com/Sailfishc/guanfu/tree/main/skills/gf-work
Command: npx skills add https://github.com/Sailfishc/guanfu --skill gf-work

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Implementing an approved active GuanFu plan slice in a repository without manual, ad-hoc steps, ensuring traceable execution and fresh verification evidence.

Core Features & Use Cases

  • Automates the execution of a single plan slice within an existing repository, updates the living plan, and records verification artifacts.
  • Supports autonomous operation after plan approval with explicit logging of assumptions, outputs, and hand-off to review.
  • Use Case: When a plan slice is ready, gf-work runs the slice, logs progress, verifies outcomes, and prepares for code-review.

Quick Start

Begin execution of the active plan slice and capture fresh verification evidence.

Frequently Asked Questions about gf-work

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

FAQPage Schema
How do I automate workflow execution for an approved plan slice in my repository?

Workflow execution for an approved plan slice is automated by running the slice directly, updating the living plan, and generating verification evidence. This ensures traceable execution while logging assumptions and routing reviews.

What is a living plan and when do I need to update it during development?

A living plan is an active, evolving project document that requires updates after executing workflow slices. You need to update it to maintain traceable progress, record verification artifacts, and prepare the work for automated review.

Can I execute plan slices autonomously without manual ad-hoc steps?

Yes, you can execute plan slices autonomously after plan approval. The automation enforces an autonomous contract, logs assumptions and outputs explicitly, and handles hand-off to review without requiring manual ad-hoc steps.

Does automating plan verification alter or destroy my existing repository files?

Automating plan verification only performs safe, non-destructive work within your repository. It generates fresh verification evidence and logs progress without altering or destroying your existing source files.

What is the best way to prepare for code review after completing a workflow slice?

The best way to prepare for code review is to automate the execution of your plan slice to generate verification artifacts. This automatically logs outcomes and routes the completed work directly to the review process.

Why does autonomous workflow execution require logging assumptions?

Autonomous workflow execution requires logging assumptions to enforce the autonomous contract and ensure traceable execution. Recording these assumptions provides necessary context for the hand-off to code review.