{{ summaryTitle }}
{{ summaryPrimary }}
{{ summaryLine }}
{{ badge.label }}
Pick the output shape before editing the title and source item lines.
Use the list, task set, habit, or reading project name readers should see first.
{{ itemHelp }}
{{ itemStatus }}
Leave blank for a compact draft with only the heading and generated rows.
Use this for print handoffs or weekly logs; leave blank to omit it.
{{ draftText }}
{{ header }} Copy
{{ cell }}
No rows are available
Add at least one source item before exporting this table.
Tags: Productivity, Text
Survey Questions Generator Draft survey questions from a research goal, audience, topic areas, and response mix, with fatigue cues, type balance, and pilot checks.
Acceptance Criteria Generator Draft acceptance criteria from a story, actor, behaviors, and edge cases, then review Gherkin scenarios, checklist gaps, and JSON exports.
Interview Questions Generator Build an interview guide from a role or research brief with tailored questions, follow-up probes, scoring anchors, risk checks, and exports.
Risk Register Generator Build a risk register from pasted rows or CSV, score inherent and residual exposure, and queue owner gaps, high risks, and review dates.
Customize
Advanced
:

A list loses value when the next reader cannot tell whether a line is an action to finish, a step to verify, or a source to review. The same short notes can become three different working documents: a checklist for confirmation, a to-do list for open work, or a reading log for sources and follow-up notes.

Reliable lists separate the item from the format. First write the item clearly, then choose the structure that matches how the list will be used. A maintenance handoff may need checkbox rows because completion matters. A status message may read better as plain action bullets. A class, research, or team reading cycle needs room for status and notes so readers remember what was reviewed and what still needs attention.

Format Best Fit Row Wording That Works Common Mistake
Checklist Completion or verification Concrete items that can be marked done or checked off. Using vague nouns that do not say what must be verified.
To-do list Open actions and handoffs Short task statements, often starting with a verb. Mixing reminders, decisions, and finished work in the same list.
Reading log Study, research, or source review Titles, chapters, articles, links, or assigned sources. Treating a source title like a task and losing room for notes.

A short owner, class, project, or period note can matter as much as the rows themselves. Lists often travel through chat, documents, notebooks, tickets, and printouts. Once a list is separated from the conversation that created it, a title and context line keep the rows tied to the right handoff or review period.

Plain item lines flow into checklist, to-do list, or reading log formats and review rows.

Automation can make the structure consistent, but it cannot decide what the item meant. A row such as invoice may be a task, a document to read, or a reminder to verify payment. Clear wording before formatting is what makes the final list trustworthy.

How to Use This Tool:

Start with the list shape, then clean the source lines before copying or downloading the generated result.

  1. Set Draft type to Checklist, To-do, or Reading log. The summary badge should change to the selected format.
  2. Enter a Title that will still make sense after the draft is copied into a note, ticket, worksheet, or message.
  3. Paste one entry per line in Items. Empty lines are ignored, and the item count in the summary shows how many usable rows are ready.
  4. Use Context line and Date label in Advanced when the draft needs an owner, project, class, week, or review cycle.
  5. Use Sample to restore the default example, or Trim lines after pasting text with stray spaces and blank rows.
  6. Read Checklist Draft for the final text, then use Item Ledger and Draft Review to confirm that each source line became one intended row.
  7. Use Source Coverage, CSV table exports, DOCX table exports, and JSON when you need a structured handoff record rather than only the finished draft text.

If the summary says 0 item(s) or a table says no rows are available, add at least one non-empty item line. If the generated draft looks technically correct but unclear, revise the item wording before sharing it.

Interpreting Results:

The item count is the first confidence check. It should match the number of real lines you expected after blank rows and extra spacing were removed. The selected draft type tells you how those rows were interpreted: checklist items, action bullets, or reading-log entries.

Result View What It Means Verification Cue
Checklist Draft The generated text in the selected format. Check the title, optional context, date label, and row wording before copying.
Item Ledger A row-by-row account of the source items. Confirm the ledger row count matches the summary count.
Source Coverage A mode sanity check showing how checklist, to-do, and reading-log patterns relate to the selected output. Use it to catch a draft type that does not match the handoff goal.
Draft Review Practical checks for item coverage, format choice, export readiness, and missing handoff context. Resolve any review row marked optional or review-worthy before sharing.
JSON A structured version of the same draft, counts, settings, and item rows. Use it only when another workflow needs structured data.

