nagiworks.

v0.3.0 · Available

Existing-CSV Weekly Report Automation Kit

Keep your existing CSV, map it once, and reuse the setup every week

Keep your existing CSV, map it once, and reuse the setup every week

This Windows PowerShell kit maps the headers and values in a local task CSV once, saves the setup, and creates a Markdown report from the fields that actually exist.

The problem

Rebuilding the same weekly summary from an existing task CSV.

Who it is for

Small teams and managers using Windows and PowerShell 7.2 or later, with a person reviewing each report.

The outcome

A reusable mapping and a reviewable Markdown task report—not another mandatory CSV template.

See the local workflow

Browser view of the Markdown weekly report generated from the included fictional five-task CSV
Actual Markdown output generated from the included fictional five-task CSV.

How it works

  1. Extract the ZIP and run a fictional sample.
  2. Map your task-name and status columns and values; save mapping.json.
  3. Reuse that mapping on a compatible weekly CSV.
  4. Review the Markdown report before sharing.

Included

  • Japanese and English header, status, and priority mapping
  • Optional owner, due date, priority, and effort fields
  • Four fictional examples and a functional self-test

Your data, on your device

No network calls, cloud uploads, email, or chat messages. Refuses to overwrite the input CSV. Mapping and report files are saved locally.

Know the limits

Windows with PowerShell 7.2+; not Windows PowerShell 5.1. One CSV, at most 5,000 rows. No direct .xlsx, multi-file joins, custom calculations, scheduling, cloud sync, or automatic sending. Compatibility and time savings are not guaranteed.

Questions, answered

Must I rename my columns every week?

The kit saves a mapping for a compatible CSV structure. A changed export may need mapping updates.

What are the minimum fields?

A task-name column and a status column. Unknown required fields or status values stop processing instead of being guessed.

Is this a web app?

No. The paid kit runs locally on Windows with PowerShell 7.2 or later.

Can support build a custom integration?

No. Support is asynchronous and text-only; customization and consulting are not included.