/model-spec — Model Spec
Category: Scoping & Design · Primary agent: modeling-methodology-specialist
Writes the model specification: equations, timing, closures, steady state, shocks, observables and known limitations.
Arguments: $ARGUMENTS
Purpose
Write the model specification: the complete, unambiguous statement of what will be built — notation, timing, units, every equation and closure, steady state, shocks, observables, parameters, identification concerns and known limitations. The output is the document the code is checked against, so that the build and validation have a single source of truth.
Use it when a model brief is approved and building is about to start, or an existing model needs a written specification.
Do not use it when the model class is still undecided (/select-model-class).
Before you start
- Check required inputs. For each input below record
FOUND or ABSENT (never 'assumed'):
- docs/models//model-brief.md
If a required input is
ABSENT, that part is NOT ASSESSED — NO DATA: do not estimate or invent it; name what is missing and which skill produces it. If all required inputs are absent, stop and say so.
- Check confidentiality. Identify the data classification level of the inputs (
.claude/docs/confidentiality-and-ai-use.md). Do not proceed with restricted or confidential data in a way the policy does not allow.
- Collaboration. Follow
.claude/docs/collaboration-protocol.md: ask questions first, present options, get approval before writing files, and update production/session-state/active.md after each approved section.
Agents
modeling-methodology-specialist — primary agent; coordinates the work and integrates results
open-economy-dsge-specialist — Builds small open-economy DSGE models
semi-structural-gap-modeler — Builds quarterly projection and semi-structural gap models
deep-learning-architect — Designs deep learning architectures for macro-financial data
Run these agents as subagents (the Task tool), in parallel where the steps are independent. Subagents only write to the paths named in your instructions.
Key design decisions (present options, let the user choose)
| Decision |
Typical options |
What it changes |
| Notation |
studio conventions, literature conventions |
Consistency with documentation |
| Timing |
end-of-period stocks, beginning-of-period stocks |
Code correctness |
| Detail |
core model only, with extensions as optional bricks |
Modularity |
| AI models |
architecture, loss and training data in place of equations |
What is specified |
Workflow
- Select the specialists for the model class and have them draft section by section
- Define notation, timing conventions and units; list all equations and the closure
- Keep a notation register used by all later documents
- Derive the steady state and the log-linearization (or the architecture and loss for AI models)
- Verify derivations symbolically for medium and large models
- List shocks, observables, parameters and identification concerns
- State known limitations and non-purposes
- Identify which parts can be lego bricks with declared interfaces
Checkpoints with the user
- After the equation list: confirm mechanisms and closure
- After shocks and observables: confirm identification concerns
Common pitfalls
- Timing ambiguities left for coders to resolve
- Equations without units
- Missing closure conditions
- Limitations omitted
Output
docs/models/<name>/model-spec.md
The specification contains the notation register, equations with units and timing, closure, steady state, shocks, observables, parameters, identification concerns and limitations.
Gate / verdict
- Every endogenous variable has an equation; counts of equations and unknowns match
- Steady state is derived or the computation approach is stated
- Timing conventions and units are stated for every variable
- A notation register is included
Suggested next steps
/calibration-plan
/data-requirements
1---2name: model-spec3description: "Writes the model specification: equations, timing, closures, steady state, shocks, observables and known limitations."4argument-hint: "[model name]"5user-invocable: true6allowed-tools: Read, Glob, Grep, Write, Edit, Bash, AskUserQuestion, Task7metadata:8 source: https://skillmd.com/skills/majiayu000/model-spec9---1011# /model-spec — Model Spec1213**Category:** Scoping & Design · **Primary agent:** `modeling-methodology-specialist`1415Writes the model specification: equations, timing, closures, steady state, shocks, observables and known limitations.1617Arguments: `$ARGUMENTS`1819## Purpose20Write the model specification: the complete, unambiguous statement of what will be built — notation, timing, units, every equation and closure, steady state, shocks, observables, parameters, identification concerns and known limitations. The output is the document the code is checked against, so that the build and validation have a single source of truth.2122**Use it when** a model brief is approved and building is about to start, or an existing model needs a written specification.2324**Do not use it when** the model class is still undecided (`/select-model-class`).2526## Before you start271. **Check required inputs.** For each input below record `FOUND` or `ABSENT` (never 'assumed'):28 - docs/models/<name>/model-brief.md29 If a required input is `ABSENT`, that part is **`NOT ASSESSED — NO DATA`**: do not estimate or invent it; name what is missing and which skill produces it. If all required inputs are absent, stop and say so.302. **Check confidentiality.** Identify the data classification level of the inputs (`.claude/docs/confidentiality-and-ai-use.md`). Do not proceed with restricted or confidential data in a way the policy does not allow.313. **Collaboration.** Follow `.claude/docs/collaboration-protocol.md`: ask questions first, present options, get approval before writing files, and update `production/session-state/active.md` after each approved section.3233## Agents34- `modeling-methodology-specialist` — primary agent; coordinates the work and integrates results35- `open-economy-dsge-specialist` — Builds small open-economy DSGE models36- `semi-structural-gap-modeler` — Builds quarterly projection and semi-structural gap models37- `deep-learning-architect` — Designs deep learning architectures for macro-financial data3839Run these agents as subagents (the `Task` tool), in parallel where the steps are independent. Subagents only write to the paths named in your instructions.4041## Key design decisions (present options, let the user choose)42| Decision | Typical options | What it changes |43|---|---|---|44| Notation | studio conventions, literature conventions | Consistency with documentation |45| Timing | end-of-period stocks, beginning-of-period stocks | Code correctness |46| Detail | core model only, with extensions as optional bricks | Modularity |47| AI models | architecture, loss and training data in place of equations | What is specified |4849## Workflow501. Select the specialists for the model class and have them draft section by section512. Define notation, timing conventions and units; list all equations and the closure52 - Keep a notation register used by all later documents533. Derive the steady state and the log-linearization (or the architecture and loss for AI models)54 - Verify derivations symbolically for medium and large models554. List shocks, observables, parameters and identification concerns565. State known limitations and non-purposes57 - Identify which parts can be lego bricks with declared interfaces5859## Checkpoints with the user60- After the equation list: confirm mechanisms and closure61- After shocks and observables: confirm identification concerns6263## Common pitfalls64- Timing ambiguities left for coders to resolve65- Equations without units66- Missing closure conditions67- Limitations omitted6869## Output70`docs/models/<name>/model-spec.md`7172The specification contains the notation register, equations with units and timing, closure, steady state, shocks, observables, parameters, identification concerns and limitations.7374## Gate / verdict75- Every endogenous variable has an equation; counts of equations and unknowns match76- Steady state is derived or the computation approach is stated77- Timing conventions and units are stated for every variable78- A notation register is included7980## Suggested next steps81- `/calibration-plan`82- `/data-requirements`