@compilr-dev/sdk 0.10.41 → 0.11.0

package/dist/skills/software-skills.js

@@ -60,10 +60,14 @@ When you have enough information:
    - Nice-to-haves (type: feature, priority: medium/low)
    - Technical setup tasks (type: chore, priority: high)
    - Known risks/unknowns (type: tech-debt, priority: medium)
-4. Update the PRD.md file with gathered requirements:
-   - Use the edit tool to update PRD.md (located in .compilr/requirements/PRD.md or {project}-docs/00-requirements/PRD.md)
+4. Save the PRD to the project DATABASE (never a file):
+   - Check for an existing PRD first: project_document_get({ doc_type: "prd" })
+   - If none exists, create it:
+     project_document_add({ doc_type: "prd", title: "Product Requirements Document", content: "<full markdown>" })
+   - If one exists, update it section by section:
+     project_document_patch({ doc_type: "prd", operation: "replace_section", section_heading: "## <heading>", content: "..." })
    - Fill in: Problem Statement, Goals, User Stories, Functional Requirements
-   - Keep the existing structure, just replace placeholder text
+   - CRITICAL: project documents live in the database. NEVER use write_file / edit / bash mkdir to create a PRD.md file on disk.
 5. Present the backlog and PRD summary to user for confirmation
    - If CHORE-001 was added, mention: "Run /scaffold to create the project foundation"
 6. If the project involves managing entities (CRUD operations on things like users, orders, products):
@@ -83,7 +87,7 @@ When you have enough information:
 ✓ MVP features are defined
 ✓ Backlog has 5-15 items
 ✓ For fresh projects: CHORE-001 scaffolding item is first (critical priority)
-✓ PRD.md is populated with requirements
+✓ PRD saved to the database (doc_type: prd) — not written to a file
 ✓ If entity-based: user informed about /scaffold auto-generation
 ✓ User has approved the backlog`,
     tags: ['planning', 'requirements'],
@@ -440,11 +444,12 @@ export const prdSkill = defineSkill({
    - "Read current PRD"
    - "Identify section to update"
    - "Gather updates"
-   - "Write updated PRD"
+   - "Save updated PRD"
 
-2. Read the existing PRD.md:
-   - Location: .compilr/requirements/PRD.md or {project}-docs/00-requirements/PRD.md
-   - If no PRD exists, inform the user to run /design first
+2. Read the existing PRD from the project DATABASE:
+   - Use project_document_get({ doc_type: "prd" })
+   - If it returns no document, inform the user to run /design first
+   - The PRD is a database document, NOT a file — never read PRD.md from disk
 
 3. Present current PRD sections to user using ask_user_simple:
    - Question: "Which section would you like to update?"
@@ -482,21 +487,23 @@ Based on section selected:
    - What to add/change
    - What to remove
    - Any clarifications
-3. Use the edit tool to update PRD.md
+3. Save the change to the database with project_document_patch:
+   - project_document_patch({ doc_type: "prd", operation: "replace_section", section_heading: "## <heading>", content: "..." })
+   - Use operation "append" / "prepend" to add new content without replacing
 4. Show the updated section for confirmation
 
 ## RULES
 
-1. ALWAYS read the existing PRD first
+1. ALWAYS read the existing PRD first (project_document_get)
 2. Use ask_user_simple for section selection
 3. Use ask_user for gathering detailed updates
-4. Preserve sections you're not updating
-5. Use edit tool (not write_file) to update specific sections
+4. Preserve sections you're not updating (patch one section at a time)
+5. CRITICAL: the PRD lives in the database. Save with project_document_patch / project_document_add — NEVER write_file / edit / a PRD.md file on disk
 6. Keep formatting consistent with existing document
 7. If scope changes affect backlog, suggest running /refine
 
 ## COMPLETION CRITERIA
-✓ PRD.md is updated with changes
+✓ PRD is updated in the database (doc_type: prd)
 ✓ User has reviewed the updates
 ✓ Related backlog updates are suggested if needed`,
     tags: ['planning', 'requirements'],
@@ -532,7 +539,7 @@ export const sessionNotesSkill = defineSkill({
 
 ## SESSION NOTE STRUCTURE
 
-Create a markdown file with this structure:
+Compose a markdown note with this structure (it will be saved to the database, not a file):
 
 \`\`\`markdown
 # Session Note - {{title}}
@@ -573,13 +580,12 @@ Create a markdown file with this structure:
 *Generated by /note*
 \`\`\`
 
-## FILE LOCATION
+## WHERE TO SAVE
 
-Save the note to:
-- Single repo: \`.compilr/sessions/{{YYYY-MM-DD}}-{{slug}}.md\`
-- Two repo: \`{{project}}-docs/04-session-notes/{{YYYY-MM-DD}}-{{slug}}.md\`
+Save the note to the project DATABASE with:
+  project_document_add({ doc_type: "notes", title: "Session Note — {{title}}", content: "<full markdown>" })
 
-Create the directory if it doesn't exist.
+CRITICAL: session notes are database documents. NEVER write a .md file (no write_file / edit / bash mkdir, no .compilr/sessions/ or {{project}}-docs/ paths).
 
 ## RULES
 
@@ -591,7 +597,7 @@ Create the directory if it doesn't exist.
 6. If user provides a title, use it; otherwise generate one from the summary
 
 ## COMPLETION CRITERIA
-✓ Session note file is created
+✓ Session note saved to the database (doc_type: notes)
 ✓ All sections are filled in
 ✓ User has reviewed the note`,
     tags: ['documentation', 'session'],

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@compilr-dev/sdk",
-  "version": "0.10.41",
+  "version": "0.11.0",
   "description": "Universal agent runtime for building AI-powered applications",
   "type": "module",
   "main": "dist/index.js",