Slash Command

/code

From c4m

Retro-documents an existing codebase as a C4 diagram by scanning the repo, presenting findings, and dialoguing to fill ambiguities.

documentation

Install

npx claudepluginhub cheriftj/c4-model-skill --plugin c4m

Prompt Preview

<!-- markdownlint-disable-file MD041 -->

You are handling a `/c4m:code` invocation.

The user wants to **retro-document an existing codebase**. This is the `c4-model` skill's **Document-code mode** — skip mode detection and go straight to the scan + dialogue workflow.

Load `skills/c4-model/mode-document-code.md` and execute its steps:

1. **Quick framing** (max 3 questions): repo scope, expected levels, output format and destination.
2. **Scan**: for a repo larger than ~50 files or an unfamiliar stack, delegate to a sub-agent via the `Agent` tool with `subagent_type: Explore` using the in...

Command Content

Other plugins with /code

/code

Implements a feature via multi-agent workflow, producing implementation plan, complete code, integration guide, testing strategy, and next actions.

essentials

2.4k

/code

Forces explicit assumption-stating, edge case consideration, and condition verification before generating code for the request.

context-fields

132

/code

Bootstraps ClosedLoop orchestrator for coding sessions in a working directory. Accepts [working-directory] [--prompt <name>] [--prd <requirements-file>] [--plan <plan-file>]. Starts with TodoWrite delegation.

code

/code

Launch a code-mode agent team

swarm

/code

编码实现专家。按计划实现功能，遵循代码规范，处理开发问题。TDD 优先，测试驱动。

claude-dev-assistant

/code

Execute a plan by spawning a swarm of parallel plan-coders

TaskTaskOutput

pair-swarm

Stats

Stars19

Forks1

Last CommitApr 24, 2026

Actions

View Source View Plugin View on GitHub View README

Tags

interactive-refinement

You are handling a `/c4m:code` invocation. The user wants to **retro-document an existing codebase**. This is the `c4-model` skill's **Document-code mode** — skip mode detection and go straight to the scan + dialogue workflow. Load `skills/c4-model/mode-document-code.md` and execute its steps: 1. **Quick framing** (max 3 questions): repo scope, expected levels, output format and destination. 2. **Scan**: for a repo larger than ~50 files or an unfamiliar stack, delegate to a sub-agent via the `Agent` tool with `subagent_type: Explore` using the in...

You are handling a /c4m:code invocation.

The user wants to retro-document an existing codebase. This is the c4-model skill's Document-code mode — skip mode detection and go straight to the scan + dialogue workflow.

Load skills/c4-model/mode-document-code.md and execute its steps:

Quick framing (max 3 questions): repo scope, expected levels, output format and destination.
Scan: for a repo larger than ~50 files or an unfamiliar stack, delegate to a sub-agent via the Agent tool with subagent_type: Explore using the inventory prompt in mode-document-code.md. Otherwise use Glob / Grep / Read directly.
Present findings as raw lists: candidate containers (with technology), external dependencies, identified flows, doubtful flows, ambiguities. Ask the user if the breakdown matches reality.
Dialogue to fill ambiguities (3-5 questions per batch). If the user doesn't know, mark it as an assumption.
Draft, iterate, finalize — produce Context + Container, run the checklist, deliver.

Inherit the common contract from SKILL.md. Inferences from code without explicit confirmation go into the Assumptions section of the document, never silently into the diagram.

If the user provided a repo path or description after /c4-document-code, use it as the scan target. Otherwise, ask which repo to document and what scope (whole monorepo or subfolder).