fp-plan

FP Plan Skill

Create plans and break them down into trackable issues.

Prerequisites

Before using fp commands, check setup:

# Check if fp is installed
fp --version

If fp is not installed, tell the user:

The fp CLI is not installed. Install it with:

curl -fsSL https://setup.fp.dev/install.sh | sh -s

# Check if project is initialized
fp tree

If 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 init

---

When This Skill Triggers

1. User asks to "create a plan", "break down feature", "design implementation"
2. User pastes a Linear, GitHub, or Notion URL (import external issue/doc)
3. User runs /plan with no arguments (interactive plan import from ~/.claude/plans/)

---

Importing from External Sources

Detecting URLs

When user pastes a URL, detect the source and fetch content:

GitHub Issues (github.com/owner/repo/issues/123):

gh issue view <url> --json title,body,labels,state

Linear Issues (linear.app/team/issue/TEAM-123): Extract the issue ID (e.g., TEAM-123) from the URL, then use the get_issue MCP tool from the Linear server.

Notion Pages (notion.so/...): Use the notion-fetch MCP tool from the Notion server with the full URL or page ID.

After Fetching

Create an FP issue from the extracted content:

fp issue create \
  --title "<extracted title>" \
  --description "<extracted body/content>"

Then offer to break it down into subtasks (see Planning Workflow below).

---

Interactive Plan Import (when /plan invoked alone)

When user runs /plan with no additional text:

1. Check for existing plans:

   ls -la ~/.claude/plans/*.md 2>/dev/null
   

2. If plans exist, use AskUserTool to prompt:

   Found plans in ~/.claude/plans/:

   1. moonlit-brewing-lynx.md
   2. swift-falcon-auth.md
   3. [Create new plan instead]

   Which plan would you like to import?