Document Management System

Document Management System helps define naming, ownership and document lifecycle records before adding a new storage tool. It recommends one owner per document type and a clear distinction between draft and final versions. The workflow captures a document, names and tags it, assigns an owner, identifies an approved version and archives it.

The skill separates advice, review, conversion and build requests before producing artifacts. Advice receives a short recommendation and an offer of a relevant build. An explicit build request proceeds once essential missing facts are resolved. It asks one question at a time, reuses answers already supplied and stops when further answers would not change the deliverable. Unknown information remains unknown rather than receiving invented values.

Use it for a document register, signature tracker, shared-drive index or a storage and signing process structure. It fits growth-stage businesses with scattered files or an existing shared drive that needs a clearer index.

It produces empty templates and does not store files or replace a document management platform. The skill does not calculate payroll, tax, leave balances or KPIs. Automation, reminders and synchronization require an integration layer. Legal, tax and HR review is required before templates drive real decisions.

Inputs describe document types and volumes, items that must not be edited, folders or tags, naming conventions, access levels, approvers, version retention and archive timing. The requested outcome can be a structure, naming rule or index. Fields record document title and type, employee, department, uploader and upload date, signature requirement and signed date, version, storage link, confidentiality, status and document ID. Document types include contracts, policies, invoices, certificates, reports, ID proof and other records. Confidentiality choices distinguish internal, public, confidential and restricted documents. Status choices cover draft, review, approval, publication, supersession and archiving.

Requested artifacts can include CSV, SQL DDL, JSON Schema, Notion property mappings or an Excel workbook. The formats derive from one field list: CSV and JSON retain matching display names, while SQL uses normalized identifiers. Dates retain date types, money retains currency types and cross-table references retain relation types. Select options are a starting set that can be renamed to match the business.

One SQL example is:

CREATE INDEX idx_document_management_system_status ON document_management_system (status);

Templates are empty by default. Example rows are produced only on request and remain obviously synthetic. Sensitive identifiers should not be repeated unnecessarily during a requested review. Machine-readable data stays separate from explanatory prose and any material validation failures. Excel-compatible CSV uses UTF-8 with a byte order mark and accompanying guidance about number, date and currency columns. An XLSX workbook is a separate requested output rather than a renamed CSV.

The Notion output routes to notion-manual-import for CSV, property mappings, import steps and verification. Manual mappings require no connection. Requested live workspace changes require actual tool access, a verified target and authorization. Imported columns may initially be Text and need their mapped property types applied. Relation links resolve after both relevant databases are imported. A static mapping alone does not establish a completed workspace change.