forge-pipeline-operator-agent

Update Forge Pipeline project entries, statuses, milestones, and notes.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates keeping Forge Pipeline's project state in sync with actual work by reflecting workspace, plan, milestone, and state changes into Forge Pipeline.

Core Features & Use Cases

  • create or update project entries
  • reflect meaningful workspace changes into project notes
  • adjust status, milestones, and follow-up tasks
  • keep project visibility aligned with actual work
  • boundary: This role reflects state into Forge Pipeline. It does not own portfolio strategy or workspace governance design. Hand those to:
  • portfolio-planning-agent for roadmap/priority shaping
  • workspace-governor-agent for workspace-local process changes
  • Reference: Read ../forge-pipeline-sync/SKILL.md and references/examples.md for update patterns.

Quick Start

Activate the Forge Pipeline Operator Agent to reflect the latest project-state changes in Forge Pipeline.

Frequently Asked Questions about forge-pipeline-operator-agent

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

FAQPage Schema
How do I keep Forge Pipeline project state in sync with actual work?

To keep Forge Pipeline project state in sync, you can automate reflecting workspace, plan, milestone, and state changes by updating project records, statuses, milestones, and notes automatically.

What is the best way to automate updating project milestones and notes in Forge Pipeline?

Automating project milestone and note updates in Forge Pipeline involves reflecting meaningful workspace changes into concise project notes while adjusting statuses and generating follow-up tasks to align visibility with actual progress.

Does the Forge Pipeline state reflection process generate follow-up tasks automatically?

Yes, Forge Pipeline state reflection generates follow-up tasks automatically. It adjusts project statuses, milestones, and creates concise notes to ensure project visibility stays aligned with actual work.

Can I use this automation to update project entries based on architecture pack changes?

Yes, you can update project entries based on architecture pack changes. The automation applies when specs, implementation milestones, or project-state changes require reflection back into Forge Pipeline records.

When should I not use Forge Pipeline state reflection for project management?

You should not use Forge Pipeline state reflection for portfolio strategy or workspace governance design. Those tasks require separate handlers for roadmap priority shaping and workspace-local process changes.

Why does my Forge Pipeline project visibility not match actual workspace progress?

Forge Pipeline project visibility mismatches actual workspace progress when state changes are not reflected. Automating the synchronization of records, milestones, and notes resolves this misalignment without manual noise.