Metadata-Version: 2.4
Name: whatnext
Version: 0.0.1
Summary: A lister of tasks found in Markdown files
Author: Mark Norman Francis
License-Expression: MIT
Project-URL: Homepage, https://github.com/norm/whatnext
Project-URL: Repository, https://github.com/norm/whatnext
Project-URL: Documentation, https://github.com/norm/whatnext
Keywords: cli,markdown,tasks,todo
Classifier: Development Status :: 3 - Alpha
Classifier: Programming Language :: Python :: 3.10
Classifier: Programming Language :: Python :: 3.11
Classifier: Programming Language :: Python :: 3.12
Requires-Python: >=3.10
Description-Content-Type: text/markdown
License-File: LICENCE
License-File: LICENSE
Requires-Dist: toml
Provides-Extra: test
Requires-Dist: flake8; extra == "test"
Requires-Dist: pytest; extra == "test"
Dynamic: license-file

# What next?

Document your tasks in Markdown files, using ["standard"][sn] notation:

```markdown
- [ ] empty, this task is outstanding
- [X] crossed, this task has been completed
```

Then install `whatnext`:

```bash
pip install whatnext
```

Now run it and it'll tell you what's next:

```bash
(computer)% whatnext
README.md:
    # What next?
    - [ ] empty, this task is outstanding
```

More detail to be found:

- [The basics of task formatting](docs/basics.md)
- [whatnext usage and arguments](docs/usage.md)
- [The `.whatnext` file](docs/dotwhatnext.md)


## The reason

I like to keep tasks in Markdown files. That way they can be interspersed
within instructions, serving as reminders, FIXMEs, and other todos.


[sn]: https://blog.github.com/2013-01-09-task-lists-in-gfm-issues-pulls-comments/
