Bootstrap the central system spec at `docs/system/` for a repository that has never had one. Scans the governed surface, proposes a concept map clustered by directory, and materializes elements + shards ONLY after a human confirms that map. Use when adopting the baseline on an existing project, or when the corpus needs re-deriving from scratch. Re-runnable. Requires `memory.architecture_map.enabled` and a declared `governed_surface`.
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
A project adopting the baseline has no spec archive to migrate from. Measured on this repository, 68% of governed files appear in no spec at all — and a project that never ran the spec phase has none. So the corpus is rebuilt from code, not imported.
What the machine does and what the human does is the whole design:
| Step | Owner |
|---|---|
| Scan the governed surface, cluster by directory, propose a concept map | machine |
| Confirm or edit that map | human, always |
| Materialize elements, derive edges, stamp digests, report coverage gaps | machine |
project.json → memory.architecture_map.enabled is true and
memory.architecture_map.governed_surface declares this project's roots. An absent
surface is a named error, never a default — a fallback would model the consumer's
.claude/ and report total coverage over a surface that is not theirs.
Check the flag.
node .claude/skills/workspace/cli.mjs flags # gates on memory.architecture_map.enabled — read the `architecture_map:` line
false → stop and tell the user to enable it (and declare a governed surface) first.
Propose the map.
node .claude/skills/workspace/cli.mjs sync --json # wraps workspace/sync.mjs -> proposeMap (propose half only; runSync is not exposed)
The proposal is a starting point, not an inference to trust. Directory clustering is deliberately plain because a human edits it next.
Have the human confirm it — always. Present the proposed concepts via
AskUserQuestion: which clusters are real concepts, which should merge, which
should split, what each is called. Concept membership is authored; this step
has no skip and no --yes. An unattended run that inferred membership would undo
the rule every prior decision in this lineage protects.
Materialize what was confirmed. runSync writes the confirmed concepts, derives
one element per anchor, stamps digests, and returns coverage gaps. It refuses
outright when no confirmation callback is supplied, and writes nothing before
confirmation returns — a refused sync leaves the corpus byte-identical.
Report the gaps. Every governed file should resolve to at least one element. Surface what did not, and let the human decide whether to widen an anchor or accept the gap. Do not close a gap by inventing a concept.
identity.deriveId exists for. Ids stay authored wherever a concept file declares
one.docs/system/. It never writes memory, never touches a consent
path, and never commits.まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
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.
日本語の概要は準備中です。原文の説明を表示しています。