@docyrus/docyrus 0.0.39 → 0.0.41

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -246,6 +246,10 @@ When `docyrus/knowledge/` exists, `docyrus agent`, `docyrus coder`, and `docyrus
246
246
  - `docyrus_knowledge_expand`
247
247
  - `docyrus_knowledge_check`
248
248
 
249
+ When `docyrus/project-plan/project-plan.json` exists, `docyrus agent`, `docyrus coder`, and `docyrus server` also load:
250
+
251
+ - `project_task`
252
+
249
253
  Inside the interactive agent TUI:
250
254
 
251
255
  ```bash
@@ -256,6 +260,7 @@ Inside the interactive agent TUI:
256
260
  /end-architect # alias for leaving an architect planning session
257
261
  /plan-policy # show the effective planning-model policy and the resolved planning model
258
262
  /architect [brief] # discover tenant data sources and generate local planning artifacts under ./docyrus/architecture/
263
+ /tasks # browse the canonical project-plan sections, features, and tasks
259
264
  ```
260
265
 
261
266
  When running through `docyrus server`, `/plan` and `/architect` can be sent through `/api/chat` as normal chat input. If clarification is needed, the server emits a synthetic `ask_user` client tool. Frontends using AI SDK `useChat` should render that tool and submit structured answers back with `addToolOutput`.