forge-pipeline-sync

Detects relevant workspace changes and updates corresponding entries in Forge Pipeline.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/harkers/forge-email-server --skill forge-pipeline-sync
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: forge-pipeline-sync
Source: https://github.com/harkers/forge-email-server/tree/main/skills/forge-pipeline-sync
Command: npx skills add https://github.com/harkers/forge-email-server --skill forge-pipeline-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Forge Pipeline is the central portfolio, planning, and visibility layer for Forge work. When meaningful workspace changes occur, this skill ensures those changes are propagated back into Forge Pipeline to maintain up-to-date visibility of projects and roadmaps.

Core Features & Use Cases

  • Identifies meaningful changes across workspaces (new workspaces, new products/projects, updated architecture/specs/reviews/roadmaps, deployment state changes, or milestone updates) and records them in Forge Pipeline.
  • Guides users to create or update Forge Pipeline entries with updated notes, timestamps, statuses, and next steps, preserving context such as location, decisions, and remaining work.
  • Establishes a standard local rule for new workspaces to document the Forge Pipeline update process.

Quick Start

Update Forge Pipeline entries for the current workspace with the latest changes.

Frequently Asked Questions about forge-pipeline-sync

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

FAQPage Schema
How do I update Forge Pipeline when workspace changes occur?

Propagate workspace changes to Forge Pipeline by recording updated project entries with notes, timestamps, statuses, and next steps. This maintains accurate portfolio visibility across new products, architecture updates, and deployment state changes.

What workspace changes require a Forge Pipeline update?

Forge Pipeline updates are required when creating new workspaces, identifying new products or projects, updating architecture, specs, reviews, or roadmaps, and documenting deployment state changes or milestone updates to reflect work progress.

How do I document project updates to keep portfolio visibility accurate?

Record updated project entries in Forge Pipeline with notes, updated timestamps, statuses, and next steps. This preserves context such as location, decisions, and remaining work, reflecting that work is complete or progressing for accurate portfolio visibility.

Can I sync roadmap and architecture updates to Forge Pipeline automatically?

Yes, sync roadmap and architecture updates by propagating meaningful workspace changes to Forge Pipeline. Guide the creation or update of entries with updated notes, timestamps, statuses, and next steps to reflect that work is complete or progressing.

What is the best way to maintain project visibility across multiple workspaces?

Establish a standard local rule for new workspaces to document the Forge Pipeline update process. Propagating meaningful changes back to the central portfolio and planning layer ensures consistent project and roadmap visibility.

Why does my Forge Pipeline portfolio show outdated project statuses?

Your Forge Pipeline portfolio shows outdated project statuses because meaningful workspace changes were not propagated back. Record updated project entries with current timestamps, statuses, and next steps to reflect that work is complete or progressing.