bolt-requirements
Turn a vague business requirement into a concrete Norbital build plan a stakeholder can confirm.
- License 许可
- MIT
- 所属仓库
- norbital-ai/oss
- 最近更新
- 2026-11-15
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- bolt-requirements
- license
- MIT
- metadata
- { "package": "@norbital-ai/bolt" }
- description
- Turn a vague business requirement into a concrete Norbital build plan a stakeholder can confirm.
02 资源文件 4
- 参考文档agents/openai.yaml230 B
- 参考文档references/elicitation-questions.md2.1 KB
- 参考文档references/plan-template.md1.8 KB
- 参考文档references/primitive-mapping.md4.0 KB
03 SKILL.md 正文
Bolt requirements
The output is a plan a non-technical person can read, correct and sign, with implementation decisions underneath.
Protocol
- Elicit. Close seven groups before writing: who, what, transitions, numbers, triggers, the outside world, outputs. Questions:
references/elicitation-questions.md. - Decompose. List sub-functions by verb, each one sentence with a named person. Classify with
bolt-feasibility. Keep native and mediated rows; not-appropriate rows become explicit exclusions. - Map. Convert each accepted sub-function to primitives:
references/primitive-mapping.md. Refuse its anti-patterns. - Draw the boundary. State what the plan excludes, in business terms. External systems of record stay external. Certified outputs go through certified channels. Version-1 cuts are written down. Each not-appropriate function names its alternative. Each mediated row names what Bolt does, what the third party does, where they meet, and what survives an outage.
- Write. Emit the plan from
references/plan-template.md. Sections 1 to 8 use the stakeholder's vocabulary with no platform jargon outside build notes. End by asking whether it matches. A change to sections 1 to 8 is a plan change.
Trap words
| They say | Ask |
|---|---|
| manage | Which states does a record live through, and who moves it? |
| track | What statuses, and what must be provable later? |
| integrate | Which system owns the data, who reads, who writes? |
| report | Which numbers, for whom, how often? |
| automate | On what trigger, with what approval, what if it fails? |
| dashboard | Which numbers, at what granularity, who may see them? |
| approve | Who approves, what happens before and after, is there an override? |
Handoff
A confirmed plan is the input to authoring: bolt-primer; another skill only for what it leaves open. Keep feasibility verdicts attached so a scope change is re-classified, not re-argued.
04 同仓库更多 Skills
norbital-platform
How Norbital behaves at runtime - approvals, policies, history, audit, agent limits. Read before answering.
data-modelling
Route data modelling decisions - models, fields, layers, state, invariants, search, migrations.
bolt-primer
Build a Bolt workspace with no other skill - source roles, contract queries, authoring order, pitfalls.
bolt-feasibility
Decide per sub-function whether a business function is native, mediated, or not appropriate on Norbital.
authoring-test-suites
Choose, write and review Bolt tests that fail for a named production defect.
authoring-tenant-workspace
Index of Bolt authoring references - models, access, apps, automations, integrations, UI, build.