docs: mention how updates work

Amolith created

Change summary

README.md | 11 +++++++++--
1 file changed, 9 insertions(+), 2 deletions(-)

Detailed changes

README.md 🔗

@@ -101,7 +101,14 @@ could be translated as "the way of work", "the doctrine of design", etc.
 - `np s` tells the model about the goal and task sub-commands and their flags
   and to begin the session by turning the user's request, bug report, issue
   contents, spec, etc. into a concise overarching goal with a thorough
-  description
+  description.
 - `np g s` accepts title and description arguments and tells the model to, if
   necessary, look around at additional relevant files before adding some tasks
-  with `np t a`. <mark>Would something like this work?</mark>
+  with `np t a`. <mark>How to provide/require/validate for pairs of -t and -d
+  flags?</mark>
+- Have the model update task statuses by ID and render the goal, the updated
+  task, and the _remaining_ tasks in the same format as planning-mcp-server. By
+  default, `planning-mcp-server` returned all tasks, but I think it would be
+  better to just return the modified one, so the model can see its previous
+  command worked, and the still-open ones. Include a flag or something so it can
+  look at all tasks including the completed ones.