armelhbobdad/bmad-module-ultracode-goal / skills/ultracode-goal
ultracode-goal
FlaggedRuns a BMAD Epic autonomously to a machine-checked Definition-of-Done. Use when the user requests to 'run an epic autonomously', 'execute this epic', 'ultracode goal', or 'autonomously deliver the epic'.
customize.toml
View on GitHub# DO NOT EDIT -- overwritten on every update.
# Customization for ultracode-goal.
# Resolved at activation via resolve_customization.py (base -> team -> user).
# Teams/users override in {project-root}/_bmad/custom/ultracode-goal.toml (and .user.toml)
# without editing this file.
[workflow]
activation_steps_prepend = []
activation_steps_append = []
persistent_facts = ["file:{project-root}/**/project-context.md"]
# --- Paths: TEA + BMAD artifacts ---
tea_config_path = "{project-root}/_bmad/tea/config.yaml"
trace_output_dir = "{project-root}/_bmad-output/test-artifacts/traceability"
implementation_artifacts = "{project-root}/_bmad-output/implementation-artifacts"
deferred_work_path = "{project-root}/_bmad-output/implementation-artifacts/deferred-work.md"
# --- Git isolation + guardrails ---
epic_branch_prefix = "ultracode/epic-"
protected_branches = ["main", "master"]
# --- Turn guardrails (runaway-proofing) ---
max_turns_per_story = 25
# DEPRECATED: accepted but no-op. Nothing reads this key any more; the runaway
# bound is turns only, via max_turns_per_story. Kept so existing overrides keep
# resolving without error. Setting it changes nothing.
story_token_budget = 1500000
# DEPRECATED: accepted but no-op. The experimental --parallel fan-out is retired;
# nothing reads this key any more. Kept so existing overrides keep resolving
# without error. Setting it changes nothing.
parallel_max_concurrency = 8
# --- Commands pre-populated to the allowlist before an unattended run ---
# `git rev-parse` and `git diff` are read-only and load-bearing: Execute's step 0 records the
# per-story baseline SHA with `git rev-parse HEAD` before any implementation, and the evidence
# trail bounds a story's commit range from it. Omitting them makes an unattended run stop for a
# permission prompt exactly where walk-away autonomy is claimed.
# `git check-ignore` tells preflight and Execute which run outputs git ignores, and the gate
# measures each story in a worktree it adds and removes with `git worktree`. Each entry becomes
# a `Bash(<entry>:*)` allow rule, which matches only a command that starts with the entry, so
# the stage references call their scripts with `uv run`, never `python3`. A test keeps every
# git and `uv run` command the references prescribe covered by this list.
allowlist_commands = ["git status", "git add", "git commit", "git rev-parse", "git diff", "git check-ignore", "git worktree", "npm test", "npm run lint", "npm run build", "pytest", "uv run", "date"]
# --- Gate backfill sweep (opt-in) ---
# The sweep the gate runs before it commits a test bmad-testarch-automate
# backfilled. "full" (default) = the full three-axis sweep, cache-defeated, as
# Execute's step 5 runs it. "scoped" = when every path the backfill stages is a
# test file (named as its toolchain names one, and mentioned by no other file
# outside the run's own records) and Execute's full step-5 sweep went green at
# the commit the backfill builds on, re-run only the checks of the packages
# that hold those files and every check that reads files across packages or
# git's file list (unless its own declared inputs exclude every staged path),
# and print each check left out. It trusts that earlier full sweep for every
# check it does not re-run, which is why it is opt-in. The tests-ran marker
# keeps scope=full and gains a sweep= line naming both captures. Any other
# backfill runs the full sweep. A scalar: a team or user layer overrides it;
# any value other than "scoped" reads as "full".
backfill_sweep = "full"
# --- Hook fired at epic completion (prompt or shell command); empty = none ---
on_epic_complete = ""
# --- Hook fired when the run escalates (prompt or shell command); empty = none ---
# The opposite terminal to on_epic_complete: that one fires only when the Epic
# advanced, this one only when a story escalated. Fires at most once per run, at
# the first escalation observed, so an operator who walked away hears that the
# run stopped making progress on its own instead of finding out on their return.
on_escalation = ""
# --- Health check (workflow self-improvement; opt-out + autonomy-safe) ---
# The terminal Finalize step reflects on the run and can file genuine workflow
# friction as fingerprint-deduped GitHub issues. Honesty-by-default: zero
# findings is the expected, healthy outcome.
# See https://armelhbobdad.github.io/bmad-module-ultracode-goal/health-check/
# Set health_check_repo = "" to disable the health check entirely; the repo
# doubles as the on/off switch (no target, nothing to run); there is no
# separate enabled toggle. (assets/module.yaml carries a test-pinned mirror of
# this default for BMad-core readers of module.yaml; this file is what the live
# run reads.)
# A repository on a host other than github.com is given as HOST/OWNER/REPO:
# log gh in to that host first, with gh auth login --hostname HOST, HOST in
# lower case and without a leading www.
# To send findings to another repository, create these labels there:
# health-check, workflow-improvement, bug, friction, gap, duplicate and
# possible-duplicate, and copy two files into it unchanged: the issue template,
# https://github.com/armelhbobdad/bmad-module-ultracode-goal/blob/main/.github/ISSUE_TEMPLATE/workflow-health-check.md
# and the dedup Action, which reads its repository from the run,
# https://github.com/armelhbobdad/bmad-module-ultracode-goal/blob/main/.github/workflows/health-check-dedup.yaml
# Without the labels the first create fails and the retry files the issue
# unlabeled; without the Action nothing labels it or closes a duplicate.
# On a host other than github.com the Action runs only once GitHub Actions is
# on there, its runs-on names one of the host's runners, the host can reach
# actions/github-script at the commit the Action pins, and those runners can
# run the Node version that commit's action.yml names in runs.using.
# Such a project must also set its own health_check_seen_cache: the cache keys
# each record by fingerprint alone, so two projects filing to different
# repositories would block or overwrite each other's records. The check only
# keeps another repository's record from suppressing or linking a finding.
health_check_repo = "armelhbobdad/bmad-module-ultracode-goal"
# Deliberately a home-relative `~` path (expanduser semantics, unlike the
# {project-root} brace tokens above): the seen-cache is machine-global because
# dedup must span the projects that file to one repository: the same defect
# met in two of them is still one report. Use `~`, not `$HOME`: health_check_fp.py normalises the path with
# Path.expanduser() only, so a literal `$HOME` survives unexpanded whenever the
# shell does not expand it first and silently writes a `$HOME/` directory under
# the current project, making the dedup per-cwd instead of machine-global.
health_check_seen_cache = "~/.ultracode-goal/health-check-seen.json"
# The folder where findings that stay local are written, one file per finding,
# with a resolved/ subfolder for retired ones; redirect it to share a triage folder.
health_check_queue_path = "{project-root}/_bmad-output/ultracode-goal/improvement-queue"
# In unattended/headless runs there is no human at the [Y]/[A]/[N]/[E]/[Q] gate.
# false (default) = queue findings locally, NEVER live-submit without a human.
# true = additionally live-submit `bug`-severity findings unattended (still
# deduped + seen-cache-guarded). friction/gap never auto-submit.
# It posts only when the four gh calls a submit makes are allowed:
# an unattended run has nobody to approve them, so each is refused
# and the finding queued. Allow them under [workflow] in
# {project-root}/_bmad/custom/ultracode-goal.toml (or .user.toml):
# allowlist_commands = ["gh auth status", "gh issue list", "gh label create", "gh issue create"]
# Arrays append: the list above keeps every command it holds.
# Preflight writes each entry as an allow rule in
# .claude/settings.local.json, where it stays for every later session
# in the project: any agent there can then create issues and labels on
# any repository without asking. To keep them to the health-check
# repository, write "gh issue list --repo <repo>",
# "gh label create --repo <repo>" and "gh issue create --repo <repo>",
# <repo> being health_check_repo. When you turn autosubmit off, drop the
# entries and delete their Bash(gh ...) rules from
# .claude/settings.local.json yourself: preflight only adds rules.
health_check_autosubmit = false
# --- Cross-Session Recall (optional; consults this repo's prior runs) ---
# Advisory only, never gates. Reads and writes the local run store that
# cross_session_recall_store names below, on this machine only. "on" = read
# prior runs at Ingest and write one record per run at Finalize | "off" =
# touch no store. "on" with the store key unset leaves recall off, and the
# run report says so (NOTE recall-store-unset).
cross_session_recall = "off"
# Folder of the local run store (one immutable file per run, per machine). No
# default: "" (or blank, an unresolved {...} token, a literal $VAR or %VAR%, a
# relative path) is unset. Use a `~` path, expanded like health_check_seen_cache,
# for example "~/.ultracode-goal/recall"; an absolute or {project-root} path also
# works, and a store the scripts create ignores itself through its own .gitignore.
cross_session_recall_store = ""
# --- Knowledge-graph refresh (optional; runs at Finalize only) ---
# Advisory only, never gates. Requires the third-party graphify CLI on PATH and
# a prior graphify-out/graph.json to update; silently inactive without either. "off" = never touch it | "refresh" = one incremental,
# time-boxed rebuild as the run exits, so the next session starts from a
# current graph rather than a stale one. Finalize is the only call site: no
# preflight step, no per-story step, and no effect on any gate verdict, the
# recorded run-status, or the headless envelope.
graphify_integration = "off"
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |