Orchestrate upstream loom bead workflows with issue-only or issue+pr lanes.
npx skills add https://github.com/fkberthold/loom --skill upstream-a-bead
Please help me install this Agent Skill. Skill: upstream-a-bead Source: https://github.com/fkberthold/loom/tree/main/skills/upstream-a-bead Command: npx skills add https://github.com/fkberthold/loom --skill upstream-a-bead
This skill owns the upstream-specific middle of the loom bead lifecycle, bridging loom's local work with upstream contribution activities by handling clone, test, draft artifacts, and watch-bead orchestration. It defers to the bead-lifecycle-shell for core lifecycle actions (claim/isolate/verify/close/capture) and provides two lanes (--issue-only and --issue+pr) to handle filing upstream issues or PRs.
Start an upstream bead workflow for a specific bead by saying 'let's work upstream-a-bead <bead-id>' and then proceed with the guidance.
High-intent search queries and answers about installing and using this skill.
The upstream workflow handles PR privacy redaction at the M6 stage gate during the issue+pr lane. It ensures sensitive data is scrubbed before drafting artifacts and filing the upstream contribution.
A bead lifecycle transition moves upstream work through 7 stages: designing, cloning, red, green, draft, review, and file. The workflow records stage markers in workflow-state to enable cold-start recovery and coordinates lane selection for issue or PR contributions.
Start an upstream bead workflow by triggering the skill with a specific bead ID and proceeding with the guided steps. It handles canonical-owner checks, lane selection between issue-only and issue+PR, and coordinates cloning through PR filing automatically.
Upstream workflows support an issue-only lane that handles filing upstream issues independently of pull requests. The alternative issue+pr lane handles upstream cloning, RED/GREEN testing, and PR drafting, allowing lane selection based on contribution scope.
Upstream PR automation defers core lifecycle actions like claim, isolate, verify, close, and capture to the bead-lifecycle-shell. It specifically owns the upstream-specific middle between design and verification, meaning it does not handle the full lifecycle independently.
fkbertholdCoordinate feature-bead work with contract-driven variable middle and lifecycle scaffolding.
fkbertholdCoordinate M1 through M6 stages for bug-shaped bead fixes.
connor-git-yamlCoordinate ten-phase Spec-Driven Development workflows with Claude Code Task tools.
amadeus-dlcRuns the environment-provisioning stage in isolation without advancing the main workflow.
