bf-status skillB
bf-status is agent-read markdown (skill) from chan4lk/specclaw: Show where a brownfield rebuild actually stands — one row per bf-* phase (analyze, architecture, domain, clarify, ui, baseline, rebuild-plan, blueprint, bootstrap, replay), what each produced, every open item holding a phase back, and the single next command to run. The bf-* counterpart to /specclaw:status, which reports the propose→plan→build→verify lifecycle and says nothing about the rebuild workstream. Read-only and deterministic — spawns no agent, reads no source code, and writes nothing at.
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# specclaw bf-status **First, run** `specclaw-ensure-init .specclaw` — idempotently creates `.specclaw/` if it doesn't exist (silent if already initialized; auto-inits using the current directory's basename as the project name). Show where the brownfield workstream stands. Read-only side-command — no `specclaw-validate-change` call, no `<change>` involved, matching the `status`/`patterns`/`bf-analyze` pattern. 1. **Compute and render:** ```bash specclaw-bf-status .specclaw ``` Deterministic, read-only, cheap. Everything it reports is recomputed from each phase's own declared artifacts on every run. **If it exits non-zero, surface its stderr message verbatim and stop** — the only failures are a missing `<specclaw_dir>` (run `/specclaw:init`) and a missing argument. Don't retry, don't guess a different path. 2. **Relay its output to the user.** It is already a finished markdown report — a phase table, a **Needs attention** list, and a **Next** line. Present it as-is rather than paraphrasing it into prose. The attention list in particular is a work list someone can act on today; summarising it away is exactly the failure this command exists to fix. …
Read the whole file at its exact version.
How to install
mdr add chan4lk/specclaw/bf-status@git:20260904.c65816amdr add chan4lk/specclaw/bf-status@sha256:2810077185014bbePin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_bbbwma2nqqsyqzmk)
1 badge views in 30 days
Versions
Audit of the latest version
- fail: Frontmatter declares a name
- pass: Frontmatter block present
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (6200 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
chan4lk/specclaw · 12 stars · license MIT · pushed 2026-09-22 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_bbbwma2nqqsyqzmk GET https://markdownregistry.com/api/v1/resolve?ref=chan4lk/specclaw/bf-status GET https://markdownregistry.com/api/v1/blob/2810077185014bbe8e4561eb1c9794eaa2a90b4205f815abcdd17eccac072869
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.