fp-workflow_skill

This skill orchestrates FP workflow sessions, guiding task pickup, progress logging, and VCS-based change tracking for efficient issue completion.

18

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill fiberplane/claude-code-plugins --skill fp-workflow

SKILL.md12.9 KB

Overview

This skill provides agent work session patterns for the FP CLI to claim, track, and complete issues using VCS-based change tracking. It codifies a commit-first rhythm (code → commit → log) and maps issue lifecycle transitions to automatic base/tip refs so work is reproducible. Use it to pick up tasks, continue sessions, hand off, and end work cleanly.

How this skill works

The skill inspects issue status, VCS state, and activity logs to guide agent actions. Marking an issue in-progress captures the current VCS ref as the base; marking it done captures the tip ref. Commands like fp issue diff, fp issue files, and fp log aggregate changes and history for the issue and its descendants. PreToolUse hooks enforce that commits exist before logging progress.

When to use it

When asked to start working on an issue ("start working on issue", "pick up task")
When you want the next actionable task ("what should I work on", "find next task")
When continuing or resuming in-progress work ("continue work", "pick up where I left off")
When handing off work to another agent or ending a session ("hand off", "end session")
When you need accurate VCS-backed change ranges for an issue

Best practices

Identify your agent with fp agent whoami at session start
Use fp tree and fp issue list --status todo to find available work
Claim work with fp issue update --status in-progress so FP captures the base ref
Follow the commit-first rule: commit changes before fp comment or fp issue update (hooks will block otherwise)
Comment after each commit to preserve context and log handoffs clearly

Example use cases

Pick a task: fp issue list --status todo → fp issue update --status in-progress FP-2 → commit → fp comment FP-2 "Starting work"
Resume work: fp issue list --status in-progress → fp context FP-5 → fp issue diff FP-5 --stat → fp comment FP-5 "Resuming"
Hand off: fp comment FP-3 "Taking over. Next: implement X" → update status as appropriate
Fix tracking after the fact: fp issue assign FP-5 --rev <commit> to retroactively attach commits
End session: commit, fp comment FP-2 "End of session: completed X. Next steps: Y" and optionally fp issue update --status done

FAQ

Use fp issue assign to retroactively link commits or specific revisions to the issue so base/tip tracking is corrected.

Why am I blocked from commenting?

PreToolUse hooks block fp comment or fp issue update when uncommitted changes exist. Commit first, then log to proceed.