From 8924ed97c8093fa2d6c3c9b3bff829a414561a08 Mon Sep 17 00:00:00 2001 From: Amolith Date: Wed, 22 Oct 2025 13:07:19 -0600 Subject: [PATCH] docs: fix startup desc --- README.md | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) diff --git a/README.md b/README.md index 6c6709c901011bf7593f97dca4746f73c7d9178b..e405557bb101b04325775ce9d15db45ab822ea91 100644 --- a/README.md +++ b/README.md @@ -46,12 +46,13 @@ you know will be relevant as possible. Mention particular symbols, paste snippets of code, etc. Once your prompt looks good, send it off. In the `np` section of the model's rules, we'll have instructions to -_immediately_ set an overarching goal with `np g s -t title -d description` that -captures the operator's request, combining the information from the ticket and -any extra operator-provided context. It should then go off and look at the -provided references and thoroughly consider how to go about resolving the goal. -After gathering that context, it adds tasks with `np t a -t title -d description --t title2 -d description2` and gets started on them. +_immediately_ run `np s`, which outputs some LLM-oriented instructions for use. +It first tells the model to set an overarching goal with `np g s -t title -d +description` that captures the operator's request, combining the information +from the ticket and any extra operator-provided context. Then it should go off +and look at the provided references and thoroughly consider how to go about +resolving the goal. After gathering that context, it adds tasks with `np t a -t +title -d description -t title2 -d description2` and gets started on them. As it works through the tasks, it's expected to update statuses by ID with something like `np t u -i id -s status`. Commands that modify the model's plan