@compilr-dev/sdk 0.5.7 → 0.5.9

package/dist/index.d.ts

@@ -61,7 +61,7 @@ export type { AskUserQuestion, AskUserInput, AskUserResult, AskUserHandler, AskU
 export { createPlatformTools, createProjectTools, createWorkItemTools, createDocumentTools, createPlanTools, createBacklogTools, createAnchorTools, createArtifactTools, createEpisodeTools, ProjectAnchorStore, } from './platform/index.js';
 export type { ProjectAnchorStoreConfig } from './platform/index.js';
 export { STEP_ORDER, GUIDED_STEP_CRITERIA, getNextStep, isValidTransition, getStepCriteria, formatStepDisplay, getStepNumber, } from './platform/index.js';
-export { platformSkills, designSkill, sketchSkill, prdSkill, refineSkill, refineItemSkill, architectureSkill, sessionNotesSkill, buildSkill, scaffoldSkill, outlineSkill, literatureReviewSkill, draftSectionSkill, } from './skills/index.js';
+export { platformSkills, designSkill, sketchSkill, prdSkill, refineSkill, refineItemSkill, architectureSkill, sessionNotesSkill, buildSkill, scaffoldSkill, outlineSkill, literatureReviewSkill, draftSectionSkill, peerReviewSkill, researchScaffoldSkill, } from './skills/index.js';
 export { ACTION_REGISTRY, getActionsForContext, getActionById, resolveActionPrompt, buildContextSummary, getSuggestedRole, } from './actions/index.js';
 export type { ActionContext, ActionDefinition } from './actions/index.js';
 export { PROJECT_TYPES, getProjectTypeConfig, getProjectTypesByCategory, generalConfig, softwareConfig, researchConfig, businessPlanConfig, contentConfig, techDocsConfig, courseConfig, } from './project-types/index.js';

package/dist/index.js

@@ -139,7 +139,7 @@ export { STEP_ORDER, GUIDED_STEP_CRITERIA, getNextStep, isValidTransition, getSt
 // =============================================================================
 // Platform Skills (platform-specific prompt expansions)
 // =============================================================================
-export { platformSkills, designSkill, sketchSkill, prdSkill, refineSkill, refineItemSkill, architectureSkill, sessionNotesSkill, buildSkill, scaffoldSkill, outlineSkill, literatureReviewSkill, draftSectionSkill, } from './skills/index.js';
+export { platformSkills, designSkill, sketchSkill, prdSkill, refineSkill, refineItemSkill, architectureSkill, sessionNotesSkill, buildSkill, scaffoldSkill, outlineSkill, literatureReviewSkill, draftSectionSkill, peerReviewSkill, researchScaffoldSkill, } from './skills/index.js';
 // =============================================================================
 // Contextual Actions (skill invocations with context)
 // =============================================================================

package/dist/project-types/configs.js

@@ -154,7 +154,7 @@ export const researchConfig = {
         { type: 'bibliography', label: 'Bibliography', description: 'References and citations' },
         { type: 'session-notes', label: 'Session Notes', description: 'Summary of work done' },
     ],
-    projectActions: ['outline', 'literature-review', 'draft-section', 'session-notes'],
+    projectActions: ['research-scaffold', 'outline', 'literature-review', 'draft-section', 'peer-review', 'session-notes'],
     workItemActions: ['draft-section', 'explain'],
     workItemLabels: {
         feature: { short: 'SC', full: 'Section' },

package/dist/skills/index.d.ts

@@ -1,4 +1,4 @@
 /**
  * Platform Skills — barrel export
  */
-export { platformSkills, designSkill, sketchSkill, prdSkill, refineSkill, refineItemSkill, architectureSkill, sessionNotesSkill, buildSkill, scaffoldSkill, outlineSkill, literatureReviewSkill, draftSectionSkill, } from './platform-skills.js';
+export { platformSkills, designSkill, sketchSkill, prdSkill, refineSkill, refineItemSkill, architectureSkill, sessionNotesSkill, buildSkill, scaffoldSkill, outlineSkill, literatureReviewSkill, draftSectionSkill, peerReviewSkill, researchScaffoldSkill, } from './platform-skills.js';

package/dist/skills/index.js

@@ -1,4 +1,4 @@
 /**
  * Platform Skills — barrel export
  */
-export { platformSkills, designSkill, sketchSkill, prdSkill, refineSkill, refineItemSkill, architectureSkill, sessionNotesSkill, buildSkill, scaffoldSkill, outlineSkill, literatureReviewSkill, draftSectionSkill, } from './platform-skills.js';
+export { platformSkills, designSkill, sketchSkill, prdSkill, refineSkill, refineItemSkill, architectureSkill, sessionNotesSkill, buildSkill, scaffoldSkill, outlineSkill, literatureReviewSkill, draftSectionSkill, peerReviewSkill, researchScaffoldSkill, } from './platform-skills.js';

package/dist/skills/platform-skills.d.ts

@@ -20,8 +20,10 @@ export declare const scaffoldSkill: Skill;
 export declare const outlineSkill: Skill;
 export declare const literatureReviewSkill: Skill;
 export declare const draftSectionSkill: Skill;
+export declare const peerReviewSkill: Skill;
+export declare const researchScaffoldSkill: Skill;
 /**
- * All platform-specific skills (11 total).
+ * All platform-specific skills (14 total).
  * These skills reference platform tools (backlog, workitems, documents, projects)
  * and belong in the SDK rather than in generic agent/coding libraries.
  */

package/dist/skills/platform-skills.js

@@ -1206,11 +1206,214 @@ Report to the user:
 ✓ User has reviewed the draft`,
     tags: ['research', 'writing', 'drafting'],
 });
+export const peerReviewSkill = defineSkill({
+    name: 'peer-review',
+    description: 'Validate argument structure, find logical gaps, check consistency across sections',
+    prompt: `You are in PEER REVIEW MODE. Your goal is to critically evaluate the research paper's argument structure, identify gaps, and check consistency — like an academic peer reviewer.
+
+## When to Use
+- One or more sections have been drafted
+- The user wants feedback before submitting/finalizing
+- After significant revisions to check nothing was broken
+- To identify areas that need more work
+
+## Step 1: Assess What's Available
+
+1. Use \`research_model_get\` with scope: "overview" for the big picture
+2. Use \`research_model_get\` with scope: "sections" to see status of each section
+3. Run \`research_model_validate\` for structural issues and warnings
+
+Report to the user:
+- "X sections drafted, Y still outlined, Z sources linked"
+- Any structural errors from validation
+- Which sections are ready for review
+
+If no sections are drafted yet, tell the user: "There's nothing to review yet — run /draft-section first."
+
+## Step 2: Argument Structure Review
+
+Read each drafted section (use \`read_file\` on the section files) and evaluate:
+
+**Thesis & Research Questions:**
+- Is the main thesis clearly stated in the Introduction?
+- Does each section contribute to answering the research questions?
+- Are the research questions actually addressed by the paper's content?
+
+**Logical Flow:**
+- Does the argument progress logically from Introduction → Literature Review → Methodology → Results → Discussion → Conclusion?
+- Does each section build on what came before?
+- Are there logical jumps or non-sequiturs between sections?
+
+**Claim Validation:**
+For each claim in the Research Model:
+- Is it actually stated in the draft text?
+- Is it supported by the cited sources?
+- Is the evidence strength rating accurate given the sources?
+- Are there unsupported assertions presented as established facts?
+
+Rate each issue found:
+- **Critical** — breaks the argument (e.g., unsupported central claim, circular reasoning)
+- **Major** — weakens the argument significantly (e.g., missing counter-arguments, logical gap)
+- **Minor** — should be fixed but doesn't break the argument (e.g., vague language, minor inconsistency)
+
+## Step 3: Gap Detection
+
+Check for missing elements:
+
+**Source Gaps:**
+- Claims that should have citations but don't
+- Sections that rely on very few sources
+- Important counter-arguments not addressed
+- Methodology claims without justification
+
+**Structural Gaps:**
+- Research questions not addressed by any section
+- Sections that don't connect to the overall argument
+- Missing limitations discussion
+- Missing future work section (if appropriate)
+
+**Content Gaps:**
+- Definitions used but never introduced
+- Acronyms used without expansion
+- Figures/tables referenced but not present
+- Promises made in the Introduction but not delivered
+
+## Step 4: Consistency Check
+
+Across all drafted sections, check:
+
+**Terminology:**
+- Is the same concept referred to consistently? (e.g., not "users" in one place and "participants" in another without reason)
+- Are technical terms used with consistent meaning?
+
+**Tense:**
+- Literature review: past tense for completed studies
+- Methodology: past tense for what was done, present for general statements
+- Results: past tense for findings
+- Discussion: present tense for interpretations
+
+**Voice & Tone:**
+- Is the level of formality consistent?
+- Is the author's voice consistent (not shifting between confident and hedging without reason)?
+
+**Numbers & Data:**
+- Do statistics match between text and any tables/figures?
+- Are numbers formatted consistently?
+
+## Step 5: Cross-Reference Check
+
+- "As discussed in Section X" — does Section X actually discuss that?
+- "See Table N" / "See Figure N" — do they exist?
+- Citations in text match sources in the Research Model
+- Consistent use of citation style throughout
+
+## Step 6: Generate Review Report
+
+Structure the report as:
+
+### Strengths
+- What the paper does well (2-3 points)
+
+### Critical Issues
+- Issues that must be addressed (with specific locations)
+
+### Major Issues
+- Significant improvements needed
+
+### Minor Issues
+- Small fixes and suggestions
+
+### Recommendations
+- Prioritized list of what to fix first
+- Suggested order of revisions
+
+Write the report to \`{project_path}/reviews/peer-review-{date}.md\`
+
+## Step 7: Update Model
+
+For issues that affect the Research Model:
+1. Update claim evidence strength if ratings were inaccurate
+2. Add new claims if the review identified missing arguments
+3. Create work items (type: "bug" / displayed as "Revision") for each critical and major issue:
+   - \`workitem_create\` with type: "bug", title: "Review: {brief issue}", description: detailed issue + suggested fix
+
+## Rules
+- Be constructive, not destructive — every critique should include a suggestion for improvement
+- Reference specific sections, claims, and sources by ID/citeKey
+- Don't rewrite the paper — point out issues and let the author fix them
+- Distinguish between opinion ("I would suggest...") and errors ("This claim is unsupported")
+- If the argument is sound, say so — don't manufacture problems
+- Focus on the argument, not the writing style (that's the Editor's job)
+
+## Completion Criteria
+✓ All drafted sections reviewed
+✓ Argument structure evaluated (thesis, logical flow, claim support)
+✓ Gaps identified (source, structural, content)
+✓ Consistency checked (terminology, tense, cross-references)
+✓ Review report written to file
+✓ Revision work items created for critical/major issues
+✓ User has received the review summary`,
+    tags: ['research', 'review', 'quality'],
+});
+export const researchScaffoldSkill = defineSkill({
+    name: 'research-scaffold',
+    description: 'Scaffold a research paper project from a template (APA, IEEE, Thesis, Literature Review, Lab Report)',
+    prompt: `You are in RESEARCH SCAFFOLD MODE. Your goal is to help the user set up a new research paper project using a template.
+
+## Available Templates
+
+| Template | ID | Best For |
+|----------|-----|----------|
+| APA Research Paper | \`apa-paper\` | Social sciences, psychology, education |
+| IEEE Conference Paper | \`ieee-paper\` | Engineering, computer science |
+| Thesis / Dissertation | \`thesis\` | Graduate work, multi-chapter |
+| Literature Review | \`literature-review\` | Standalone review papers |
+| Lab Report | \`lab-report\` | Scientific experiments |
+
+## Step 1: Gather Info
+
+Ask the user (if not already provided):
+1. What is the paper topic / title?
+2. Which template best fits their needs? (describe the options briefly)
+3. What citation style? (default depends on template — APA for most, IEEE for engineering)
+
+## Step 2: Scaffold
+
+Call the \`research_scaffold\` tool with:
+- \`template\`: the template ID
+- \`title\`: the paper title
+- \`citation_style\`: if different from template default
+- \`output_dir\`: the project path
+
+This creates:
+- A Research Model with pre-defined sections
+- Folder structure (sections/, figures/, references/, knowledge/)
+- Section stub files (one per section)
+- COMPILR.md with project context
+- Bibliography file (.bib)
+- Work items for each section (type: "Section")
+
+## Step 3: Confirm and Guide
+
+After scaffolding, tell the user:
+- What was created (sections, files, work items)
+- Suggested next steps:
+  1. "Add your source material to the Knowledge Base"
+  2. "Run /outline to customize the section structure"
+  3. "Run /literature-review to analyze your sources"
+  4. "Run /draft-section to start writing"
+
+## Rules
+- If a Research Model already exists, warn the user and don't overwrite
+- Use dry_run first if the user seems uncertain
+- The scaffold is a starting point — the user can customize everything after`,
+    tags: ['research', 'scaffold', 'setup'],
+});
 // =============================================================================
 // Aggregate export
 // =============================================================================
 /**
- * All platform-specific skills (11 total).
+ * All platform-specific skills (14 total).
  * These skills reference platform tools (backlog, workitems, documents, projects)
  * and belong in the SDK rather than in generic agent/coding libraries.
  */
@@ -1227,4 +1430,6 @@ export const platformSkills = [
     outlineSkill,
     literatureReviewSkill,
     draftSectionSkill,
+    peerReviewSkill,
+    researchScaffoldSkill,
 ];

package/package.json

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