project-sync

Synchronize project state across Linear and GSD after explicit user confirmation.

Updated Mar 1, 2026
One-click install
npx skills add https://github.com/gerardloupecyb/claude-code-project-template --skill project-sync-gerardloupecyb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-sync
Source: https://github.com/gerardloupecyb/claude-code-project-template/tree/main/.claude/skills/project-sync
Command: npx skills add https://github.com/gerardloupecyb/claude-code-project-template --skill project-sync-gerardloupecyb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Synchronize project state across external tools (Linear and GSD) while enforcing explicit user confirmation before any write.

Core Features & Use Cases

  • Read and validate integration settings from .claude/integrations.md to determine which tools are active.
  • Coordinate with Linear to close issues, move tasks, and align milestones; read memory/MEMORY.md for context and next steps.
  • Provide advisory prompts and require explicit user confirmation before performing any actions; read STATE.md to surface current phase and plan.

Quick Start

Initiate a sync with /project-sync to align your project state across tools using the current integrations and memory.

Frequently Asked Questions about project-sync

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

FAQPage Schema
How do I synchronize project state across Linear and other task tracking tools?

Project state synchronization across Linear and GSD coordinates issue closure, task updates, and next-step planning. It reads local memory and integration settings to align milestones across active tools while requiring explicit user confirmation before writing changes.

How does issue closure automation work with external project management tools?

Issue closure automation works by reading memory and STATE.md to surface the current phase and plan, then coordinating with Linear to close issues and move tasks. Advisory prompts require explicit user confirmation before performing any actions.

Do I need specific configuration files to sync tasks between Linear and GSD?

Yes, task syncing requires .claude/integrations.md to determine active tools, memory/MEMORY.md for context, and STATE.md to surface current plans. The synchronization validates required IDs from these files before executing any updates.

Can I use project state synchronization without explicit user confirmation before writes?

No, project state synchronization enforces explicit user confirmation before performing any write actions. Advisory prompts ensure users validate issue closure, task updates, and milestone alignment across Linear and GSD before changes are committed.

What is the best way to align milestones and next steps across multiple project tools?

The best way to align milestones is initiating a sync to coordinate issue closure and task updates across Linear and GSD. It reads local memory and integration settings to drive next-step planning while validating required IDs.

Why does my project sync require validating IDs before updating tasks in Linear?

Project sync requires validating IDs to ensure accurate task updates and issue closure across Linear and GSD. It reads .claude/integrations.md and memory files to confirm active tools and prevent invalid state synchronization writes.