Employee Suggestion Hub

Employee Suggestion Hub helps define a feedback loop that includes an explicit response to each idea. Its workflow moves from submission through triage and decision to a response, then implementation or closure. It treats the response record as an essential step in keeping a suggestion process active.

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 suggestion box, employee feedback portal structure, idea submission tracker or staff suggestion process. It fits scale-stage businesses moving ideas out of forms, chats or meetings into a review queue.

It produces empty templates and does not implement changes or promise that a suggestion will be adopted. 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 cover staff and submission volumes, anonymous participation, triage and response ownership, response times, sharing decisions, crediting implemented ideas and the existing feedback channel. The requested outcome can be a submission form, review queue or reporting. Fields include suggestion title, submitter, anonymity, department, category, description, submission date, votes, reviewer, decision, response, status and suggestion ID. Categories cover process, tooling, workload, culture and facilities. Initial status options distinguish submitted, under review, accepted, in progress, closed and declined ideas.

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_employee_suggestion_hub_status ON employee_suggestion_hub (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.