What next?
I like to keep tasks in Markdown files. That way they can be interspersed within instructions, serving as reminders, FIXMEs, and other todos.
All the features for enhancing your task lists are discussed in detail in the documentation.
Document your tasks using an expanded version of the original GitHub task list notation:
- [ ] open, this task is outstanding
- [/] in progress, this task is partially complete
- [X] complete, this task has been finished
- [#] cancelled, this task has been scratched
- [<] blocked, this task needs more input
- [ ] _an important task_
# **Make apple pie from scratch**
- [ ] invent the universe
# Things for later
- [ ] get NYE fireworks tickets @2025-12-31
- [ ] but in the end it doesn't even matter @after
Then install whatnext:
pip install whatnext
Now run it and it'll tell you what's next, sorting by priority and state:
(computer)% whatnext
README.md:
# Make apple pie from scratch / HIGH
- [ ] invent the universe
README.md:
# What next? / MEDIUM
- [ ] an important task
README.md:
# Things for later / IMMINENT 6d
- [ ] get NYE fireworks tickets
README.md:
# What next?
- [/] in progress, this task is partially complete
- [ ] open, this task is outstanding
- [<] blocked, this task needs more input
Also provided, next to add tasks to files.
# by default, adds to $HOME/tasks.md
(computer)% next Add more features to whatnext
Updated tasks.md
Metadata
Release files for whatnext 3.5.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| whatnext-3.5.1.tar.gz | 65.8 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| whatnext-3.5.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 88.5 kB
Release files / whatnext-3.5.1.tar.gz
| Download URL | whatnext-3.5.1.tar.gz |
|---|---|
| Size | 65.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9f02523b62a048beb94f6dc00abd1cc88f7eb0e83d569669a7159ccb096626c0
|
|
BLAKE2b-256 checksum How to use checksums |
d7b254f7fdbf0f966113f69ddd6c8ae46afbd5a25046bd9c781dc4a3c1511606
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 16, 2026.
Transparency logRelease files / whatnext-3.5.1-py3-none-any.whl
| Download URL | whatnext-3.5.1-py3-none-any.whl |
|---|---|
| Size | 22.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
567993becb313e7d744483b0d6d14f928d719562d267203943f8798ef33c9a78
|
|
BLAKE2b-256 checksum How to use checksums |
cd47f984c21b0b65196020a087f618141abf7ca97d082dadcca39742f792f5f0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 16, 2026.
Transparency log