architect
Place one slice in the C4 model (LikeC4) by interviewing the driver on each design decision: layer by layer in arc42's views, and a runtime view only for a complex sequence. A short MADR only for a cross-cutting decision. Use after the spec, before code.
Install
npx skills add https://github.com/novibe-org/novibe/tree/main/plugins/novibe/skills/architect
claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install novibe-org-novibe@llmmart
git clone https://github.com/novibe-org/novibe.git
The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole novibe-org/novibe collection as a plugin from our marketplace. Git is the plain clone.
Skill manifest
Architect
In: the Gherkin spec at features/<domain>/<feature>.feature.
Out: the slice placed in the LikeC4 model at docs/architecture/ — plus one terse ADR in
docs/adrs/, only when a crucial cross-cutting decision was made.
Write only the model — no code, no diagram files.
Read the model — none yet? This slice starts it, in the layout below, with just enough to place the slice.
Grill the design into the model, only where the slice changes it — in arc42's order: context and scope, then the building blocks level by level, each box before its parts, then deployment. Touch only the layers the slice changes, and say in one line which stay as they are. A runtime view only when the order of the steps can be read neither from the relations nor from a scenario — a sequence a scenario pins needs none. Ask in rounds, each question with your recommendation; write each answer into the model before the next round.
Ask with
AskUserQuestion— up to four questions a call, so a bigger round takes several calls in a row; your recommendation is the first option, marked (Recommended). A question with nothing to choose between goes in plain text. No such tool in this session? Number the questions and put your recommendation under each.Facts are yours, decisions are the driver's — look up what the code and the model can tell you; ask only what changes the structure: a new element, who talks to whom, the mechanism between them, where something runs. A question about behaviour is the spec's: hand it back to the requirements step, never settle it in the model.
ADR only if warranted — default to none. Before writing one, ask: would a later slice decide differently without it? If not, there is no ADR. Never one that says how a feature behaves; a choice the driver made for this slice is answered in the model, not recorded again. A decision that is cross-cutting? Recommend the ADR and ask the driver first. Then plain MADR, kept short, next number in
docs/adrs/.Push — once no question is open and the driver agrees: commit as
arch: …to the slice's branch and push.
Rules for the model
- Views follow arc42; its goals and quality live in
features/, its cross-cutting decisions indocs/adrs/. - A box with parts of its own gets a view at the next level.
- A building-block view holds its subject's children and their direct neighbours. No element appears at two levels in one view.
- A runtime view holds only the elements that take a step.
- Say a fact once. A description says what an element is, in one sentence. What it does to another element, and by what mechanism, is a relation — never when, unless, or what the user is told: that is the spec's. How a story runs is the feature file; a runtime view shows only a sequence too complex to read from it. Why one feature is built this way needs no record; why every feature must be is an ADR.
- An ADR names the views it shaped, by view id; the model never names an ADR.
- Applications share no storage; one reaches another only through its API.
- Model your own parts. A library you use is a technology line; a package you write is a
library. - Where the system is headed is a view on this model, never a second model.
- An element takes the spec's word for what it is, never a second one — the ubiquitous language. A part the spec does not name takes the field's term; when two are in use, offer them with their source and ask.
Layout
likec4.config.mjs(defineConfig, never JSON): the project, its summary inmetadata.description.models/base-model.c4: element kinds, people, externals, the system and its applications.models/<part>.c4: one per container or package, eachextending its parent.models/deployment.c4: where each part runs.views/views.c4: every view.
Done when
No question is open, the driver agrees the model places the slice, and an ADR exists only if a crucial decision was made — often none.
Files (novibe)
-
SKILL.md 4.5 KB
--- name: architect description: "Place one slice in the C4 model (LikeC4) by interviewing the driver on the decisions that change its structure, in arc42's views, touching only the layers the slice changes. No runtime view for a sequence a scenario pins, and an ADR only when a later slice would decide differently without it. Use after the spec, before code, when a slice brings a new component, framework, technology or integration." --- # Architect **In:** the Gherkin spec at `features/<domain>/<feature>.feature`. **Out:** the slice placed in the **LikeC4 model** at `docs/architecture/` — plus one terse ADR in `docs/adrs/`, only when a crucial cross-cutting decision was made. **Write only the model** — no code, no diagram files. 1. **Read the model** — none yet? This slice starts it, in the layout below, with just enough to place the slice. 2. **Grill the design into the model, only where the slice changes it** — in arc42's order: context and scope, then the building blocks level by level, each box before its parts, then deployment. Touch only the layers the slice changes, and say in one line which stay as they are. A runtime view only when the order of the steps can be read neither from the relations nor from a scenario — a sequence a scenario pins needs none. Ask in rounds, each question with your recommendation; write each answer into the model before the next round. **Ask with `AskUserQuestion`** — up to four questions a call, so a bigger round takes several calls in a row; your recommendation is the first option, marked *(Recommended)*. A question with nothing to choose between goes in plain text. No such tool in this session? Number the questions and put your recommendation under each. **Facts are yours, decisions are the driver's** — look up what the code and the model can tell you; ask only what changes the structure: a new element, who talks to whom, the mechanism between them, where something runs. A question about behaviour is the spec's: hand it back to the requirements step, never settle it in the model. 3. **ADR only if warranted** — default to none. Before writing one, ask: would a later slice decide differently without it? If not, there is no ADR. Never one that says how a feature behaves; a choice the driver made for this slice is answered in the model, not recorded again. A decision that is cross-cutting? Recommend the ADR and ask the driver first. Then plain [MADR](https://adr.github.io/madr/), kept short, next number in `docs/adrs/`. 4. **Push** — once no question is open and the driver agrees: commit as `arch: …` to the slice's branch and push. ## Rules for the model - Views follow [arc42](https://arc42.org/overview/); its goals and quality live in `features/`, its cross-cutting decisions in `docs/adrs/`. - A box with parts of its own gets a view at the next level. - A building-block view holds its subject's children and their direct neighbours. No element appears at two levels in one view. - A runtime view holds only the elements that take a step. - **Say a fact once.** A description says what an element is, in one sentence. What it does to another element, and by what mechanism, is a relation — never when, unless, or what the user is told: that is the spec's. How a story runs is the feature file; a runtime view shows only a sequence too complex to read from it. Why one feature is built this way needs no record; why every feature must be is an ADR. - An ADR names the views it shaped, by view id; the model never names an ADR. - Applications share no storage; one reaches another only through its API. - Model your own parts. A library you use is a technology line; a package you write is a `library`. - Where the system is headed is a view on this model, never a second model. - **An element takes the spec's word** for what it is, never a second one — the [ubiquitous language](../../references/ubiquitous-language.md). A part the spec does not name takes the field's term; when two are in use, offer them with their source and ask. ## Layout - `likec4.config.mjs` (`defineConfig`, never JSON): the project, its summary in `metadata.description`. - `models/base-model.c4`: element kinds, people, externals, the system and its applications. - `models/<part>.c4`: one per container or package, each `extend`ing its parent. - `models/deployment.c4`: where each part runs. - `views/views.c4`: every view. ## Done when No question is open, the driver agrees the model places the slice, and an ADR exists only if a crucial decision was made — often none.
Comments (0)
Sign in to join the conversation.
Reviews (0)
No reviews yet.
No comments yet.