Checklist and Log Generator

Short lists become useful records only when each line has a clear job. A verification list asks whether something is complete, an action list says what still needs doing, and a reading log leaves room to record progress or notes. Choosing the wrong shape can make finished work look open or turn a set of sources into an awkward task list.

The wording matters as much as the marker. “Server” is difficult to complete or verify, while “Confirm the backup completed” gives the reader an observable outcome. Reading entries work differently because a title, chapter, article, or link may be enough to identify what will be reviewed.

Order is often meaningful. A checklist may follow a runbook, a to-do list may reflect priority, and a reading log may follow a syllabus. Repeated lines can also be intentional when the same check occurs at different stages. Cleaning a list should remove blank space, not silently sort or deduplicate the work.

A generated draft is a starting document rather than proof that the source items are complete. Review vague rows, add owners or dates when they affect the handoff, and keep sensitive operational details out of a list that will be shared broadly.

How to Use This Tool:

Choose the document shape before editing the rows so the generated markers match how the list will be used.

1. Choose Checklist, To-do, or Reading log, then enter a title that will still make sense after the draft is copied elsewhere.
2. Enter one item per line. Use Trim lines when pasted text has uneven spacing; blank lines are removed, while order and duplicate items remain intact.
3. Add an optional Context line or Date label when the document needs an owner, project, week, or cycle. Check the generated draft before copying or downloading it.

Interpreting Results:

The item count reflects non-empty normalized lines, not unique items. Compare the generated draft with the source list when repeated entries may be accidental.

The item ledger shows the row order, generated role, and marker separately. Use it to catch a wrong document type or a line that does not read naturally in its new format.

Technical Details:

Each non-empty source line becomes exactly one output row. Leading and trailing whitespace is removed, internal runs of whitespace collapse to one space, and the surviving lines keep their original order. No sorting or deduplication occurs.

Transformation Core

The selected document shape determines the row marker and surrounding Markdown structure.

The title is emitted as a first-level Markdown heading. When context or a date label is present, the available values are joined with a centered dot on one italicized metadata line beneath the title. Vertical bars inside reading items are escaped so they do not split the Markdown table.

A valid draft requires a recognized mode, a non-empty title, and at least one non-empty item. The title accepts up to 120 characters, the complete item source up to 20,000 characters, the context line up to 160 characters, and the date label up to 80 characters.

Worked Examples: