Reference
The skills.
INSPIRE ships fifteen agent skills, each invoked as /inspire-<skill> <subcommand>. Seven specify the product, two codify it into production code under source/, and six handle housekeeping — project setup, the surface roster, brownfield onboarding, work tracking, vault-wide review and the lessons catalog. Every subcommand is listed below.
Specification
seven skills that capture what the product is — its decisions, modules, features, contracts, screens and prototypes — in inspire_kb/
Architecture decisions spanning ≥2 modules or ≥2 surfaces — or system-wide — along a maturity ladder (design → prototyped → implemented).
create | New ADR (defaults to design maturity). |
|---|---|
update | Modify an ADR — supersede required only once implemented. |
promote | Advance the maturity ladder and propagate its consequences. |
supersede | Retire an ADR and wire in its replacement. |
The module hub — overview + links to its features, screens, specs and ADRs, kept in sync across every KB layer.
create | Scaffold a new module: its hub + features and screens folders, and record its ID prefix. |
|---|---|
review | Full consistency review incl. hub ↔ sub-layer sync. Required gate before a PR that touches it. |
update | Add or remove use cases, restructure, realign after an ADR — transactionally. |
scan | SDD entry point: surface features lacking specs and chain authoring into /inspire-domain. |
delete | Remove the module (hub + subfolders) and clean every cross-reference. |
Lifecycle of a single use case, kept in sync with screens, specs and ADRs.
create | New use-case file; runs the acceptance-criteria quality gate first. |
|---|---|
review | Cross-layer coverage for one feature — or batch over a whole module. |
update | Change description, dependencies, priority or state; re-gates the acceptance criteria. |
scan | SDD-layer alignment: which action descriptors realize the feature (fast). |
delete | Remove the feature and clean its references across layers. |
Domain contracts (SDD) — action descriptors and entity documents, authored through a socratic interview.
define | Author a new action or entity from scratch, interview-driven. |
|---|---|
show | Render an existing descriptor with cross-references resolved (read-only). |
update | Iterate on a descriptor — blocks on stable, demote first. |
refactor | Rename, split or merge actions, walking each consumer. |
delete | Remove an action — refuses if any other action requires it. |
promote · demote | Walk the lifecycle forward / back (draft → accepted → stable). |
review | Run the quality-lib checks and show findings (read-only). |
source | Show the back-source trail for every claim (read-only). |
graph | Print the action→action requires graph + supersession edges (read-only). |
Pattern-driven screen specs: each screen instantiates a shared pattern and reuses shared components.
create | Author a new screen spec from a shared pattern. |
|---|---|
validate | Check a screen against its pattern and components; flag drift (incl. reverse drift from the prototype). |
update | Iterate on an existing screen — blocks on stable, regress it first. |
promote | Walk a screen through its four-state lifecycle. |
routes | Render the derived route map and the transition graph (read-only). |
extract | Promote repeated UI blocks into shared components or patterns. |
audit | Sweep a module's screens for pattern and component compliance. |
The horizontal, mock-data visual prototype (in this repo). Discovery: the user sees the whole product and steers it; insights co-evolve the vault live.
scaffold | Build or extend the /prototype mock, pattern-driven from the KB (design system + UI profile, agile — no tests). |
|---|---|
learnings | Insights land in the vault live via the spec skills — the horizontal keeps no learnings file. |
Vertical spikes: register and harvest an external functional-prototype repo — a gap analysis, not a copy.
register | Reference an external spike repo (name, question, scope, features) and set up its learnings hygiene. |
|---|---|
capture | Gap-analyse the spike against the vault; import the signal it de-risked, leave its rough shortcuts behind. |
Codification
two skills that realize the knowledge base as production code under source/ — one attended, one unattended
The coding stage — always re-anchoring to the ADRs, descriptors and acceptance criteria that specify the code.
tdd | Implement a feature test-first, anchored to its acceptance criteria. |
|---|---|
review | Judgment review of a diff against the KB and universal quality; fans out to dimension agents. |
debug | Six-step root-cause framework; routes spec gaps back to /inspire-feature or /inspire-domain. |
fix-build | Diagnose and fix compile / build errors, then verify. |
fix-vulns | Remediate npm vulnerabilities with the fewest overrides, keeping build and tests green. |
The unattended loop — one goal, no human turns between the start and the report. It walks the knowledge base in dependency waves, giving every unit a contracter, a tester, an implementer and two overseers.
plan | Read-only: the waves it would build, what blocks each one, and a refusal rather than a run that provably cannot reach its goal. |
|---|---|
run | Walk every wave hands-off, each persona in its own worktree. A unit is promoted only once both overseers approve and the tests citing its claims are green — and promotion is a merge carrying that verdict, never a knowledge-base write. |
Stack-agnostic by design. Both codification skills layer optional stack profiles — resolved on demand from 00_bootstrap/stack.md — that add a framework's concrete conventions (layering, test conventions, review focus, build commands) on top of the generic checks. The template ships lean react, angular, nestjs, ios and android defaults plus a typescript language profile; a fork adds its own.
Housekeeping
six skills that set up and keep the workspace coherent — greenfield foundation, the surface roster, brownfield onboarding, the work tracker, the pre-PR review, and the lessons catalog
The project foundation — language, tech stack + shape, and the design system every other layer reads.
init | First-time setup: language, stack + shape, theme, and the project's own root README. |
|---|---|
language | Set the output language every skill writes its artifacts in. |
stack | Define or update the tech stack, its shape, and the inspire-code stack profiles. |
theme | Define or update the design-system default (theme.md) — or derive it from a mockup's CSS. |
design-system | Edit the project's live design system (05_screens/design-system.md), seeded from the theme. |
readme | Create or update the project's own root README. |
review | Check the bootstrap artifacts exist and stay coherent. |
The suite's surface roster — the second axis beside the module. A surface is a deliverable that faces someone: a UI, a headless service, or a shared lib package. One domain truth spans them all; a project that declares none is a suite of one.
add | Declare a surface — greenfield (empty), split (grown out of an existing one, with an operator-classified sweep that moves its screens and re-prefixes routes), or adopt (an existing codebase joining, via /inspire-extract). |
|---|---|
retire | Wind a surface down: everything scoped solely to it takes an explicit archive-or-rescope decision; the roster entry goes last. |
review | Roster coherence — unique non-reserved ids, packages under source_root, unique shell prefixes, and a screens tree in the shape the roster implies (read-only). |
Brownfield onboarding — fan out four parallel scanners over an existing codebase (stack & infra, UI screens, logic·API·DB, styles), consolidate into cross-linked KB candidates, and hand off to the authoring skills. Read-only against the source.
scan | The flagship: fan out the four scanners over a path; each inventories its artifacts and proposes consolidations. |
|---|---|
fingerprint | Quick read — run only the stack + styles scanners to see what the codebase is before a full scan. |
review | Re-open the consolidated manifest for another pass before handing candidates to the authoring skills. |
Workspace-level validation: the pre-PR global review and top-level vault-structure checks.
review | Full cross-module vault review. Required gate before any PR that touches inspire_kb/. |
|---|---|
structure | Validate CLAUDE.md, module hubs and ADRs by their glob, screens directories' _index.md, and tracker invariants — no orphan files at the vault root. |
A plain-file kanban — one Markdown ticket per file, no external tool — for work, drift and skill-feedback.
create | Open a ticket (epic, size, importance, owning skills). |
|---|---|
update | Change fields; a status change moves the file between open and archive. |
close | Mark Done (or Cancelled) and archive it. |
list | Query open tickets by status, epic, size or skill (read-only). |
show | Print a ticket's frontmatter + body (read-only). |
The self-teaching layer — write-once, timestamp-named, version-stamped one-line instructions that change how a skill behaves in this project. Relevant here; whether one generalizes is decided upstream.
note | Capture a lesson: one imperative line, drafted with you and confirmed, stamped with the runtime version and release commit. Written once and never edited — to revise, write a new one with --supersedes. |
|---|---|
list | Query the catalog by date, skill, category or reporter (read-only). |
show | Print a lesson's frontmatter + body (read-only). |
purge | Delete archived lessons past a threshold — dry-run by default, whole files only, so the write-once contract holds. Fully optional. |
Every artifact a skill writes into the knowledge layers — ADRs through screens — carries provenance. After the write, the tooling — never the skill itself — stamps a produced block onto it: which skill performed the write, the exact deployed bytes it ran against, and the runtime version, so drift in the machinery is visible without pinning content to a moment in time. Separately, an operator can vouch for what's there with endorsed: a name and a date, written only after an explicit yes. It is attestation, not a content hash — a human read this at that point in history; git history is the audit trail since. Absence is honest: no block reads as "never endorsed" or "provenance unknown," and nothing is stamped retroactively.