pfSyncPull

Pulls PlanFlow cloud plan into local PROJECT_PL.md via authenticated API request.

1|Updated Jan 26, 2026
One-click install
npx skills add https://github.com/BekaChkhiro/claude-plan-plugin --skill pfsyncpull
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pfSyncPull
Source: https://github.com/BekaChkhiro/claude-plan-plugin/tree/main/commands/pfSyncPull
Command: npx skills add https://github.com/BekaChkhiro/claude-plan-plugin --skill pfsyncpull

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill synchronizes the PlanFlow cloud plan with your local PROJECT_PLAN.md, ensuring you always work on the latest plan offline and for versioning.

Core Features & Use Cases

  • Cloud-to-local synchronization: Pulls the latest cloud plan into PROJECT_PLAN.md for editing and archiving.
  • Change detection: Detects diffs between local and cloud plans and presents them before writing.
  • Safe write & authentication: Validates authentication and project linkage, then writes to local files.

Quick Start

Use the pfSyncPull command to pull the cloud plan into PROJECT_PLAN.md. Example:

  • /pfSyncPull
  • /pfSyncPull --force

Frequently Asked Questions about pfSyncPull

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

FAQPage Schema
How do I sync a cloud plan to my local PROJECT_PLAN.md file?

To sync a cloud plan to your local PROJECT_PLAN.md, use the pfSyncPull command to fetch the latest plan from the PlanFlow API and safely write it to your local file.

How does diff detection work when pulling a cloud plan to a local markdown file?

Diff detection works by comparing the fetched PlanFlow cloud plan with your local PROJECT_PLAN.md, presenting the differences to you before performing a safe write-back to the file.

What prerequisites do I need to pull a plan from PlanFlow cloud to local?

You need valid authentication and established project linkage configured before pulling a plan from PlanFlow cloud, as the command validates these prerequisites before executing the GET request.

Can I force the synchronization of a PlanFlow cloud plan to overwrite local files?

Yes, you can force the synchronization of a PlanFlow cloud plan to overwrite local files by passing the --force argument to bypass standard diff generation and proceed with safe write-back.

Why is my PlanFlow cloud plan pull not writing to the local file?

A PlanFlow cloud plan pull may not write to the local file if authentication fails, project linkage is invalid, or prerequisites are unmet, as the workflow enforces validation before write-back.

What is the best way to keep an offline copy of a cloud project plan for versioning?

The best way to keep an offline copy of a cloud project plan for versioning is to pull the latest PlanFlow cloud plan into your local PROJECT_PLAN.md using a CLI-driven synchronization workflow.