orchestrate-github-project

What it does and when to use it

Reconcile committed elixpoo squad receipts into an issue-backed GitHub Project V2 operations view. Use when creating or updating lifecycle items, provisioning agent-specific fields, enforcing run-ID freshness, recovering missed transitions, or producing sanitized operational status without an external database.

How it works

1. Build a snapshot
2. Reconcile safely
3. Recover

---
name: orchestrate-github-project
description: Reconcile committed elixpoo squad receipts into an issue-backed GitHub Project V2 operations view. Use when creating or updating lifecycle items, provisioning agent-specific fields, enforcing run-ID freshness, recovering missed transitions, or producing sanitized operational status without an external database.
---

# Orchestrate the GitHub Project

Use the original public GitHub issue as the Project item. Key every transition as
`owner/repository#issue`; never create duplicate draft items for the same work.

## Build a snapshot

1. Load the committed ledger and current versioned squad receipts.
2. Resolve the original issue through GitHub and require its node ID.
3. Derive one status and current squad from authoritative receipts.
4. Include only branch and PR URLs, timestamps, token totals, Doctor warning, and
   cleanup status. Exclude source, prompts, comments, transcripts, and secrets.
5. Use GitHub terminal state and the ledger for merged or closed work.

## Reconcile safely

- Resolve the configured user or organization Project by number.
- Provision only missing agent-specific fields. Fail when a same-named field has
  an incompatible type; never rewrite human fields.
- Add the external issue with `addProjectV2ItemById` only when it is absent.
- Update only values that changed.
- Reject a different run ID when its timestamp is not newer than the stored item.
- Isolate per-item failures and emit a bounded versioned receipt.

## Recover

Reconcile after state-writing workflows and on a low-frequency schedule. Treat the
scheduled pass as recovery for missed webhooks or dispatches. Replaying the same
snapshot must be harmless.

Do not create a database, publish private metadata, delete Project items, archive
history automatically, or let one malformed ledger record block other items.

Versions

The database has no other skills named orchestrate-github-project.

Database snapshot: 13.11.2026 · package version 4a80904bcc7a (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

• 100github-project-setup
  Configure github project setup operations. Auto-activating skill for Enterprise Workflows. Triggers on: github project setup, github project setup Part of the Enterprise Workflows skill category. Use when working with github project setup functionality. Trigger with phrases like…
• 100projman
  Project management skill for markdown-based projects with GitHub Project sync. Use when: (1) viewing/managing projects in projects/ folder, (2) syncing project checkboxes to GitHub Projects, (3) picking up next work item from a project, (4) updating project status after…
• 100project-docs
  Use whenever creating or updating features, agent tasks, issues, reports or decisions in this project, or changing their status. Defines locations, file naming, numbering, required frontmatter, allowed status transitions, and how agent tasks relate to the team tracker; new…
• 100manage-project
  Keep the organizzolini/codebase GitHub Project board filled in — set an issue's Status, Priority, and Effort, move work to In Progress, and know when a milestone applies. Use when starting or finishing work on an issue, after filing or sorting issues, when estimating effort or…
• 100github-guide
  Use when managing GitHub tickets, Projects kanban, pull-request delivery/review, durable issue or PR context comments, or native CI/repository enforcement on github.com or GitHub Enterprise Server. Triggers on GitHub issues, issue relationships, `gh issue`, Projects v2…