@@ -84,6 +84,10 @@ EOF
)"
</formatted-commit_example>
+## Planning before acting
+
+IMPORTANT: When I ask you to plan first, I want you to first slow down and make sure you're taking your time and deliberating prior to jumping in and fulfilling my request. You'll need to look around at any mentioned files, or explore them to identify which are relevant, prior to deciding on a course of action. Only once you've broken the request down and have a solid idea what changes are necessary should you fill out your task list. Once you've made the plan, stop and ask me to review it. Once I explicitly confirm, you may get started.
+
## Preferred tooling
### git-bug
@@ -102,13 +106,40 @@ I like using a bug tracker that embeds bugs and identities and conversations dir
- `git bugs-pull`
- `git bugs-push`
-### nasin pali (the way of work)
+### lune (Lunatask CLI)
-IMPORTANT: If I ask you to `use np` or `use nasin pali` or some variation, you must completely ignore your built-in TODO tools and follow _nasin pali_ by immediately running the appropriate `np` subcommand and adhering its instructions. If I've asked you to use it, start a session by running `np s`. If I've explicitly asked you to resume, use `np r`. Ask me whether to archive when you're done; do NOT do it on your own. If I haven't asked you to follow _nasin pali_, prefer your built-in tools, if any, and proceed normally.
+CLI for Lunatask (E2E encrypted productivity app). Names/contents are write-only due to encryption.
-### Planning before acting
+**Conventions:** Resources accept UUIDs or `lunatask://` deeplinks as IDs, config keys for areas/goals/habits/notebooks, `-` for stdin, natural language for dates, and Markdown for content.
-IMPORTANT: When I ask you to plan first, I want you to first slow down and make sure you're taking your time and deliberating prior to jumping in and fulfilling my request. You'll need to look around at any mentioned files, or explore them to identify which are relevant, prior to deciding on a course of action. Only once you've broken the request down and have a solid idea what changes are necessary should you fill out your task list. Once you've made the plan, stop and ask me to review it. Once I explicitly confirm, you may get started.
+Task notes are useful for storing context/prompts for future agent sessions—use a `TASK_ID` placeholder, then update with the real ID so agents can track progress.
+
+```bash
+lune task add "Name" -a AREA -g GOAL -n "note" -s next
+lune task update ID -s completed
+lune jrnl "Entry" # or: lune journal add -d yesterday
+lune habit track KEY -d "2 days ago"
+lune note add "Title" -b NOTEBOOK -c - < content.md
+```
+
+If I specify an area but not a goal, check `lune goal list -a AREA` first.
+
+#### Area workflows
+
+Only provide flags necessary to express the workflow; they're not all compatible.
+
+- Work: kanban
+ - later (default)
+ - waiting (on someone, something, etc.)
+ - next
+ - started
+ - completed
+- Personal: now/later
+ - later (default)
+ - started
+ - completed
+- Projects: kanban
+- Some day: nothing but priority
### Use `fish -c 'doc-agent'` for supported doc sets