Prose Draft
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
Install
npx skills add danybgoode/golden-frijoles --skill prose-draftgit clone --depth 1 https://github.com/danybgoode/golden-frijoles.git /tmp/golden-frijoles
mkdir -p ~/.claude/skills
cp -r /tmp/golden-frijoles/.claude/skills/prose-draft ~/.claude/skills/prose-draftPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# prose-draft — delegated first drafts for file-derived close-out prose
> **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.
## The contract (why this is safe to delegate)
- **File-derived inputs only.** The tool reads the epic directory's `*.md` + `git log --oneline`
for that path. Artifacts whose real source is the builder's in-head context (PR bodies,Details
- Skill name
prose-draft- Repository
- danybgoode/golden-frijoles
- Path
.claude/skills/prose-draft/SKILL.md- Repo updated
- 17 November 2026
- Listed in
- karanb192/awesome-claude-skills
FAQ
What does the Prose Draft skill do?
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
How do I install the Prose Draft skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add danybgoode/golden-frijoles --skill prose-draft. 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
Build Order Sync
danybgoode/golden-frijoles
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.
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.
Setup
danybgoode/golden-frijoles
The front door for a stranger's agent that just installed this plugin. Use whenever the golden-frijoles plugin is freshly installed, or when a session isn't sure which of its five skills to reach for. Detects state with commands, never guesses (is Roadmap/ present, is frijoles linked, is the kit reachable, which install channel is this), offers `frijoles-kit init` to adopt a bare repo, and routes by job to refine / strategy / report / smoke / frijoles. States plainly what the `npx skills` channel lacks (no build-view hook, no verifier agent) instead of pretending it has parity with the Claude
When Not to Orchestrate
PapiScholz/symphony
Use when about to fan work out to parallel agents, when a user asks to "throw this at a bunch of agents" or parallelize for speed, and before splitting a refactor, rename, migration, or sweep across subagents. Also use when a delegated batch produced inconsistent or conflicting edits, or when deciding whether a task is worth delegating at all rather than doing it in one pass.
Agents Md Audit
agentkitco/agentkit-dev-skills
Audit an AGENTS.md, CLAUDE.md, Cursor rule or Copilot instructions file for stale commands, broken paths, vague rules, secrets and contradictions. Use to review or trim agent instructions.
Browse the most popular Claude skills, all ai, llms & agents skills, or write your own with the skills generator.