What it is: Resource management.
Works out the smallest useful Capacity & Workload Planner setup for the business in front of it, then
builds it only when asked. The default output is a short recommendation, not a
spreadsheet. Artifacts - CSV, SQL DDL, JSON Schema, Notion mapping - are produced on
request, from one field list so they cannot drift apart.
Layer: Layer 4: Manage. Fits: Scale stage. Table code: n/a.
Also use it when the user says "resource management", or describes the same process happening in a
spreadsheet, a document or someone inboxes.
Do not use it for: payroll calculation, tax filing, or legal advice. This skill produces
empty templates only - it never holds or processes real employee or customer data.
Follow the shared execution contract. The module-specific rules below define only domain fields, decisions, calculations, and safety constraints.
Read the request and pick the intent before asking anything.
Ask only if this is the highest-value missing fact; otherwise proceed without an opener:
Q: How many people are billable?
Skip anything the user already answered, in any earlier message. Ask the rest one at a
time, and stop as soon as the remaining answers would not change the output.
Never invent an answer. If the user does not know, record it as unknown and carry on.
Hold the answers in this shape. It stays internal - it is not shown to the user unless
they ask, and it never carries a value the user did not give.
module: capacity-workload-planner
intent: null # setup | advice | review | fix | build | convert | export
scale: null # Starter | Growth | Scale, only if the answer changes it
areas:
"Capacity": null
"Demand": null
"Method": null
"Current process": null
"Outcome": null
requested_outputs: [] # csv | sql | json | notion | xlsx - requested formats only
confirmed_facts: [] # only what the user actually said
open_questions: [] # the unanswered ones, in the order worth asking
If an artifact was requested, build it after resolving essential missing facts. Otherwise give a short recommendation and offer the relevant artifact.
Recommended approach: Start with weekly planning when it fits the work, and flag over-allocation; use daily detail when shift or delivery constraints require it.
Why this one: Weekly planning can be a useful starting point; confirm the actual planning horizon and avoid unsupported claims about how every team works.
Workflow: People → Available hours → Allocation by week → Over-allocation flag → Rebalance
Derived values - calculate, never ask for and never accept as typed:
Utilisation % = Allocated Hours / Available Hours x 100, rounded once to the nearest whole number
Allocation Check = Over-allocated when Allocated Hours > Available Hours
Within capacity when Allocated Hours = Available Hours
Under-allocated when Allocated Hours < Available Hours
The percentage is stored as a whole number: 80 means 80%, never 0.8. Round once, at this
step for display only. Compare unrounded hours for the flag: 40.1/40 displays 100% but is still over-allocated. Do not let rounding hide excess demand. If Available Hours is 0 the ratio is undefined: leave Utilisation % andAllocation Check empty and flag the row for a human rather than dividing by zero or
defaulting to 0. A person on full leave has no capacity, which is not the same as having
spare capacity.
Approval gate: a week may only be Approved when capacity is positive and allocated hours do not exceed available hours; both Within capacity and Under-allocated may qualify.
An over-allocated week is a real finding, not a rounding error - raise it, do not approve it,
and do not quietly trim Allocated Hours to make it fit. Reallocate with the people affected,
or record why the over-allocation is accepted.
Once the user asks for it, derive the fields from the confirmed context and emit the
requested artifacts. For machine-readable text, keep prose outside the data; for files,
provide a usable link. Report material validation failures or limitations separately.
**A selected Notion output is rendered by notion-manual-import, so route the
Notion step there.** When the user selects Notion, hand that step to
@notion-manual-import: it holds the CSV, the property
mapping, the import steps and the verification checklist, and it renders the Field
Reference below instead of defining a table of its own. Do not restate the mapping
here and do not improvise the import steps. Manual CSV and mapping outputs need no
connection. For requested workspace changes, follow the shared contract: verify actual
tool access and the target before writing. A user saying "connected" is not tool evidence.
Never ask for a Notion password or token.
For an Excel-compatible CSV, use UTF-8 with a byte order mark so Excel opens the
text correctly. A CSV is not an .xlsx workbook; create .xlsx only when the user
requests a workbook.
A CSV carries no types, so after it, name the columns
that need a number, date or currency format applied.
Employee Name,Department,Project,Week Start,Available Hours,Allocated Hours,Utilisation %,Allocation Check,Leave Days,Status,Notes,Capacity ID
Example Employee,Delivery,Website Redesign,2026-01-05,32,38,119,Over-allocated,3,Draft,"Allocated 38 hours against 32 available, so this week needs a trade before it can be approved.",
CREATE TABLE capacity_workload_planner (
employee_name VARCHAR(255),
department VARCHAR(255),
project VARCHAR(255),
week_start DATE NOT NULL,
available_hours NUMERIC NOT NULL,
allocated_hours NUMERIC NOT NULL,
utilisation_pct NUMERIC,
allocation_check VARCHAR(100),
leave_days NUMERIC NOT NULL,
status VARCHAR(100) NOT NULL,
notes TEXT,
capacity_id SERIAL PRIMARY KEY,
created_at TIMESTAMP DEFAULT NOW(),
updated_at TIMESTAMP DEFAULT NOW(),
-- Utilisation and the check are derived, so they stay nullable: zero capacity is undefined, not zero.
CHECK (allocation_check IS NULL OR allocation_check IN ('Over-allocated', 'Within capacity', 'Under-allocated')),
-- An over-allocated week is a finding to escalate, not a plan to sign off.
CHECK (available_hours >= 0 AND allocated_hours >= 0 AND leave_days >= 0),
CHECK (status <> 'Approved' OR (available_hours > 0 AND allocated_hours <= available_hours
AND COALESCE(allocation_check IN ('Within capacity', 'Under-allocated'), FALSE)))
);
CREATE INDEX idx_capacity_workload_planner_status ON capacity_workload_planner (status);
CREATE INDEX idx_capacity_workload_planner_week_start ON capacity_workload_planner (week_start);
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"title": "Capacity Workload Planner",
"type": "object",
"additionalProperties": false,
"properties": {
"Employee Name": { "type": "string" },
"Department": { "type": "string" },
"Project": { "type": "string" },
"Week Start": { "type": "string", "format": "date" },
"Available Hours": { "type": "number" },
"Allocated Hours": { "type": "number" },
"Utilisation %": { "type": "number" },
"Allocation Check": { "type": "string" },
"Leave Days": { "type": "number" },
"Status": { "type": "string" },
"Notes": { "type": "string" },
"Capacity ID": { "type": "integer" }
},
"required": [
"Week Start",
"Available Hours",
"Allocated Hours",
"Leave Days",
"Status"
]
}
| CSV column | Notion property | Set after import |
|---|---|---|
| Employee Name | Title | Use as the database title |
| Department | Text | Leave as Text |
| Project | Text | Leave as Text |
| Week Start | Date | Convert to Date |
| Available Hours | Number | Convert to Number |
| Allocated Hours | Number | Convert to Number |
| Utilisation % | Number | Convert to Number, and do not type it - it is calculated from Allocated Hours / Available Hours |
| Allocation Check | Select (add options after import) | Convert to Select, add options: "Over-allocated", "Within capacity", "Under-allocated" |
| Leave Days | Number | Convert to Number |
| Status | Select (add options after import) | Convert to Select, add options: "Draft", "Approved", "Active", "Revised", "Closed". Approved is blocked while Allocation Check is Over-allocated |
| Notes | Text | Leave as Text |
| Capacity ID | Text (preserve source ID) | Keep imported IDs as Text; optionally add a separate Unique ID property |
The rows above are documentation examples only. Emit empty templates unless the user explicitly requests examples. Money stays currency, dates stay date,
and anything pointing at another table stays relation.
Aggregate allocations across all projects for the same person/week before comparing against their capacity; otherwise each project can appear safe while the total is over-allocated. Available Hours is net of agreed leave/non-project time; do not subtract leave twice. SQL columns are inputs unless the application enforces calculations: a Select property in Notion does not automatically compute or block approval. Implement and verify a formula/approval workflow in the target system rather than claiming the mapping enforces it.
| # | Field | Type | SQL | JSON Schema | Notion | CSV example |
|---|---|---|---|---|---|---|
| 1 | Employee Name | text | VARCHAR(255) | string | Text | Example Employee |
| 2 | Department | text | VARCHAR(255) | string | Text | Delivery |
| 3 | Project | text | VARCHAR(255) | string | Text | Website Redesign |
| 4 | Week Start | date | DATE | string, format: date | Date | 2026-01-05 |
| 5 | Available Hours | number | NUMERIC | number | Number | 32 |
| 6 | Allocated Hours | number | NUMERIC | number | Number | 38 |
| 7 | Utilisation % | number | NUMERIC | number | Number | 119 |
| 8 | Allocation Check | select | VARCHAR(100) | string | Select (add options after import) | Over-allocated |
| 9 | Leave Days | number | NUMERIC | number | Number | 3 |
| 10 | Status | select | VARCHAR(100) | string | Select (add options after import) | Draft |
| 11 | Notes | long_text | TEXT | string | Text | Allocated 38 hours against 32 available, so this week needs a trade before it can be approved. |
| 12 | Capacity ID | id | SERIAL PRIMARY KEY | integer | Text (preserve source ID) | (blank) |
Allocation Check
Over-allocated | Within capacity | Under-allocated
Calculated from unrounded allocated/available hours, not chosen. Leave empty when Available Hours is 0.
Status
Draft | Approved | Active | Revised | Closed
Approved is blocked while Allocation Check is Over-allocated.
Link fields: none
Prompt
We keep overcommitting and miss delivery dates.
Context first - one question per message, nothing already answered:
Q: Weekly hours?
A: 40.
Q: How many live projects?
A: Six.
Q: Do you plan weekly?
A: No, we guess.
Recommended next step - offered, not built:
Start with weekly planning when it fits the work, and flag over-allocation; use daily detail when shift or delivery constraints require it.
Workflow: People → Available hours → Allocation by week → Over-allocation flag → Rebalance
Want the CSV, SQL, JSON Schema and Notion mapping for this?
relation for anything that points at another table, text only for free text.currency, never text. Dates are date, never free text.External writes, messages, provisioning, and publication require authorization for that
action and target; existing explicit authorization does not need to be repeated.
the requested review needs; keep generated templates empty. Do not claim deletion
from the conversation or service storage.
is acted on.
Solution: deliver manual mappings without a connection; claim a live change only
after the authorized tool operation succeeds.
Solution: ask one, wait, and drop any the first answer already covered.
Solution: build what was requested; mention the parent skill separately.
Solution: derive all four from the field list in this file, never by hand.
Solution: a typed number disagreed with its own arithmetic, so an over-allocated week looked safe. Calculate Utilisation % and Allocation Check from the hours every time and let the approval gate block the week.
Solution: that is expected. Apply the property mapping table once, after import.
I want to set up resource management for my company.
Ask me one short question at a time, and only about what I have not already told you.
Then recommend the smallest setup that fits, and wait for me to ask before you build it.
When I ask, output CSV, SQL DDL, JSON Schema, a Notion property mapping or an Excel workbook. Data only.