@docyrus/docyrus 0.0.43 → 0.0.44

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@docyrus/docyrus",
-  "version": "0.0.43",
+  "version": "0.0.44",
   "private": false,
   "description": "Docyrus API CLI",
   "main": "./main.js",

package/resources/pi-agent/extensions/tasks.ts

@@ -11,6 +11,7 @@ import { Text } from "@mariozechner/pi-tui";
 type ITasksAction =
   | "show"
   | "get"
+  | "create-section"
   | "create-feature"
   | "create-task"
   | "set-status"
@@ -53,9 +54,10 @@ interface IProjectFeatureSummary {
 }
 
 interface IProjectSectionSummary {
-  sectionId: string;
-  heading: string;
-  filePath: string;
+  id: string;
+  title: string;
+  slug: string;
+  summary: string;
   status: string;
   featureCount: number;
   taskCount: number;
@@ -72,6 +74,7 @@ const TaskParams = Type.Object({
   action: StringEnum([
     "show",
     "get",
+    "create-section",
     "create-feature",
     "create-task",
     "set-status",
@@ -79,10 +82,10 @@ const TaskParams = Type.Object({
   ] as const),
   taskId: Type.Optional(Type.String({ description: "Canonical task id" })),
   featureId: Type.Optional(Type.String({ description: "Canonical feature id" })),
-  sectionId: Type.Optional(Type.String({ description: "Knowledge section id" })),
-  title: Type.Optional(Type.String({ description: "Feature or task title" })),
-  summary: Type.Optional(Type.String({ description: "Feature or task summary" })),
-  slug: Type.Optional(Type.String({ description: "Feature slug" })),
+  sectionId: Type.Optional(Type.String({ description: "Project plan section id" })),
+  title: Type.Optional(Type.String({ description: "Section, feature, or task title" })),
+  summary: Type.Optional(Type.String({ description: "Section, feature, or task summary" })),
+  slug: Type.Optional(Type.String({ description: "Section or feature slug" })),
   type: Type.Optional(Type.String({ description: "Task type" })),
   assignee: Type.Optional(Type.String({ description: "Task assignee" })),
   status: Type.Optional(Type.String({ description: "Task status" })),
@@ -175,7 +178,7 @@ function formatHierarchySummary(payload: IProjectPlanShowPayload): string {
 
   const lines: string[] = [];
   for (const section of populatedSections) {
-    lines.push(`${section.heading} (${section.status})`);
+    lines.push(`${section.title} (${section.status})`);
     for (const feature of section.features) {
       lines.push(`  - ${feature.title} (${feature.status})`);
       for (const task of feature.tasks) {
@@ -212,21 +215,21 @@ async function tasksCommandHandler(pi: ExtensionAPI, ctx: ExtensionCommandContex
 
   const query = rawArgs.trim().toLowerCase();
   const sections = payload.hierarchy.sections.filter((section) => section.features.length > 0)
-    .filter((section) => !query || section.heading.toLowerCase().includes(query) || section.sectionId.toLowerCase().includes(query));
+    .filter((section) => !query || section.title.toLowerCase().includes(query) || section.id.toLowerCase().includes(query));
   if (sections.length === 0) {
     ctx.ui.notify("No project-plan sections with tasks were found.", "info");
     return;
   }
 
   const selectedSectionId = await selectFromOptions(ctx, "Project Sections", sections.map((section) => ({
-    label: `${section.heading} (${section.status})`,
-    value: section.sectionId,
+    label: `${section.title} (${section.status})`,
+    value: section.id,
   })));
   if (!selectedSectionId) {
     return;
   }
 
-  const section = sections.find((item) => item.sectionId === selectedSectionId);
+  const section = sections.find((item) => item.id === selectedSectionId);
   if (!section) {
     return;
   }
@@ -361,6 +364,32 @@ export default function tasksExtension(pi: ExtensionAPI) {
           };
         }
 
+        case "create-section": {
+          if (!params.title) {
+            return {
+              content: [{ type: "text", text: "title required" }],
+              isError: true,
+            };
+          }
+          const args = [
+            "project-plan",
+            "upsert-section",
+            "--title",
+            String(params.title),
+          ];
+          if (params.slug) {
+            args.push("--slug", String(params.slug));
+          }
+          if (params.summary) {
+            args.push("--summary", String(params.summary));
+          }
+          const payload = await runCliJson<Record<string, unknown>>(environment, args, ctx.cwd);
+          return {
+            content: [{ type: "text", text: JSON.stringify(payload, null, 2) }],
+            details: payload,
+          };
+        }
+
         case "create-feature": {
           if (!params.sectionId || !params.title) {
             return {

package/resources/pi-agent/prompts/agent-system.md

@@ -27,11 +27,12 @@ Docyrus concepts you should understand and use accurately:
 
 Project plan system:
 
-The project-plan is a repo-tracked work graph stored at `docyrus/project-plan/project-plan.json`. It organizes work into sections (anchored to knowledge graph section IDs), features, and tasks. A derived `PROJECT_PLAN.md` is always kept in sync.
+The project-plan is a repo-tracked work graph stored at `docyrus/project-plan/project-plan.json`. It organizes work into sections (standalone groupings like phases or feature areas), features, and tasks. A derived `PROJECT_PLAN.md` is always kept in sync. Features are also synced into the knowledge base features document when it exists.
 
 - `docyrus project-plan show` — view the full hierarchy with statuses
 - `docyrus project-plan get-task --taskId <id>` — inspect a task and its linked local subtasks
 - `docyrus project-plan set-task-status --taskId <id> --status <status>` — advance task status (`planned` → `in_progress` → `done`, or `blocked`)
+- `docyrus project-plan upsert-section --title <title>` — create or update a section
 - `docyrus project-plan check` — validate that all section references and task fields are consistent
 
 When working on a repo that has a project plan, read it at the start of a session to understand scope and priorities. Update task status as work progresses and after it completes.

package/resources/pi-agent/prompts/coder-system.md

@@ -72,7 +72,7 @@ Schema-first workflow for new Docyrus-backed apps and major features:
 
 Project plan system:
 
-The project-plan is a repo-tracked work graph stored at `docyrus/project-plan/project-plan.json` with a derived `PROJECT_PLAN.md` always kept in sync. Work is organized into sections (anchored to knowledge graph section IDs), features, and tasks. Tasks have a type (`new-implementation`, `bug-fix`, `api-test`, `browser-automation-test`, `work`), an assignee (`agent` or `user`), a status (`planned`, `in_progress`, `blocked`, `done`), and optional acceptance criteria.
+The project-plan is a repo-tracked work graph stored at `docyrus/project-plan/project-plan.json` with a derived `PROJECT_PLAN.md` always kept in sync. Work is organized into sections (standalone groupings like phases or feature areas), features, and tasks. Features are also synced into the knowledge base features document when it exists. Tasks have a type (`new-implementation`, `bug-fix`, `api-test`, `browser-automation-test`, `work`), an assignee (`agent` or `user`), a status (`planned`, `in_progress`, `blocked`, `done`), and optional acceptance criteria.
 
 Key commands:
 
@@ -80,10 +80,11 @@ Key commands:
 - `docyrus project-plan get-task --taskId <id>` — inspect a specific task and its linked local subtasks
 - `docyrus project-plan set-task-status --taskId <id> --status <status>` — advance task status
 - `docyrus project-plan create-linked-todo --taskId <id> --title <title> --body <body>` — create a local `.pi/todos` subtask linked to an agent-assigned canonical task
+- `docyrus project-plan upsert-section --title <title> --slug <slug> --summary <summary>` — create or update a section
 - `docyrus project-plan upsert-feature --sectionId <id> --title <title> --slug <slug>` — create or update a feature
 - `docyrus project-plan upsert-task --featureId <id> --title <title> --type <type> --assignee <assignee>` — create or update a task
 - `docyrus project-plan check` — validate section references and graph integrity
-- `docyrus project-plan ensure` — initialize the graph from knowledge sections if it does not yet exist
+- `docyrus project-plan ensure` — initialize an empty project-plan graph if it does not yet exist
 
 Workflow: read the project plan at session start → set relevant tasks to `in_progress` before beginning → create linked todos for complex implementation tasks → set tasks to `done` after work is verified.