bf-blueprint SKILL.md skillB

bf-blueprint from chan4lk/specclaw is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned

mdr add chan4lk/specclaw/bf-blueprint@git:20261012.6b78134

Pins git:20261012.6b78134 in mdr.lock. Pin the fingerprint instead.

Audit grade: B, 16 of 17 checks passed
Kind: SKILL.md skill
Repository: chan4lk/specclaw
Path: plugins/specclaw-bf/skills/bf-blueprint/SKILL.md
Versions recorded: 2
Latest version: git:20261012.6b78134, committed Oct 12, 2026
First version recorded: Oct 11, 2026
Size: 10,473 bytes
Repository stars: 13
License: MIT

Use when a rebuild's decisions and backlog exist and the target architecture must be drawn.

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# specclaw bf-blueprint

**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).

Write `.specclaw/analysis/target-architecture.md`: the **target** architecture of a brownfield rebuild, synthesised from decisions already recorded. Read-only side-command — no `specclaw-validate-change` call, no `<change>` involved, matching the `analyze`/`architecture`/`domain`/`clarify`/`rebuild-plan` pattern.

**Why this command exists.** The pipeline was asymmetric. The legacy side had `architecture.md`, `domain-model.md` and `module-map.md`; the target side had its architecture scattered across `decisions.md`, ADRs, `bootstrap-plan.md` and the backlog — nothing that showed the shape of the thing being built, and nothing anyone could put in front of a client.
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint

mdr add chan4lk/specclaw/bf-blueprint@sha256:e9754f5e428acc3f

The line at the top of this page pins the label git:20261012.6b78134, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.

Badge

[![mdr](https://markdownregistry.com/badge/art_au3hpcptlptngerw.svg)](https://markdownregistry.com/a/art_au3hpcptlptngerw)

2 badge image fetches in 30 days. What the badge shows.

Versions

The registry has recorded 2 versions of this file, between Oct 11, 2026 and Oct 12, 2026, more than one a day.

version	committed	commit	size	audit
git:20261012.6b78134 latest	2026-10-12	6b78134	10,473 B	B	view · diff
git:20261011.e9430eb	2026-10-11	e9430eb	11,528 B	B	view

Audit of the latest version

B 16 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.

fail: Frontmatter declares a name
pass: Frontmatter block present
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (10473 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

Starting a new one? Use a template for SKILL.md on mdpantry, which passes every one of these checks and says what to change in it.

Source

GitHub

chan4lk/specclaw · 13 stars · license MIT · pushed 2026-10-20 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_au3hpcptlptngerw
GET https://markdownregistry.com/api/v1/resolve?ref=chan4lk/specclaw/bf-blueprint
GET https://markdownregistry.com/api/v1/blob/e9754f5e428acc3f802240b589d07d1a6f5969a301cf6c65b7c7aa87e00778f1

Your AI assistant 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.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from chan4lk/specclaw

specclaw SKILL.md skill

chan4lk/specclaw · .agents/skills/specclaw/SKILL.md · Run the SpecClaw spec-driven lifecycle in this repository when a request needs proposal, planning, build, verification…

git:20261011.f968269 · audit A · 13 stars

CLAUDE.md CLAUDE.md file

chan4lk/specclaw · CLAUDE.md

git:20260918.26bbfe4 · audit A · 13 stars

llms-full.txt@docs llms.txt file

chan4lk/specclaw · docs/llms-full.txt

git:20261011.f968269 · audit A · 13 stars

llms.txt@docs llms.txt file

chan4lk/specclaw · docs/llms.txt

git:20260717.fc3814b · audit A · 13 stars

bf-analyze SKILL.md skill

chan4lk/specclaw · plugins/specclaw-bf/skills/bf-analyze/SKILL.md · Use when onboarding to an existing or legacy codebase that needs a grounded stack, dependency and risk report.