A clean draft can still give false confidence. The generator does not know whether update means update a document, a tracker, a server, or a student note. Treat the generated rows as formatting output, then use the Item Ledger and Draft Review to catch unclear wording, missing context, or the wrong draft type.

Technical Details:

Structured list generation is a deterministic text transformation. The governing unit is a non-empty item line. Spacing inside each line is normalized, blank lines are discarded, and the remaining lines keep their original order because sequence often carries meaning in routines, readings, and handoffs.

The transformation is intentionally conservative. It does not infer owners, priorities, due dates, dependency order, or completion status from the wording. That prevents a short text formatter from assigning intent that the source lines did not state.

Transformation Core:

Each normalized item line maps to one generated row. The selected draft type changes the row wrapper, not the order of the underlying items.

Draft Type Generated Row Shape Technical Meaning
Checklist - [ ] followed by the item text. The row is an unchecked Markdown task suitable for completion tracking.
To-do - followed by the item text. The row is a plain bullet and carries no checkbox state.
Reading log A Markdown table row with number, reading item, blank notes, and Not started status. The item is treated as a source or assignment, not as an action command.
Context and date label Non-empty values are placed near the top of the draft under the title. They preserve owner, period, project, or class context without changing item rows.

Rule Core:

The important boundaries are row normalization and fallback behavior. These rules explain why a pasted block may produce fewer rows than the visible number of text lines.

Condition Behavior Review Impact
Leading, trailing, or repeated internal spacing The item is trimmed and repeated whitespace becomes a single space. Pasted lines become cleaner without changing their order.
Blank lines They are ignored and do not create ledger rows. The summary count may be lower than the raw line count.
Duplicate item text Duplicates remain separate rows. Repeated inspections, readings, or routines are not silently removed.
No usable item lines The draft shows a placeholder row, while item tables have no source rows. Add a real item before treating the output as share-ready.
Vertical bar in reading-log text The character is escaped in the generated Markdown table. The reading-log columns stay aligned when a title contains |.

A simple mechanism path is: source text is split into lines, each line is cleaned, empty lines are removed, and the remaining ordered list is wrapped in the selected row format. The Item Ledger is useful because its first row corresponds to the first usable item line, its second row corresponds to the second usable item line, and so on.

Worked Examples:

Weekly review checklist. With the title Weekly Review and the item lines Review notes, Update priorities, and Share follow-up, Checklist mode creates three unchecked rows in Checklist Draft. Item Ledger should also show three rows.

Operations handoff. A title such as Router Maintenance, a context line of Owner: Network team, and To-do mode turn lines like Confirm backup and Send maintenance notice into plain bullets. Draft Review should show that handoff context is present.

Reading cycle. In Reading log mode, lines such as Chapter 4: Switching Basics and RFC excerpt on addressing become table rows with blank notes and Not started status. Add a date label when the log belongs to a weekly class, study group, or review period.

Blank paste cleanup. If a copied note block contains blank lines and extra indentation, Trim lines removes the spacing noise. If the summary still says 0 item(s), the pasted text did not contain any non-empty item lines and must be replaced before export.

FAQ:

Why did blank lines disappear?

Blank lines are ignored so copied notes do not create empty checklist items, blank action bullets, or empty reading-log rows.

Can the generator add priorities or due dates?

No. Priorities, owners, due dates, and dependencies must be written into the item text or added after export.

What belongs in Reading log mode?

Use titles, chapters, articles, URLs, assigned texts, or research sources. The generated rows leave notes blank and start the status as Not started.

Why are duplicate rows kept?

Duplicates may be intentional in recurring routines or repeated reading assignments. Edit the Items box if a duplicate was accidental.

What should I check before sharing the draft?

Compare the summary count with Item Ledger, review Draft Review for missing context, and read Checklist Draft as the recipient would read it.

Glossary:

Checklist
A list of items meant to be verified, completed, or checked off.
To-do list
A list of open actions, usually written as concise task statements.
Reading log
A record of readings, sources, notes, and progress status.
Item Ledger
The row-by-row table used to confirm each source item became one generated row.
Source Coverage
The result view that compares the selected draft type with checklist, to-do, and reading-log patterns.
Draft Review
The result view that flags practical checks such as item coverage and missing handoff context.

References: