Spreadsheet Manual Build

Spreadsheet Manual Build renders a field list already confirmed by the active business module. It owns no table or schema. The same canonical names, types, order, requiredness, options and calculations that produce the module’s CSV, SQL, JSON Schema and Notion mapping produce its workbook. It fits every business stage.

The smallest setup is one sheet named Register, one header row and one column per confirmed field. Apply a bold header, freeze the top row, add an autofilter, set sensible widths and wrap long text. Add extra sheets, dashboards, charts, lookup sheets or instruction tabs only when requested or clearly required by the confirmed workflow.

Use it for an Excel workbook, spreadsheet template, manually editable register, importable table or workbook built from agreed module fields. It does not decide which fields the business needs. A missing or ambiguous source module must be clarified before building. A formatting fix stays a fix; a mapping request produces a column plan rather than a file.

The deliverable is a file rather than a connected system. It has no automation, synchronization, cross-row validation or source-system connection. Validation lists are conveniences that pasted values can bypass. Operational checking remains necessary after users enter records, and qualified legal, tax or payroll review is needed before the register drives decisions.

Reuse the confirmed purpose, fields, types, options, dates, currency, parent-defined formulas, statuses and IDs. Ask one short question only when the answer changes the result, such as workbook versus CSV or whether examples are wanted. An explicitly requested workbook defaults to .xlsx without example rows. An .xlsx must be a real file; CSV must not be described as an Excel workbook.

Template intent produces headers and formatting with no rows. Explicit example intent permits obviously synthetic rows. Fix intent changes only the requested structure or formatting. Mapping intent provides the column plan. Generated data is delivered without preamble or closing prose. Workbook name, necessary sheets, exact columns, date and number formats and confirmed options are checked before handoff.

IDs, titles and ordinary text use Text. Long text is wrapped. Numbers use Number; currency uses Currency or Accounting only when the currency is known, otherwise keep numbers and a separate currency designation. Percentages use a 0-100 scale and must be converted to fractions before Percentage formatting. Dates use Date and datetimes Date plus Time. Checkboxes use TRUE/FALSE. Select fields use practical data-validation lists containing only confirmed options. Multi-select values use Text unless a richer structure is requested. URLs use Hyperlink or Text; email and phone use Text. Relations use text reference keys unless an explicit workbook design supports lookups.

Never invent formulas. Add them only when the parent module defines them or the user provides the requested rule. Values calculated elsewhere, such as Net Tax Payable, Days to Due, Balance and Variance, remain inputs or outputs. Parent rules assigning calculation to accounting or tax software remain binding. Empty ID columns stay blank; production IDs are not generated without a request, and automatic spreadsheet IDs require a confirmed pattern.

CSV uses UTF-8 with a byte order mark and a separate note identifying number, date and currency formatting. A text-stored date still sorts as text regardless of its appearance. Relation keys are not live links. Lookup sheets or VLOOKUP chains require an explicit design request and confirmation of the target sheet.

Read the active module’s Field Reference at skills/<slug>/SKILL.md; CATALOG.md is the user-facing module index. The input index covers Foundation, Acquire, Onboard, Manage, Develop, Engage, Protect, Operate, Analyze and Exit modules, with accounting-audit and brand-growth sub-packs. The selected module determines the workbook fields, not the index’s labels or example field counts. Options belong to that module and remain a business-confirmed vocabulary.

A supplied default is:

format: xlsx
example_rows: false

Separate best-practices and security-safety references contain further guidance. The generated file stays empty unless synthetic examples were expressly requested.