using-specclaw SKILL.md skillB

using-specclaw 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/using-specclaw@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/skills/using-specclaw/SKILL.md
Versions recorded
3
Latest version
git:20261012.6b78134, committed Oct 12, 2026
First version recorded
Sep 18, 2026
Size
4,415 bytes
Repository stars
14
License
MIT

Use when a session starts in a repo that has a .specclaw/ directory — establishes how specclaw verbs are chosen.

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

# Using specclaw

specclaw is a spec-driven change lifecycle. Every change gets a directory under
`.specclaw/changes/<NNN>-<slug>/` holding its proposal, spec, tasks, errors and learnings — **that
directory is the paper trail, and it only exists if the lifecycle created it.**

Lifecycle: `propose → plan → build → verify → pr → archive`.

## The one hard gate: new work MUST be proposed

If the user asks to add, build, create, implement, change, extend, remove or "just quickly" alter
**anything in this codebase** — a feature, a flag, a file, a config value, a one-line fix — and there
is even a 1% chance it is new work rather than a question, you MUST invoke `/specclaw:propose` before
reading, editing or creating any source file.

This is not negotiable. You cannot rationalise your way out of it. *"It's too small"*, *"I'll propose
it after"*, *"they seem in a hurry"*, *"I'm just looking first"* — all of these mean STOP and invoke
`/specclaw:propose`.

The gate is forcing because this is the **only route with no recovery path**. A change that begins
without a proposal has no change dir, and no later verb can create one retroactively: the trail is
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint
mdr add chan4lk/specclaw/using-specclaw@sha256:5bbe203e611ca9d6

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 badge

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

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

Versions

The registry has recorded 3 versions of this file, between Sep 18, 2026 and Oct 12, 2026, about one every 12 days.

versioncommittedcommitsizeaudit
git:20261012.6b78134 latest2026-10-12 6b78134 4,415 BB view · diff
git:20261011.f9682692026-10-11 f968269 4,245 BB view · diff
git:20260918.c4abb6b2026-09-18 c4abb6b 4,231 BB 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 (4415 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 · 14 stars · license MIT · pushed 2026-11-08 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_253th47vu5a2gybv
GET https://markdownregistry.com/api/v1/resolve?ref=chan4lk/specclaw/using-specclaw
GET https://markdownregistry.com/api/v1/blob/5bbe203e611ca9d65e3efc11d220216e84957d135a853a33a7f3007dd1405251

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 · 14 stars
CLAUDE.md CLAUDE.md file
chan4lk/specclaw · CLAUDE.md
git:20261029.e7b3be8 · audit A · 14 stars
llms-full.txt@docs llms.txt file
chan4lk/specclaw · docs/llms-full.txt
git:20261011.f968269 · audit A · 14 stars
llms.txt@docs llms.txt file
chan4lk/specclaw · docs/llms.txt
git:20260717.fc3814b · audit A · 14 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.
git:20261012.6b78134 · audit B · 14 stars
bf-architecture SKILL.md skill
chan4lk/specclaw · plugins/specclaw-bf/skills/bf-architecture/SKILL.md · Use when a legacy codebase needs a C4 architecture view before a rebuild.
git:20261012.6b78134 · audit B · 14 stars
bf-baseline SKILL.md skill
chan4lk/specclaw · plugins/specclaw-bf/skills/bf-baseline/SKILL.md · Use when a rebuild needs golden-master seams, scenarios and a capture harness from the legacy app.
git:20261012.6b78134 · audit B · 14 stars
bf-blueprint SKILL.md skill
chan4lk/specclaw · plugins/specclaw-bf/skills/bf-blueprint/SKILL.md · Use when a rebuild's decisions and backlog exist and the target architecture must be drawn.
git:20261012.6b78134 · audit B · 14 stars
bf-bootstrap SKILL.md skill
chan4lk/specclaw · plugins/specclaw-bf/skills/bf-bootstrap/SKILL.md · Use when a rebuild backlog exists but the new repo has no application foundation yet.
git:20261012.6b78134 · audit B · 14 stars
bf-clarify SKILL.md skill
chan4lk/specclaw · plugins/specclaw-bf/skills/bf-clarify/SKILL.md · Use when brownfield analysis has open inferences or gaps that need human answers.
git:20261012.6b78134 · audit B · 14 stars
bf-domain SKILL.md skill
chan4lk/specclaw · plugins/specclaw-bf/skills/bf-domain/SKILL.md · Use when a legacy codebase needs its domain model, functional spec and module map.
git:20261012.6b78134 · audit B · 14 stars
bf-e2e SKILL.md skill
chan4lk/specclaw · plugins/specclaw-bf/skills/bf-e2e/SKILL.md · Use when an application needs runnable end-to-end tests that assert its own business behaviour.
git:20261012.6b78134 · audit B · 14 stars

Every file in chan4lk/specclaw

Browse by kind, by grade B, or by owner.