add-bead
FreeCapture free-text work as a tracked Beads issue. Use when the user runs /add-bead or wants to quickly file a Beads issue.
The English summary is being prepared. Showing the original description.
Trimmed Forge pipeline (scope → build → wrap) for small, clear-scope work. Use when the user runs /forgemaster-mini or has a small, well-scoped task.
The English summary is being prepared. Showing the original description.
Review the instructions the agent will receive before you install.
Run the low-ceremony Forge path for small, clear-scope work (bugs, chores, config, single-file changes). Same Beads + TDD discipline as the full pipeline, but collapsed into three lightweight steps — scope → build → wrap — with far fewer turns, gates, and artifacts to keep cost down.
Use this directly when you already know the task is small. For anything medium-or-higher, use
/forgemaster (which can also auto-route here).
Accepts the same inputs as /forgemaster — a JIRA ticket, a Beads issue id, or a
free-text description.
/forgemaster-mini <task description> # free text
/forgemaster-mini <BEADS-ID> # e.g. agent-forge-harness-f25 → run mini against that issue
/forgemaster-mini <JIRA-KEY> # e.g. PROJ-1234 → mirror into Beads, then run mini
/forgemaster-mini <task> --smith <name> # also record the run, as built by a configured smith
Follow .claude/workflows/forge-mini.md in full. In short:
bd ready >/dev/null; if it errors, bd dolt start and retry. Beads is required.bd show an existing id, mirror a JIRA key into Beads (--external-ref jira-<KEY>,
pasting the ticket if no JIRA integration is configured), or create a new task for free text —
then --claim it (priority via .claude/skills/beads-priority-assignment/SKILL.md). Confirm the
approach once..claude/skills/tdd/SKILL.md (vertical slices) for code; one runnable demo;
worklog: comment; commit with tests.bd dolt push),
and report inline: what changed, how to verify, Beads id + PR link.No plans/ or reports/ doc files and no forge:phase-gate / run state file, unless it was given
--smith — tracking lives in Beads. Escalate to the full pipeline (/forge-research <slug>) if
the work outgrows "mini".
--smith <name>The mini path keeps no run state, so a --smith is recorded by one write at the very end. Pick a
kebab-case <slug> for the run, and after the wrap step's push:
reports/<slug>-ship.md.bun run forge:phase-gate ship --slug <slug> --write --bead <task-id> --smith <name>That call checks the name (a smith that is not configured is refused, with the list of the ones that
are: correct it and run the call again; nothing is lost, because this session builds either way),
stores the smith on the run as its executor, and leaves a run that is already shipped, so it never
shows as in flight. --smith does not change the model of the session reading this command. A mini
run has no linked gate entry, with or without --smith: its checks are the bare
bun run typecheck && bun run lint && bun test of the wrap step.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Capture free-text work as a tracked Beads issue. Use when the user runs /add-bead or wants to quickly file a Beads issue.
The English summary is being prepared. Showing the original description.
Register a new sub-repo in the knowledge base.
The English summary is being prepared. Showing the original description.
Add focused Bun unit tests for mission-critical behavior and edge cases — not blanket coverage.
The English summary is being prepared. Showing the original description.
Answer questions about the codebase from knowledge files. Use when the user runs /ask or asks a domain/knowledge question about the repos.
The English summary is being prepared. Showing the original description.
Meta-skill for creating Agent Forge skills under .claude/skills/ with SKILL.md, optional references/ and scripts/, and Bun scaffolds. Use when the user wants to add or author a skill, scaffold a new skill folder, or align skill docs with harness conventions (JSON script output, Beads for tasks).
The English summary is being prepared. Showing the original description.
Choose Beads issue priority (P0–P4, numeric, or named) from urgency, impact, and risk when creating or triaging work.
The English summary is being prepared. Showing the original description.