businesslisted

Creates, maintains and audits BUSINESS.md — the project's business context (why it exists, for whom, its value, scope and non-goals). Works like /init, but for BUSINESS.md: it first establishes the project's ARCHETYPE (library / CLI / service / data-pipeline / AI-system / local-app), which selects a tailored template and a focused question set. Three modes: bootstrap (write the file in a new project), update (reconcile it against the project's state), and `audit` (check reality — code, commits, diff — against the declared non-goals and scope, read-only; in a project that did not install /compliance it also inherits the shared ladder's fallback row for regulated ground). Bootstrap and update end by making the compliance call — whether this project needs COMPLIANCE.md at all. Generic — usable in any project. Do NOT use it for live status (that belongs in PROGRESS.md) or for rules/conventions (they belong in CLAUDE.md).
radozaprazny/attest · ★ 0 · Data & Documents · score 69

Install: claude install-skill radozaprazny/attest

# /business — business context + archetype (BUSINESS.md) This skill maintains **`BUSINESS.md`** — the document about **why the project exists**. It changes rarely. It works much like `/init` (which creates `CLAUDE.md`), but focuses purely on business context, and it opens by establishing the project's **archetype** so the questions it asks and the template it writes fit the *kind* of software in front of it. The skill is **generic** — work with what you actually find in the repo, and assume nothing about the specific project. ## The control documents — keep them separate **Anti-duplication:** status → `PROGRESS.md` · rules → `CLAUDE.md` · why-it-exists → `BUSINESS.md` · why-we-chose-X-over-Y → `DECISIONS.md` · under-what-rules → `COMPLIANCE.md`. Write each fact in exactly one place. (full table: GUIDE PART 1) > This skill only maintains `BUSINESS.md`; treat the others as sources of context if they > exist. If you catch yourself writing current status ("done", "running", "6 tests green") or > a technical rule (language version, commit style) into `BUSINESS.md` — it belongs elsewhere, > leave it out. A specific choice and *why it beat the alternative* is a `DECISIONS.md` entry, > not a non-goal. ## The archetype Before writing anything, decide **what kind of software this is**. The archetype is a lightweight label — not a legal judgement. It does two jobs: it picks the right questions and template below, and it is recorded as one line in `BUSINESS.md` as a **trigger** fo