Build Order Sync

Regenerates Roadmap/00-ideas/BUILD-ORDER.md when it has drifted from the SSOT (each epic README's frontmatter status:) and opens a claude/ docs PR with the fix — never hand-edits the board. Use when the product owner asks to "sync the build order", "regenerate BUILD-ORDER.md", "check board drift", "is the build-order board stale", "open a build-order PR", or as the nightly ops routine's first step. Runs scripts/build-order-sync.mjs, which does the check, the regen, and (on real drift) the branch/commit/ push/PR — this skill just invokes it and reports the result.

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add danybgoode/golden-frijoles --skill build-order-sync
Manual install
git clone --depth 1 https://github.com/danybgoode/golden-frijoles.git /tmp/golden-frijoles
mkdir -p ~/.claude/skills
cp -r /tmp/golden-frijoles/.claude/skills/build-order-sync ~/.claude/skills/build-order-sync

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# build-order-sync — keep the generated board honest

> **Running this skill's scripts.** Each `node scripts/<name>.mjs <args>` below means, from the project root:
> `if [ -f scripts/<name>.mjs ]; then node scripts/<name>.mjs <args>; else npx -y @golden-frijoles/kit@0.45.0 <name> <args>; fi`
> The project's own copy always wins. The kit needs no install and copies nothing into the repo. If npx fails on
> the network or the registry (ENOTFOUND, ECONNREFUSED, ETIMEDOUT, E404, a proxy error), report **could not
> look: the kit is unreachable**, not a broken project, and offer to retry online or to copy the script into
> `scripts/`. This covers the scripts the kit carries (`frijoles-kit --list`). Any other `scripts/` command here is
> project tooling: if the project lacks it, say so and stop. Never re-implement a script's logic inline.
> If a script prints `GF-NEEDS-SETTING {"key",…}`, ask the user that question once, save the answer with
> `npx -y @golden-frijoles/kit@0.45.0 config set <key> <value>` (always the kit, never local-wins: a project
> may own an unrelated `scripts/config.mjs`), tell them they can change it later the same way, and run the
> script again if it exited 7.

> This skill never hand-edits `Roadmap/00-ideas/BUILD-ORDER.md`. Its only writes are: regenerating that
> one file (via the existing generator) and, only on real drift, a `claude/`-branch docs PR containing
> just that regenerated file.

## When to run me
Read the full skill on GitHub

Details

Skill name
build-order-sync
Path
.claude/skills/build-order-sync/SKILL.md
Repo updated
17 November 2026

FAQ

What does the Build Order Sync skill do?

Regenerates Roadmap/00-ideas/BUILD-ORDER.md when it has drifted from the SSOT (each epic README's frontmatter status:) and opens a claude/ docs PR with the fix — never hand-edits the board. Use when the product owner asks to "sync the build order", "regenerate BUILD-ORDER.md", "check board drift", "is the build-order board stale", "open a build-order PR", or as the nightly ops routine's first step. Runs scripts/build-order-sync.mjs, which does the check, the regen, and (on real drift) the branch/commit/ push/PR — this skill just invokes it and reports the result.

How do I install the Build Order Sync skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add danybgoode/golden-frijoles --skill build-order-sync. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Related skills

Babysit PR

danybgoode/golden-frijoles

Advisory PR watch for a single open PR — retries flaky CI (re-runs failed workflow runs) and surfaces merge conflicts via one comment; never merges, never a required check. Use when the product owner asks to "babysit this PR", "check on open PRs", "retry flaky CI", "is this PR stuck", "why isn't this PR moving", or as the nightly ops routine's third step (once per open PR across the project's repos). Runs scripts/babysit-pr.mjs, which does the gh reads, the retry, and the comment post. A clean PR (no conflict, no failing checks) gets NO comment — this tool never adds nightly noise to a healthy

Git & Code ReviewIn 1 list

Doc Hygiene

danybgoode/golden-frijoles

Keeps the always-read session-start docs (this project's AGENTS.md, Roadmap/WAYS-OF-WORKING.md, Roadmap/LEARNINGS.md, Roadmap/README.md poster) from re-bloating after the one-time de-noise sweep. Use when the product owner asks to "check doc hygiene", "measure LEARNINGS size", "is LEARNINGS bloated again", "run the doc hygiene report", or as the weekly Routine C hygiene pass. Runs scripts/doc-hygiene.mjs, reviews its flagged candidates against the source docs, and emits a dated advisory report. Never edits Roadmap docs — proposals only, the product owner or the builder hand-merges.

Writing & ContentIn 1 list

Prose Draft

danybgoode/golden-frijoles

First-draft internal close-out prose (retrospectives, product-poster entries, sprint-wrap summaries) by delegating to a cheap different-family model via the cross-agent rail. Use at sprint/epic close, or when the product owner asks to "draft the retro", "draft the poster entry", "write the sprint wrap". Runs scripts/prose-draft.mjs, which gathers the epic's own docs + git log, applies the house-voice prompt, and prints an advisory draft to stdout. The draft is NEVER committed as-is — the coordinating agent edits it for factual accuracy first (drafts invent plausible-sounding gaps; the output b

AI, LLMs & AgentsIn 1 list

Report

danybgoode/golden-frijoles

Posts a project report to a chat destination, at the cadence asked for. Daily: a delta-only standup of overnight signals across every repo the project spans (opened/merged PRs and CI, the latest browser smoke, BUILD-ORDER drift, open-PR state, stale previews). Weekly: an executive recap/retro (merged PRs, shipped epics, deploys per app repo, a retro digest). PMO: the weekly operational report with scrum/DORA/doc-ops metrics and a story deck, or the on-demand monthly stakeholder packet with a metrics sheet. Use when the product owner asks to "post the standup", "run the daily standup", "what ha

Git & Code ReviewIn 1 list

Brag Doc From Git

agentkitco/agentkit-dev-skills

Build an evidence-based brag doc or self-review draft from your merged PRs and commits, leaving visible gaps where results are unknown. Use for review season, promotion cases or resumes.

Git & Code ReviewIn 1 list

Generating Smart Commits

jeremylongshore/claude-code-plugins-plus-skills

This skill generates conventional commit messages using AI analysis of staged Git changes. It automatically determines the commit type (feat, fix, docs, etc.), identifies breaking changes, and formats the message according to conventional commit standards. Use this when asked to create a commit message, write a Git commit, or when the user uses the `/commit-smart` or `/gc` command. It is especially useful after changes have been staged with `git add`.

Git & Code Review

Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.