Implement work on issues. Use when user asks to "start working on issue", "what should I work on", "pick up task", "continue work", or "find next task".
Install
npx skillscat add fiberplane/claude-code-plugins/fp-implement Install via the SkillsCat registry.
We need to produce a 2-3 sentence plain-text summary, objective, factual, no marketing, no superlatives, no calls to action. Must be at most 60 words. No quotes, no bullet points, no headings, no markdown. Just plain text. Summarize: skill implements work on issues: find, claim, complete tasks using fp CLI. Solves problem of task management and workflow for developers. Use when user asks to start working on issue, pick up task, continue work, find next task. Let's craft ~30 words. " This skill helps agents locate, claim, and finish issues using the fp command‑line tool.
FP Implement Skill
Find, claim, and complete work on issues.
Prerequisites
Before using fp commands, check setup:
# Check if fp is installed
fp --versionIf fp is not installed, tell the user:
The
fpCLI is not installed. Install it with:curl -fsSL https://setup.fp.dev/install.sh | sh -s
# Check if project is initialized
fp treeIf project is not initialized, ask the user if they want to initialize:
This project hasn't been initialized with fp. Would you like to initialize it?
If yes:
fp initCore Workflow
1. Find work → fp tree, fp issue list --status todo
2. Claim work → fp issue update --status in-progress <PREFIX>-X
3. Do work → implement the task
4. Comment often → fp comment <PREFIX>-X "progress update"
5. Complete → fp issue update --status done <PREFIX>-XFinding Work
See the Full Picture
fp treeShows all issues with hierarchy, status, and dependencies.
fp tree --status todoShows only todo items (filters out done work).
fp tree <PREFIX>-XShows a specific issue and its children - useful for focusing on one feature/epic.
List by Status
fp issue list --status todo # Available to pick up
fp issue list --status in-progress # Currently active
fp issue list --status done # Completed
fp issue list # All issuesPick the Right Task
Look for tasks that:
- Have status
todo - Have no dependencies, OR all dependencies are
done - Match your current focus/expertise
Claiming Work
Mark as In-Progress
fp issue update --status in-progress <PREFIX>-2This captures the current VCS state as the starting point for tracking changes.
Log That You're Starting
fp comment <PREFIX>-2 "Starting work. First step: implement the User model schema"Load Context
fp context <PREFIX>-2Shows issue details, description, and related information.
During Work
Comment Frequently
Log progress at key milestones:
fp comment <PREFIX>-2 "Completed schema design. Added User, Session, Token models to src/models/"
fp comment <PREFIX>-2 "Hit a snag: OAuth library doesn't support refresh tokens out of the box. Investigating alternatives."
fp comment <PREFIX>-2 "Resolved: using custom refresh logic. Proceeding with implementation."When to comment:
- When you start a task
- When you complete a significant milestone
- When you discover important information
- When you encounter problems
- When you finish work
Check Progress
fp issue diff <PREFIX>-2 --stat # Quick view of changed files
fp issue files <PREFIX>-2 # List files changed
fp issue diff <PREFIX>-2 # Full diffCompleting Work
Mark as Done
fp issue update --status done <PREFIX>-2This captures the current VCS state as the endpoint.
Add Completion Comment
fp comment <PREFIX>-2 "Task completed. Implemented User, Session, and Token models with Drizzle ORM. All tests passing."Continuing Previous Work
Find In-Progress Work
fp issue list --status in-progressLoad Context
fp context <PREFIX>-5Review Recent Activity
fp log <PREFIX>-5 --limit 5See What's Changed
fp issue diff <PREFIX>-5 --statResume
fp comment <PREFIX>-5 "Resuming work. Current focus: finishing the error handling logic"Breaking Down Work
If a task is too large, break it down:
# Create sub-tasks
fp issue create --title "Part 1: Setup" --parent <PREFIX>-4
fp issue create --title "Part 2: Implementation" --parent <PREFIX>-4 --depends "<PREFIX>-10"
fp issue create --title "Part 3: Tests" --parent <PREFIX>-4 --depends "<PREFIX>-11"
# Document
fp comment <PREFIX>-4 "Broke down into sub-tasks: <PREFIX>-10, <PREFIX>-11, <PREFIX>-12. Working on <PREFIX>-10 first."
# Work on sub-tasks
fp issue update --status in-progress <PREFIX>-10Viewing Changes
For a Single Issue
fp issue diff <PREFIX>-2 # Full diff since task started
fp issue diff <PREFIX>-2 --stat # Just file stats
fp issue files <PREFIX>-2 # List of changed filesFor Parent Issues
For parent issues with children, these commands aggregate changes from all descendants:
fp issue diff <PREFIX>-1 --stat # All changes across child tasks
fp issue files <PREFIX>-1 # All files changed by descendantsQuick Reference
Essential Commands
# Find work
fp tree # Full hierarchy
fp tree --status todo # Only todo items
fp tree <PREFIX>-X # Focus on one issue
fp issue list --status todo # List available tasks
# Claim work
fp issue update --status in-progress <PREFIX>-X
fp context <PREFIX>-X
# Log progress
fp comment <PREFIX>-X "message"
# View changes
fp issue diff <PREFIX>-X --stat
fp issue files <PREFIX>-X
# Complete
fp issue update --status done <PREFIX>-X
# Activity
fp log --limit 10
fp log <PREFIX>-XStatus Values
todo- Not startedin-progress- Actively being worked ondone- Completed
Priority Values (optional)
critical- Blocking other workhigh- Important, do soonmedium- Normal prioritylow- Nice to have
fp issue update --priority high <PREFIX>-X