Preflight a spec draft without saving. Runs the same checks as the write-boundary hooks — PlantUML syntax, required diagram presence, AC-to-sequence traceability, Design calls quality floor, and System delta row resolution — and prints a compact pass/fail table. Use while iterating so the hooks don't bite on save.
中文简介正在准备中。当前显示原文说明。
查看安装方法安装前可以查看交给 AI 代理的指令内容。
Checker config (tier-dial:read-path): this checker's floor/ceiling come from the tier dial at
.claude/hooks/lib/tier-dial.mjsviaresolveCheckerThreshold('spec'). Advisory only this slice (v1 piece 2); blocking is piece 5.
Invocable by both user (/spec-lint <slug>) and Claude (when iterating on a spec and wanting to check status before writing).
Five checks always run, same logic as the hooks, but advisory (no writes are blocked). One more appears only when its trigger fires.
Checks are identified by row name, in the order the report prints them. Ordinals are deliberately
absent: they have already drifted once — lint.mjs labels the codesign check "#4" in its own comment
while the report prints it last — and a number that means one thing in the source and another in the
table is worse than no number.
| Check | Row name | Hook it mirrors |
|---|---|---|
Every plantuml fence parses under plantuml -checkonly | plantuml_syntax | plantuml_syntax_guard |
Required diagram kinds present (config: project.json → artifacts.required_diagrams.spec) | diagram_presence | spec_diagram_presence_guard |
Every AC-NNN row in the Acceptance criteria table references a §Behavior #N section that exists | ac_traceability | (no hook — unique to the lint) |
Each ## Design calls row carries a populated Reference target and Quality criteria | design_calls | spec_design_calls_guard |
Each ## System delta row resolves — an add anchors inside the governed surface, a change/remove names an existing element | system_delta | (no hook — the guard checks only that the section is present) |
| Conditional check | Row name | Fires when |
|---|---|---|
A ## Decisions section is present | codesign_decisions | workflow.json → codesign_mode is true |
system_delta reports SKIP when project.json → memory.architecture_map.enabled is not true. The
corpus at docs/system/ is opt-in, so a project that has not adopted it declares no delta and the
check has nothing to resolve.
/spec-lint <slug> — where <slug> corresponds to docs/specs/<slug>.md.
docs/specs/<slug>.md must exist.node .claude/skills/spec-lint/lint.mjs <slug>
check status
---------------------------------- ------
plantuml_syntax PASS
diagram_presence FAIL (missing: c4_component, dependency_graph)
ac_traceability FAIL (AC-002 → §Behavior #2 not found)
design_calls PASS
system_delta FAIL (add row foo-guard: anchor docs/notes/x.md falls outside the governed surface)
---------------------------------- ------
overall FAIL
Exit 0 on overall PASS, 1 on overall FAIL. Intended for use in CI or a pre-commit loop as well as interactively.
plantuml CLI on PATH for check #1 (if absent, #1 is reported as SKIP (no plantuml); the rest still run).spec-lint runs against the on-disk file, not proposed content. Save or use the hooks to validate an unsaved draft.spec-lint does not render. Use /spec-render <slug> for that.还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
Phase 10.5 — move the slug's workflow artifacts (intake, scout, research, spec, approvals, swarm state, security reports, rendered diagrams) to docs/archive/<YYYY-MM-DD>/<slug>/. Runs before /commit so the committed tree is clean of work-in-flight files. workflow.json stays live and gets archived as the first step of /commit.
中文简介正在准备中。当前显示原文说明。
Drift check between the baseline implementation on disk and the claims in `docs/init/seed.md` + cross-references in CLAUDE.md, README.md, and the rendered docs site. Verifies hook/agent/skill/command names + counts, settings.json wiring, project.json key presence, .mcp.json servers, vendored license files, and helper script presence. Exit 0 PASS / 1 FAIL — suitable for CI. Read-only; safe to invoke any time.
中文简介正在准备中。当前显示原文说明。
PM-mode brainstorm helper. Captures the requirement via Socratic dialogue before any entry phase (`/intake`, `/spec`, `/tdd`) drafts its artifact. Stage 0 skip-check, Stage 1 gap-analysis, Stage 2 probe-loop, Stage 3 confirm-and-persist. Output lives at `docs/brief/<slug>.md`. Never proposes solutions — Stage 2 dialogue discipline is structurally enforced via `discipline.mjs`.
中文简介正在准备中。当前显示原文说明。
Draft a Business Requirements Document (BRD) for cross-functional or stakeholder-heavy work that needs more structure than an intake. Use after `/intake` when the request spans multiple systems/teams, carries regulatory weight, or needs formal sign-off. Output lives at `docs/brd/<slug>.md`.
中文简介正在准备中。当前显示原文说明。
Workflow track for tasks that need no TDD — documentation edits, governance count bumps, vendored-skill content updates, configuration tweaks, formatting, typo fixes, dependency bumps where no project code changes. Skips `/scenario` and `/implement` (no failing test to drive) and runs the work directly. `archive`, `memory-sync`, `/grant-commit`, and `/commit` remain mandatory. `verify`, `simplify`, `integrate`, and `document` are conditional — required when the diff hits one of the listed triggers, optional otherwise. `verify` is skipped only when the diff is pure-docs/prose AND `project.json → test.kind` is `behavior` (absent/invalid `test.kind` → `structural` → verify runs). Chore is a stripped-down pipeline, not a bypass; never silently skip a conditional phase whose triggers apply.
中文简介正在准备中。当前显示原文说明。
Analyze a codebase and recommend Claude Code automations (hooks, subagents, skills, plugins, MCP servers). Use when user asks for automation recommendations, wants to optimize their Claude Code setup, mentions improving Claude Code workflows, asks how to first set up Claude Code for a project, or wants to know what Claude Code features they should use.
中文简介正在准备中。当前显示原文说明。