@exaudeus/workrail 3.14.0 → 3.16.0

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.
Files changed (156) hide show
  1. package/dist/application/services/validation-engine.js +4 -9
  2. package/dist/application/services/workflow-compiler.js +4 -6
  3. package/dist/application/services/workflow-service.d.ts +2 -0
  4. package/dist/application/services/workflow-service.js +3 -0
  5. package/dist/console/assets/index-BE5PAgPO.js +28 -0
  6. package/dist/console/assets/index-BZNM03t1.css +1 -0
  7. package/dist/console/index.html +2 -2
  8. package/dist/engine/engine-factory.js +2 -2
  9. package/dist/engine/types.d.ts +1 -1
  10. package/dist/env-flags.d.ts +1 -0
  11. package/dist/env-flags.js +4 -0
  12. package/dist/infrastructure/session/HttpServer.d.ts +3 -3
  13. package/dist/infrastructure/session/HttpServer.js +68 -74
  14. package/dist/infrastructure/storage/caching-workflow-storage.d.ts +2 -0
  15. package/dist/infrastructure/storage/caching-workflow-storage.js +15 -6
  16. package/dist/infrastructure/storage/file-workflow-storage.js +3 -4
  17. package/dist/infrastructure/storage/schema-validating-workflow-storage.js +9 -8
  18. package/dist/manifest.json +283 -219
  19. package/dist/mcp/assert-output.d.ts +37 -0
  20. package/dist/mcp/assert-output.js +52 -0
  21. package/dist/mcp/boundary-coercion.d.ts +1 -0
  22. package/dist/mcp/boundary-coercion.js +44 -0
  23. package/dist/mcp/dev-mode.d.ts +1 -0
  24. package/dist/mcp/dev-mode.js +4 -0
  25. package/dist/mcp/handler-factory.js +12 -9
  26. package/dist/mcp/handlers/session.js +8 -9
  27. package/dist/mcp/handlers/shared/request-workflow-reader.d.ts +5 -0
  28. package/dist/mcp/handlers/shared/request-workflow-reader.js +47 -2
  29. package/dist/mcp/handlers/v2-advance-core/assessment-consequences.d.ts +1 -1
  30. package/dist/mcp/handlers/v2-advance-core/assessment-consequences.js +4 -5
  31. package/dist/mcp/handlers/v2-advance-core/event-builders.d.ts +2 -0
  32. package/dist/mcp/handlers/v2-advance-core/event-builders.js +6 -6
  33. package/dist/mcp/handlers/v2-advance-core/index.d.ts +2 -0
  34. package/dist/mcp/handlers/v2-advance-core/index.js +5 -4
  35. package/dist/mcp/handlers/v2-advance-core/input-validation.d.ts +2 -0
  36. package/dist/mcp/handlers/v2-advance-core/input-validation.js +32 -9
  37. package/dist/mcp/handlers/v2-advance-core/outcome-blocked.d.ts +2 -0
  38. package/dist/mcp/handlers/v2-advance-core/outcome-blocked.js +2 -2
  39. package/dist/mcp/handlers/v2-advance-core/outcome-success.d.ts +2 -0
  40. package/dist/mcp/handlers/v2-advance-core/outcome-success.js +1 -1
  41. package/dist/mcp/handlers/v2-checkpoint.d.ts +1 -1
  42. package/dist/mcp/handlers/v2-checkpoint.js +5 -6
  43. package/dist/mcp/handlers/v2-execution/advance.d.ts +4 -2
  44. package/dist/mcp/handlers/v2-execution/advance.js +5 -7
  45. package/dist/mcp/handlers/v2-execution/continue-advance.js +56 -26
  46. package/dist/mcp/handlers/v2-execution/continue-rehydrate.d.ts +1 -1
  47. package/dist/mcp/handlers/v2-execution/continue-rehydrate.js +9 -9
  48. package/dist/mcp/handlers/v2-execution/replay.d.ts +6 -4
  49. package/dist/mcp/handlers/v2-execution/replay.js +47 -30
  50. package/dist/mcp/handlers/v2-execution/start.d.ts +3 -3
  51. package/dist/mcp/handlers/v2-execution/start.js +31 -12
  52. package/dist/mcp/handlers/v2-execution/workflow-object-cache.d.ts +5 -0
  53. package/dist/mcp/handlers/v2-execution/workflow-object-cache.js +19 -0
  54. package/dist/mcp/handlers/v2-execution-helpers.d.ts +1 -0
  55. package/dist/mcp/handlers/v2-execution-helpers.js +23 -7
  56. package/dist/mcp/handlers/v2-resume.d.ts +1 -1
  57. package/dist/mcp/handlers/v2-resume.js +3 -4
  58. package/dist/mcp/handlers/v2-state-conversion.js +5 -1
  59. package/dist/mcp/handlers/v2-workflow.d.ts +100 -0
  60. package/dist/mcp/handlers/v2-workflow.js +155 -31
  61. package/dist/mcp/handlers/workflow.d.ts +2 -5
  62. package/dist/mcp/handlers/workflow.js +15 -12
  63. package/dist/mcp/output-schemas.d.ts +123 -29
  64. package/dist/mcp/output-schemas.js +36 -18
  65. package/dist/mcp/server.js +70 -5
  66. package/dist/mcp/tool-call-timing.d.ts +24 -0
  67. package/dist/mcp/tool-call-timing.js +85 -0
  68. package/dist/mcp/tool-descriptions.js +17 -9
  69. package/dist/mcp/transports/http-entry.js +3 -2
  70. package/dist/mcp/transports/http-listener.d.ts +1 -0
  71. package/dist/mcp/transports/http-listener.js +25 -0
  72. package/dist/mcp/transports/shutdown-hooks.d.ts +4 -1
  73. package/dist/mcp/transports/shutdown-hooks.js +3 -2
  74. package/dist/mcp/transports/stdio-entry.js +6 -28
  75. package/dist/mcp/v2/tools.d.ts +6 -0
  76. package/dist/mcp/v2/tools.js +2 -0
  77. package/dist/mcp/v2-response-formatter.js +2 -4
  78. package/dist/mcp/validation/schema-introspection.d.ts +1 -0
  79. package/dist/mcp/validation/schema-introspection.js +15 -5
  80. package/dist/mcp/validation/suggestion-generator.js +2 -2
  81. package/dist/mcp/workflow-protocol-contracts.js +5 -1
  82. package/dist/runtime/adapters/node-process-signals.d.ts +1 -0
  83. package/dist/runtime/adapters/node-process-signals.js +5 -0
  84. package/dist/runtime/adapters/noop-process-signals.d.ts +1 -0
  85. package/dist/runtime/adapters/noop-process-signals.js +2 -0
  86. package/dist/runtime/ports/process-signals.d.ts +1 -0
  87. package/dist/types/workflow-definition.d.ts +3 -2
  88. package/dist/types/workflow.d.ts +3 -0
  89. package/dist/types/workflow.js +35 -26
  90. package/dist/v2/durable-core/domain/context-template-resolver.js +2 -2
  91. package/dist/v2/durable-core/domain/function-definition-expander.js +2 -17
  92. package/dist/v2/durable-core/domain/prompt-renderer.d.ts +1 -0
  93. package/dist/v2/durable-core/domain/prompt-renderer.js +23 -18
  94. package/dist/v2/durable-core/domain/recap-recovery.js +23 -16
  95. package/dist/v2/durable-core/domain/retrieval-contract.js +13 -7
  96. package/dist/v2/durable-core/session-index.d.ts +22 -0
  97. package/dist/v2/durable-core/session-index.js +58 -0
  98. package/dist/v2/durable-core/sorted-event-log.d.ts +6 -0
  99. package/dist/v2/durable-core/sorted-event-log.js +15 -0
  100. package/dist/v2/infra/local/fs/index.js +8 -8
  101. package/dist/v2/infra/local/session-store/index.d.ts +1 -1
  102. package/dist/v2/infra/local/session-store/index.js +71 -61
  103. package/dist/v2/infra/local/session-summary-provider/index.js +9 -4
  104. package/dist/v2/infra/local/snapshot-store/index.js +2 -1
  105. package/dist/v2/infra/local/workspace-anchor/index.js +4 -1
  106. package/dist/v2/ports/session-event-log-store.port.d.ts +1 -1
  107. package/dist/v2/projections/assessment-consequences.d.ts +2 -1
  108. package/dist/v2/projections/assessment-consequences.js +0 -5
  109. package/dist/v2/projections/assessments.d.ts +2 -1
  110. package/dist/v2/projections/assessments.js +2 -4
  111. package/dist/v2/projections/gaps.d.ts +2 -1
  112. package/dist/v2/projections/gaps.js +0 -5
  113. package/dist/v2/projections/preferences.d.ts +2 -1
  114. package/dist/v2/projections/preferences.js +0 -5
  115. package/dist/v2/projections/run-context.d.ts +2 -2
  116. package/dist/v2/projections/run-context.js +0 -5
  117. package/dist/v2/projections/run-dag.js +7 -1
  118. package/dist/v2/projections/run-execution-trace.d.ts +8 -0
  119. package/dist/v2/projections/run-execution-trace.js +124 -0
  120. package/dist/v2/projections/run-status-signals.d.ts +2 -2
  121. package/dist/v2/usecases/console-routes.d.ts +3 -1
  122. package/dist/v2/usecases/console-routes.js +149 -3
  123. package/dist/v2/usecases/console-service.d.ts +2 -0
  124. package/dist/v2/usecases/console-service.js +87 -26
  125. package/dist/v2/usecases/console-types.d.ts +65 -0
  126. package/dist/v2/usecases/worktree-service.js +87 -8
  127. package/package.json +7 -6
  128. package/spec/authoring-spec.json +82 -1
  129. package/spec/workflow-tags.json +132 -0
  130. package/spec/workflow.schema.json +21 -11
  131. package/workflows/adaptive-ticket-creation.json +33 -8
  132. package/workflows/architecture-scalability-audit.json +50 -9
  133. package/workflows/bug-investigation.agentic.v2.json +43 -14
  134. package/workflows/coding-task-workflow-agentic.json +57 -38
  135. package/workflows/coding-task-workflow-agentic.lean.v2.json +129 -34
  136. package/workflows/coding-task-workflow-agentic.v2.json +97 -30
  137. package/workflows/cross-platform-code-conversion.v2.json +175 -48
  138. package/workflows/document-creation-workflow.json +49 -12
  139. package/workflows/documentation-update-workflow.json +9 -2
  140. package/workflows/intelligent-test-case-generation.json +9 -2
  141. package/workflows/learner-centered-course-workflow.json +273 -266
  142. package/workflows/mr-review-workflow.agentic.v2.json +88 -14
  143. package/workflows/personal-learning-materials-creation-branched.json +181 -174
  144. package/workflows/presentation-creation.json +167 -160
  145. package/workflows/production-readiness-audit.json +61 -15
  146. package/workflows/relocation-workflow-us.json +21 -5
  147. package/workflows/routines/tension-driven-design.json +1 -1
  148. package/workflows/scoped-documentation-workflow.json +9 -2
  149. package/workflows/test-artifact-loop-control.json +1 -2
  150. package/workflows/ui-ux-design-workflow.json +334 -0
  151. package/workflows/workflow-diagnose-environment.json +7 -1
  152. package/workflows/workflow-for-workflows.json +514 -484
  153. package/workflows/workflow-for-workflows.v2.json +55 -11
  154. package/workflows/wr.discovery.json +118 -29
  155. package/dist/console/assets/index-DW78t31j.css +0 -1
  156. package/dist/console/assets/index-EsSXrC_a.js +0 -28
@@ -1,8 +1,15 @@
1
1
  {
2
2
  "id": "mr-review-workflow-agentic",
3
- "name": "MR Review Workflow (Lean v2 Notes-First Evidence-Driven Reviewer Families)",
4
- "version": "2.2.0",
3
+ "name": "MR Review Workflow (Lean v2 \u2022 Notes-First \u2022 Evidence-Driven Reviewer Families)",
4
+ "version": "2.4.0",
5
5
  "description": "Lean v2 MR review workflow. Merges intake, missing-input gating, context gathering, and re-triage into one structured front phase, then drives review through a shared fact packet, parallel reviewer families, contradiction-driven synthesis, and evidence-first final validation.",
6
+ "about": "## MR Review Workflow\n\nThis workflow conducts a structured, evidence-driven code review of a merge request or pull request. It is designed for cases where you want a thorough, audit-quality review rather than a quick glance -- particularly when the change touches critical surfaces, spans many files, or carries real production risk.\n\n**What it does:**\nThe workflow locates and bounds the review target, enriches it with PR context and ticket intent, classifies the change by risk and shape, then runs parallel \"reviewer family\" agents (covering correctness, architecture, runtime risk, tests/docs, and more) from a shared neutral fact packet. It reconciles contradictions between reviewer families, stress-tests the recommendation with adversarial validators, and produces a final handoff with severity-classified findings and ready-to-post MR comments.\n\n**When to use it:**\n- Before merging a PR that touches auth, data models, APIs, or critical paths\n- When you want independent perspectives on a change without the noise of an unstructured review\n- When the change is large or the reviewer is unfamiliar with the surrounding code\n- When you need a reproducible audit trail for compliance or team review processes\n\n**What it produces:**\nA final review recommendation (approve / request changes / needs discussion) with a confidence band, severity-graded findings (Critical / Major / Minor / Nit), ready-to-post MR comments, a coverage ledger showing which review domains were checked, and an honest disclosure of any context that could not be recovered.\n\n**How to get good results:**\nProvide the PR URL, branch name, or diff. The workflow can recover most context on its own -- ticket links, repo patterns, policy docs -- but if the change has non-obvious intent, a one-sentence description of the goal helps calibrate review sensitivity. The workflow will not post comments or approve/reject without explicit instruction.",
7
+ "examples": [
8
+ "Review PR #47 adding JWT refresh token rotation before it merges to main",
9
+ "Review the feature/cache-expiration branch for correctness and production risk before merging",
10
+ "Audit PR #312 refactoring the payment service data model for backward compatibility and rollout safety",
11
+ "Review the open MR for the new rate-limiting middleware against our API contract standards"
12
+ ],
6
13
  "recommendedPreferences": {
7
14
  "recommendedAutonomy": "guided",
8
15
  "recommendedRiskPolicy": "conservative"
@@ -10,6 +17,29 @@
10
17
  "features": [
11
18
  "wr.features.subagent_guidance"
12
19
  ],
20
+ "assessments": [
21
+ {
22
+ "id": "review_readiness_gate",
23
+ "purpose": "Assess whether the review is ready to hand off across three orthogonal dimensions. Each must be high independently -- strength in one cannot compensate for weakness in another.",
24
+ "dimensions": [
25
+ {
26
+ "id": "evidence_quality",
27
+ "purpose": "Key findings are backed by specific code references, line numbers, or concrete observations -- not intuition or pattern-matching alone.",
28
+ "levels": ["low", "high"]
29
+ },
30
+ {
31
+ "id": "coverage_completeness",
32
+ "purpose": "All relevant review domains have been adequately checked for this change. No material blind spots remain unacknowledged.",
33
+ "levels": ["low", "high"]
34
+ },
35
+ {
36
+ "id": "contradiction_resolution",
37
+ "purpose": "Material contradictions and competing interpretations are resolved or explicitly acknowledged with a clear rationale for the chosen position.",
38
+ "levels": ["low", "high"]
39
+ }
40
+ ]
41
+ }
42
+ ],
13
43
  "preconditions": [
14
44
  "User provides an MR/PR objective, diff, patch, branch, or equivalent review target.",
15
45
  "The agent can inspect the changed files, surrounding code, and any deterministic validation artifacts needed to review accurately.",
@@ -34,11 +64,17 @@
34
64
  {
35
65
  "id": "phase-0-understand-and-classify",
36
66
  "title": "Phase 0: Locate, Bound, Enrich & Classify",
37
- "prompt": "Build the review foundation in one pass.\n\nStep 1 Early exit / minimum inputs:\nBefore exploring, verify that the review target is real and inspectable. If the diff, changed files, or equivalent review material are completely absent and cannot be inferred with tools, ask for the minimum missing artifact and stop. Do NOT ask questions you can resolve with tools.\n\nStep 2 Locate and bound the review target:\nAttempt to determine the strongest available review target and boundary.\n\nAttempt to establish:\n- `reviewTargetKind` from the strongest available source such as PR/MR, branch, patch, diff, or local working tree changes\n- `reviewTargetSource` describing where the target came from\n- likely PR/MR identity when available (`prUrl`, `prNumber`)\n- likely base / ancestor reference (`baseCandidate`, `mergeBaseRef`) when available\n- whether the branch may include inherited or out-of-scope changes\n- `boundaryConfidence`: High / Medium / Low\n\nDo not over-prescribe your own investigation path. Use the strongest available evidence and record uncertainty honestly.\n\nStep 3 Enrich with context:\nRecover the strongest available intent and policy context from whatever sources are actually available.\n\nAttempt to recover:\n- MR title and purpose\n- ticket / issue / acceptance context (`ticketRefs`, `ticketContext`)\n- supporting docs / specs / rollout context (`supportingDocsFound`)\n- repo or user policy/convention context when it is likely to affect review judgment (`policySourcesFound`)\n- `contextConfidence`: High / Medium / Low\n\nStep 4 Review-surface hygiene:\nClassify the visible change into a minimal review surface.\n\nSet:\n- `coreReviewSurface`\n- `likelyNoiseOrMechanicalChurn`\n- `likelyInheritedOrOutOfScopeChanges`\n- `reviewSurfaceSummary`\n- `reviewScopeWarnings`\n\nThe goal is not a giant ledger. The goal is to avoid treating every visible changed file as equally worthy of deep review by default.\n\nStep 5 Classify the review:\nAfter exploration, classify the work.\n\nSet:\n- `reviewMode`: QUICK / STANDARD / THOROUGH\n- `riskLevel`: Low / Medium / High\n- `shapeProfile`: choose the best primary label from `isolated_change`, `crosscutting_change`, `mechanically_noisy_change`, or `ambiguous_boundary`\n- `changeTypeProfile`: choose the best primary label from `general_code_change`, `api_contract_change`, `data_model_or_migration`, `security_sensitive`, or `test_only`\n- `maxParallelism`: 0 / 3 / 5\n- `criticalSurfaceTouched`: true / false\n- `needsSimulation`: true / false\n- `needsBoundaryFollowup`: true / false\n- `needsContextFollowup`: true / false\n- `needsReviewerBundle`: true / false\n\nDecision guidance:\n- QUICK: very small, isolated, low-risk changes with little ambiguity\n- STANDARD: typical feature or bug-fix reviews with moderate ambiguity or moderate risk\n- THOROUGH: critical surfaces, architectural novelty, high risk, broad change sets, or strong need for independent reviewer perspectives\n\nMinimal routing guidance:\n- if `boundaryConfidence = Low`, bias toward boundary/context follow-up before strong recommendation confidence\n- if `changeTypeProfile = api_contract_change`, bias toward contract/consumer/backward-compatibility scrutiny\n- if `changeTypeProfile = data_model_or_migration`, bias toward rollout / compatibility / simulation scrutiny\n- if `changeTypeProfile = security_sensitive`, bias toward adversarial/runtime-risk scrutiny and lower tolerance for weak evidence\n- if `changeTypeProfile = test_only`, bias toward stronger false-positive suppression\n- if `shapeProfile = mechanically_noisy_change`, bias toward stronger noise filtering and lower appetite for style-only findings\n\nStep 6 Optional deeper context:\nIf `reviewMode` is STANDARD or THOROUGH and context remains incomplete, and delegation is available, spawn TWO WorkRail Executors SIMULTANEOUSLY running `routine-context-gathering` with focus=COMPLETENESS and focus=DEPTH. Synthesize both outputs before finishing this step.\n\nStep 7 Human-facing artifact:\nChoose `reviewDocPath` only if a live artifact will materially improve human readability. Default suggestion: `mr-review.md` at the project root. This artifact is optional and never canonical workflow state.\n\nFallback behavior:\n- if PR/MR is not found but a branch/diff is inspectable, continue with downgraded context confidence and disclose missing PR context later\n- if the branch is inspectable but merge-base / ancestor remains ambiguous, continue with downgraded boundary confidence, set `needsBoundaryFollowup = true`, and disclose the uncertainty later\n- if ticket or supporting docs are missing, continue with downgraded context confidence and avoid overclaiming intent-sensitive findings\n- if only a patch/diff is available, continue if it is inspectable, but keep lower confidence on intent/boundary-dependent conclusions\n- if the review target itself is missing, ask only for that missing artifact and stop\n\nSet these keys in the next `continue_workflow` call's `context` object:\n- `reviewTargetKind`\n- `reviewTargetSource`\n- `prUrl`\n- `prNumber`\n- `baseCandidate`\n- `mergeBaseRef`\n- `boundaryConfidence`\n- `contextConfidence`\n- `mrTitle`\n- `mrPurpose`\n- `ticketRefs`\n- `ticketContext`\n- `supportingDocsFound`\n- `policySourcesFound`\n- `accessibleContextSources`\n- `missingContextSources`\n- `focusAreas`\n- `changedFileCount`\n- `criticalSurfaceTouched`\n- `reviewMode`\n- `riskLevel`\n- `shapeProfile`\n- `changeTypeProfile`\n- `maxParallelism`\n- `reviewDocPath`\n- `contextSummary`\n- `candidateFiles`\n- `moduleRoots`\n- `contextUnknownCount`\n- `coverageGapCount`\n- `authorIntentUnclear`\n- `needsSimulation`\n- `needsBoundaryFollowup`\n- `needsContextFollowup`\n- `needsReviewerBundle`\n- `coreReviewSurface`\n- `likelyNoiseOrMechanicalChurn`\n- `likelyInheritedOrOutOfScopeChanges`\n- `reviewSurfaceSummary`\n- `reviewScopeWarnings`\n- `openQuestions`\n\nRules:\n- answer your own questions with tools whenever possible\n- only keep true human-decision questions in `openQuestions`\n- keep `openQuestions` bounded to the minimum necessary\n- classify AFTER exploring, not before\n- before leaving this phase, either establish the likely review boundary or explicitly record why you could not",
67
+ "prompt": "Build the review foundation in one pass.\n\nStep 1 \u2014 Early exit / minimum inputs:\nBefore exploring, verify that the review target is real and inspectable. If the diff, changed files, or equivalent review material are completely absent and cannot be inferred with tools, ask for the minimum missing artifact and stop. Do NOT ask questions you can resolve with tools.\n\nStep 2 \u2014 Locate and bound the review target:\nAttempt to determine the strongest available review target and boundary.\n\nAttempt to establish:\n- `reviewTargetKind` from the strongest available source such as PR/MR, branch, patch, diff, or local working tree changes\n- `reviewTargetSource` describing where the target came from\n- likely PR/MR identity when available (`prUrl`, `prNumber`)\n- likely base / ancestor reference (`baseCandidate`, `mergeBaseRef`) when available\n- whether the branch may include inherited or out-of-scope changes\n- `boundaryConfidence`: High / Medium / Low\n\nDo not over-prescribe your own investigation path. Use the strongest available evidence and record uncertainty honestly.\n\nStep 3 \u2014 Enrich with context:\nRecover the strongest available intent and policy context from whatever sources are actually available.\n\nAttempt to recover:\n- MR title and purpose\n- ticket / issue / acceptance context (`ticketRefs`, `ticketContext`)\n- supporting docs / specs / rollout context (`supportingDocsFound`)\n- repo or user policy/convention context when it is likely to affect review judgment (`policySourcesFound`)\n- `contextConfidence`: High / Medium / Low\n\nStep 4 \u2014 Review-surface hygiene:\nClassify the visible change into a minimal review surface.\n\nSet:\n- `coreReviewSurface`\n- `likelyNoiseOrMechanicalChurn`\n- `likelyInheritedOrOutOfScopeChanges`\n- `reviewSurfaceSummary`\n- `reviewScopeWarnings`\n\nThe goal is not a giant ledger. The goal is to avoid treating every visible changed file as equally worthy of deep review by default.\n\nStep 5 \u2014 Classify the review:\nAfter exploration, classify the work.\n\nSet:\n- `reviewMode`: QUICK / STANDARD / THOROUGH\n- `riskLevel`: Low / Medium / High\n- `shapeProfile`: choose the best primary label from `isolated_change`, `crosscutting_change`, `mechanically_noisy_change`, or `ambiguous_boundary`\n- `changeTypeProfile`: choose the best primary label from `general_code_change`, `api_contract_change`, `data_model_or_migration`, `security_sensitive`, or `test_only`\n- `maxParallelism`: 0 / 3 / 5\n- `criticalSurfaceTouched`: true / false\n- `needsSimulation`: true / false\n- `needsBoundaryFollowup`: true / false\n- `needsContextFollowup`: true / false\n- `needsReviewerBundle`: true / false\n\nDecision guidance:\n- QUICK: very small, isolated, low-risk changes with little ambiguity\n- STANDARD: typical feature or bug-fix reviews with moderate ambiguity or moderate risk\n- THOROUGH: critical surfaces, architectural novelty, high risk, broad change sets, or strong need for independent reviewer perspectives\n\nMinimal routing guidance:\n- if `boundaryConfidence = Low`, bias toward boundary/context follow-up before strong recommendation confidence\n- if `changeTypeProfile = api_contract_change`, bias toward contract/consumer/backward-compatibility scrutiny\n- if `changeTypeProfile = data_model_or_migration`, bias toward rollout / compatibility / simulation scrutiny\n- if `changeTypeProfile = security_sensitive`, bias toward adversarial/runtime-risk scrutiny and lower tolerance for weak evidence\n- if `changeTypeProfile = test_only`, bias toward stronger false-positive suppression\n- if `shapeProfile = mechanically_noisy_change`, bias toward stronger noise filtering and lower appetite for style-only findings\n\nStep 6 \u2014 Optional deeper context:\nIf `reviewMode` is STANDARD or THOROUGH and context remains incomplete, and delegation is available, spawn TWO WorkRail Executors SIMULTANEOUSLY running `routine-context-gathering` with focus=COMPLETENESS and focus=DEPTH. Synthesize both outputs before finishing this step.\n\nStep 7 \u2014 Human-facing artifact:\nChoose `reviewDocPath` only if a live artifact will materially improve human readability. Default suggestion: `mr-review.md` at the project root. This artifact is optional and never canonical workflow state.\n\nFallback behavior:\n- if PR/MR is not found but a branch/diff is inspectable, continue with downgraded context confidence and disclose missing PR context later\n- if the branch is inspectable but merge-base / ancestor remains ambiguous, continue with downgraded boundary confidence, set `needsBoundaryFollowup = true`, and disclose the uncertainty later\n- if ticket or supporting docs are missing, continue with downgraded context confidence and avoid overclaiming intent-sensitive findings\n- if only a patch/diff is available, continue if it is inspectable, but keep lower confidence on intent/boundary-dependent conclusions\n- if the review target itself is missing, ask only for that missing artifact and stop\n\nSet these keys in the next `continue_workflow` call's `context` object:\n- `reviewTargetKind`\n- `reviewTargetSource`\n- `prUrl`\n- `prNumber`\n- `baseCandidate`\n- `mergeBaseRef`\n- `boundaryConfidence`\n- `contextConfidence`\n- `mrTitle`\n- `mrPurpose`\n- `ticketRefs`\n- `ticketContext`\n- `supportingDocsFound`\n- `policySourcesFound`\n- `accessibleContextSources`\n- `missingContextSources`\n- `focusAreas`\n- `changedFileCount`\n- `criticalSurfaceTouched`\n- `reviewMode`\n- `riskLevel`\n- `shapeProfile`\n- `changeTypeProfile`\n- `maxParallelism`\n- `reviewDocPath`\n- `contextSummary`\n- `candidateFiles`\n- `moduleRoots`\n- `contextUnknownCount`\n- `coverageGapCount`\n- `authorIntentUnclear`\n- `needsSimulation`\n- `needsBoundaryFollowup`\n- `needsContextFollowup`\n- `needsReviewerBundle`\n- `coreReviewSurface`\n- `likelyNoiseOrMechanicalChurn`\n- `likelyInheritedOrOutOfScopeChanges`\n- `reviewSurfaceSummary`\n- `reviewScopeWarnings`\n- `openQuestions`\n\nRules:\n- answer your own questions with tools whenever possible\n- only keep true human-decision questions in `openQuestions`\n- keep `openQuestions` bounded to the minimum necessary\n- classify AFTER exploring, not before\n- before leaving this phase, either establish the likely review boundary or explicitly record why you could not\n\nAlso set in the context object: one sentence describing what you are trying to accomplish (e.g. \"implement OAuth refresh token rotation\", \"review PR #47 before merge\"). This populates the session title in the Workspace console immediately.",
38
68
  "requireConfirmation": {
39
69
  "or": [
40
- { "var": "reviewMode", "equals": "THOROUGH" },
41
- { "var": "riskLevel", "equals": "High" }
70
+ {
71
+ "var": "reviewMode",
72
+ "equals": "THOROUGH"
73
+ },
74
+ {
75
+ "var": "riskLevel",
76
+ "equals": "High"
77
+ }
42
78
  ]
43
79
  }
44
80
  },
@@ -55,7 +91,10 @@
55
91
  "goal": "Freeze a shared factual basis for review and decide how much reviewer-family parallelism is warranted.",
56
92
  "constraints": [
57
93
  [
58
- { "kind": "ref", "refId": "wr.refs.notes_first_durability" }
94
+ {
95
+ "kind": "ref",
96
+ "refId": "wr.refs.notes_first_durability"
97
+ }
59
98
  ],
60
99
  "The fact packet is the primary truth for downstream reviewer families.",
61
100
  "Keep `recommendationHypothesis` as a secondary hypothesis to challenge, not a frame to defend."
@@ -89,10 +128,16 @@
89
128
  "goal": "Run the selected reviewer families in parallel from the same fact packet, then synthesize their output as evidence rather than conclusions.",
90
129
  "constraints": [
91
130
  [
92
- { "kind": "ref", "refId": "wr.refs.notes_first_durability" }
131
+ {
132
+ "kind": "ref",
133
+ "refId": "wr.refs.notes_first_durability"
134
+ }
93
135
  ],
94
136
  [
95
- { "kind": "ref", "refId": "wr.refs.synthesis_under_disagreement" }
137
+ {
138
+ "kind": "ref",
139
+ "refId": "wr.refs.synthesis_under_disagreement"
140
+ }
96
141
  ],
97
142
  "Each reviewer family must use `reviewFactPacket` as primary truth.",
98
143
  "Use `recommendationHypothesis` only as secondary comparison context.",
@@ -138,7 +183,10 @@
138
183
  "goal": "If contradictions, blind spots, or important coverage gaps remain, run only the smallest targeted follow-up needed.",
139
184
  "constraints": [
140
185
  [
141
- { "kind": "ref", "refId": "wr.refs.parallelize_cognition_serialize_synthesis" }
186
+ {
187
+ "kind": "ref",
188
+ "refId": "wr.refs.parallelize_cognition_serialize_synthesis"
189
+ }
142
190
  ],
143
191
  "Prefer one compact targeted bundle over repeated broad delegation moments.",
144
192
  "Do not regather broad context unless a contradiction proves the original fact packet is insufficient.",
@@ -162,7 +210,7 @@
162
210
  {
163
211
  "id": "phase-4b-canonical-synthesis",
164
212
  "title": "Canonical Synthesis and Coverage Update",
165
- "prompt": "Synthesize all reviewer-family outputs and targeted follow-up into one canonical review state.\n\nPart A Compare against your hypothesis:\n- revisit `recommendationHypothesis`\n- what did the evidence confirm?\n- what did it challenge?\n- what changed your mind, what held firm, and what do you explicitly reject?\n\nPart B Synthesis decision table:\n- if 2+ reviewer families flag the same serious issue with the same severity, treat it as validated\n- if the same issue is flagged with different severities, default to the higher severity unless the lower-severity position includes specific counter-evidence\n- if one family flags an issue and others are silent, investigate it but do not automatically block unless it is clearly critical or security-sensitive\n- if one family says false positive and another says valid issue, require explicit main-agent adjudication in notes before finalization\n- if recommendation spread shows material disagreement, findings override recommendation until reconciled\n- if simulation reveals a new production risk, add a new finding and re-evaluate recommendation confidence\n\nPart C Coverage ledger rules:\n- move a domain from `uncertain` to `checked` only when evidence is materially adequate\n- keep a domain `uncertain` if disagreement or missing evidence still materially affects recommendation quality\n- mark `not_applicable` only when the MR genuinely does not engage that dimension\n- clear `contradicted` only when the contradiction is explicitly resolved by evidence or adjudication\n- clear `needs_followup` only when required follow-up has actually been completed or the domain is explicitly downgraded as non-material\n\nPart D Recommendation confidence rules:\n- set `recommendationConfidenceBand = High` only if no unresolved material contradictions remain, no important coverage domains remain uncertain, false-positive risk is not material, and the evidence is strong enough for the current mode\n- set `recommendationConfidenceBand = Medium` when one bounded uncertainty remains but the recommendation is still directionally justified\n- set `recommendationConfidenceBand = Low` when multiple viable interpretations remain, major contradictions are unresolved, or important coverage gaps still weaken the recommendation\n\nSet these keys in the next `continue_workflow` call's `context` object:\n- `reviewFindings`\n- `criticalFindingsCount`\n- `majorFindingsCount`\n- `minorFindingsCount`\n- `nitFindingsCount`\n- `recommendation`\n- `recommendationConfidenceBand`\n- `recommendationDriftDetected`\n- `coverageLedger`\n- `coverageUncertainCount`\n- `docCompletenessConcernCount`\n\nIf `reviewDocPath` exists, keep it aligned for human readability only. Notes/context remain workflow truth.",
213
+ "prompt": "Synthesize all reviewer-family outputs and targeted follow-up into one canonical review state.\n\nPart A \u2014 Compare against your hypothesis:\n- revisit `recommendationHypothesis`\n- what did the evidence confirm?\n- what did it challenge?\n- what changed your mind, what held firm, and what do you explicitly reject?\n\nPart B \u2014 Synthesis decision table:\n- if 2+ reviewer families flag the same serious issue with the same severity, treat it as validated\n- if the same issue is flagged with different severities, default to the higher severity unless the lower-severity position includes specific counter-evidence\n- if one family flags an issue and others are silent, investigate it but do not automatically block unless it is clearly critical or security-sensitive\n- if one family says false positive and another says valid issue, require explicit main-agent adjudication in notes before finalization\n- if recommendation spread shows material disagreement, findings override recommendation until reconciled\n- if simulation reveals a new production risk, add a new finding and re-evaluate recommendation confidence\n\nPart C \u2014 Coverage ledger rules:\n- move a domain from `uncertain` to `checked` only when evidence is materially adequate\n- keep a domain `uncertain` if disagreement or missing evidence still materially affects recommendation quality\n- mark `not_applicable` only when the MR genuinely does not engage that dimension\n- clear `contradicted` only when the contradiction is explicitly resolved by evidence or adjudication\n- clear `needs_followup` only when required follow-up has actually been completed or the domain is explicitly downgraded as non-material\n\nPart D \u2014 Recommendation confidence rules:\n- set `recommendationConfidenceBand = High` only if no unresolved material contradictions remain, no important coverage domains remain uncertain, false-positive risk is not material, and the evidence is strong enough for the current mode\n- set `recommendationConfidenceBand = Medium` when one bounded uncertainty remains but the recommendation is still directionally justified\n- set `recommendationConfidenceBand = Low` when multiple viable interpretations remain, major contradictions are unresolved, or important coverage gaps still weaken the recommendation\n\nSet these keys in the next `continue_workflow` call's `context` object:\n- `reviewFindings`\n- `criticalFindingsCount`\n- `majorFindingsCount`\n- `minorFindingsCount`\n- `nitFindingsCount`\n- `recommendation`\n- `recommendationConfidenceBand`\n- `recommendationDriftDetected`\n- `coverageLedger`\n- `coverageUncertainCount`\n- `docCompletenessConcernCount`\n\nIf `reviewDocPath` exists, keep it aligned for human readability only. Notes/context remain workflow truth.",
166
214
  "requireConfirmation": false
167
215
  },
168
216
  {
@@ -183,10 +231,16 @@
183
231
  "goal": "Stress-test the current recommendation before final handoff.",
184
232
  "constraints": [
185
233
  [
186
- { "kind": "ref", "refId": "wr.refs.adversarial_challenge_rules" }
234
+ {
235
+ "kind": "ref",
236
+ "refId": "wr.refs.adversarial_challenge_rules"
237
+ }
187
238
  ],
188
239
  [
189
- { "kind": "ref", "refId": "wr.refs.synthesis_under_disagreement" }
240
+ {
241
+ "kind": "ref",
242
+ "refId": "wr.refs.synthesis_under_disagreement"
243
+ }
190
244
  ],
191
245
  "Validation output is evidence to synthesize, not an automatic reopen signal."
192
246
  ],
@@ -205,10 +259,30 @@
205
259
  "If no validator can materially break the current recommendation and findings are internally consistent, proceed to handoff."
206
260
  ]
207
261
  },
262
+ "assessmentRefs": [
263
+ "review_readiness_gate"
264
+ ],
265
+ "assessmentConsequences": [
266
+ {
267
+ "when": {
268
+ "anyEqualsLevel": "low"
269
+ },
270
+ "effect": {
271
+ "kind": "require_followup",
272
+ "guidance": "Address whichever dimensions scored low: evidence_quality low -- anchor each finding to a specific file, function, or line; remove findings without concrete grounding. coverage_completeness low -- investigate uncovered domains or explicitly acknowledge gaps in the ledger. contradiction_resolution low -- resolve each contradiction or explicitly state your position with rationale."
273
+ }
274
+ }
275
+ ],
208
276
  "requireConfirmation": {
209
277
  "or": [
210
- { "var": "validatorConsensusLevel", "equals": "Low" },
211
- { "var": "recommendationConfidenceBand", "equals": "Low" }
278
+ {
279
+ "var": "validatorConsensusLevel",
280
+ "equals": "Low"
281
+ },
282
+ {
283
+ "var": "recommendationConfidenceBand",
284
+ "equals": "Low"
285
+ }
212
286
  ]
213
287
  }
214
288
  },
@@ -1,188 +1,195 @@
1
1
  {
2
- "id": "personal-learning-materials-creation-branched",
3
- "name": "Personal Learning Materials Creation Workflow (Branched)",
4
- "version": "1.1.0",
5
- "description": "A systematic workflow for creating high-quality learning materials with three thoroughness paths: Quick Start (essential materials), Balanced (comprehensive system), and Comprehensive (enterprise-grade). Adapts depth and features based on user time constraints and quality goals.",
6
- "clarificationPrompts": [
7
- "Do you have a completed learning plan with defined objectives and modules?",
8
- "How much time can you dedicate weekly to materials creation?",
9
- "What content creation tools do you have access to?",
10
- "What material formats work best for your learning style?"
11
- ],
12
- "preconditions": [
13
- "Completed learning plan or course design with clear objectives",
14
- "Access to basic content creation tools (word processor, simple design software)",
15
- "Time allocated for focused materials development sessions",
16
- "Clear understanding of personal learning style preferences"
17
- ],
18
- "metaGuidance": [
19
- "OBJECTIVE ALIGNMENT: Every material must directly support specific learning objectives",
20
- "ADAPTIVE DEPTH: Adjust thoroughness based on selected path without compromising quality",
21
- "IMMEDIATE USABILITY: Materials should be ready to use without additional setup",
22
- "QUALITY OVER QUANTITY: Better fewer high-quality materials than many mediocre ones"
23
- ],
24
- "steps": [
2
+ "id": "personal-learning-materials-creation-branched",
3
+ "name": "Personal Learning Materials Creation Workflow (Branched)",
4
+ "version": "1.1.0",
5
+ "description": "Use this to create learning materials for a course or subject. Adapts depth and format to your time budget Quick Start, Balanced, or Comprehensive.",
6
+ "about": "## Personal Learning Materials Creation Workflow\n\nUse this to create the actual study materials for a course or subject you are learning -- study guides, exercises, assessments, and spaced-repetition review materials. This workflow assumes you already have a learning plan or course design with defined objectives; it focuses on producing materials that directly support those objectives.\n\n### What it produces\n\nDepending on the path you choose:\n\n- **Quick Start (2-3 weeks)**: study guides and basic exercises for immediate use.\n- **Balanced (4-6 weeks)**: a complete learning system -- study guides, exercises, assessments, and spaced repetition materials.\n- **Comprehensive (8-12 weeks)**: a full learning ecosystem with interactive elements, effectiveness measurement, and a scalable update protocol.\n\n### When to use it\n\n- You have a learning plan and need to turn it into usable materials.\n- You are preparing for a certification, exam, or structured self-study program.\n- You want materials tailored to your specific objectives rather than relying entirely on off-the-shelf resources.\n\n### When NOT to use it\n\n- You haven't designed your learning course yet -- use the Personal Learning Course Design workflow first to define objectives and structure.\n- You need to design a course for others to take -- use the Learner-Centered Course workflow instead.\n\n### How to get good results\n\n- Select the path honestly based on available time. Starting with Quick Start and expanding later is better than committing to Comprehensive and abandoning it.\n- Have your learning objectives written out before starting -- the workflow maps every material directly to an objective.\n- Be specific about your preferred learning formats (text, diagrams, flashcards, practice problems) at the start.",
7
+ "examples": [
8
+ "Create study guides and exercises for my AWS Solutions Architect certification prep",
9
+ "Build a complete set of flashcards and practice problems for learning Rust ownership",
10
+ "Create materials for a 6-week self-study course on Bayesian statistics",
11
+ "Make a quick-start study guide for the CKAD Kubernetes exam"
12
+ ],
13
+ "clarificationPrompts": [
14
+ "Do you have a completed learning plan with defined objectives and modules?",
15
+ "How much time can you dedicate weekly to materials creation?",
16
+ "What content creation tools do you have access to?",
17
+ "What material formats work best for your learning style?"
18
+ ],
19
+ "preconditions": [
20
+ "Completed learning plan or course design with clear objectives",
21
+ "Access to basic content creation tools (word processor, simple design software)",
22
+ "Time allocated for focused materials development sessions",
23
+ "Clear understanding of personal learning style preferences"
24
+ ],
25
+ "metaGuidance": [
26
+ "OBJECTIVE ALIGNMENT: Every material must directly support specific learning objectives",
27
+ "ADAPTIVE DEPTH: Adjust thoroughness based on selected path without compromising quality",
28
+ "IMMEDIATE USABILITY: Materials should be ready to use without additional setup",
29
+ "QUALITY OVER QUANTITY: Better fewer high-quality materials than many mediocre ones"
30
+ ],
31
+ "steps": [
32
+ {
33
+ "id": "phase-0-select-thoroughness-path",
34
+ "title": "Phase 0: Select Your Materials Creation Path",
35
+ "prompt": "Choose your learning materials creation approach based on your time, goals, and quality needs:\n\n📚 **Quick Start Path**\n• Timeline: 2-3 weeks (5-8 hours total)\n• Materials: Study guides + basic exercises\n• Best for: Time-constrained learners, getting started quickly\n• Outcome: Functional materials for immediate use\n\n🎯 **Balanced Path**\n• Timeline: 4-6 weeks (12-20 hours total)\n• Materials: Study guides + exercises + assessments + spaced repetition\n• Best for: Comprehensive learning support, professional quality\n• Outcome: Complete learning system with proven effectiveness\n\n🏆 **Comprehensive Path**\n• Timeline: 8-12 weeks (25-40 hours total)\n• Materials: All types + interactive elements + full testing\n• Best for: Professional educators, enterprise-grade projects\n• Outcome: Optimized learning ecosystem with maximum effectiveness\n\nWhich path best matches your timeline and quality goals?",
36
+ "agentRole": "You are a learning materials consultant specializing in helping users choose the right approach for their constraints and goals. Guide users toward the path that best fits their needs. Set the thoroughnessLevel context variable based on their selection.",
37
+ "guidance": [
38
+ "Help users make realistic choices based on their actual time availability",
39
+ "Explain the trade-offs between speed and comprehensiveness",
40
+ "Encourage users to start with a simpler path if uncertain"
41
+ ],
42
+ "requireConfirmation": true
43
+ },
44
+ {
45
+ "id": "analyze-learning-plan-quick",
46
+ "runCondition": {
47
+ "var": "thoroughnessLevel",
48
+ "equals": "Quick"
49
+ },
50
+ "title": "Phase 1: Essential Learning Plan Analysis (Quick Start)",
51
+ "prompt": "Extract the core elements from your learning plan for rapid materials creation:\n\n**STEP 1: Core Objectives**\n• Identify your 3-5 most important learning objectives\n• Note success criteria for each objective\n• Skip complex prerequisite analysis\n\n**STEP 2: Essential Materials Map**\n• For each objective, identify if you need: study guide, basic exercises, or both\n• Focus on immediate learning needs, not comprehensive coverage\n• Note existing resources that can supplement your materials\n\n**STEP 3: Quick Resource Assessment**\n• List available source materials (books, courses, notes)\n• Identify 2-3 key resources for each objective\n• Note time constraints and creation priorities\n\nGoal: Practical roadmap for essential materials creation in minimal time.",
52
+ "agentRole": "You are an efficient learning analyst focused on rapid materials development. Help users identify core needs quickly without over-analysis. Emphasize practical, immediately actionable insights.",
53
+ "guidance": [
54
+ "Keep analysis focused and action-oriented",
55
+ "Avoid perfectionism - good enough is good enough",
56
+ "Focus on high-impact materials that provide immediate value"
57
+ ],
58
+ "validationCriteria": [
25
59
  {
26
- "id": "phase-0-select-thoroughness-path",
27
- "title": "Phase 0: Select Your Materials Creation Path",
28
- "prompt": "Choose your learning materials creation approach based on your time, goals, and quality needs:\n\n\ud83d\udcda **Quick Start Path**\n\u2022 Timeline: 2-3 weeks (5-8 hours total)\n\u2022 Materials: Study guides + basic exercises\n\u2022 Best for: Time-constrained learners, getting started quickly\n\u2022 Outcome: Functional materials for immediate use\n\n\ud83c\udfaf **Balanced Path**\n\u2022 Timeline: 4-6 weeks (12-20 hours total)\n\u2022 Materials: Study guides + exercises + assessments + spaced repetition\n\u2022 Best for: Comprehensive learning support, professional quality\n\u2022 Outcome: Complete learning system with proven effectiveness\n\n\ud83c\udfc6 **Comprehensive Path**\n\u2022 Timeline: 8-12 weeks (25-40 hours total)\n\u2022 Materials: All types + interactive elements + full testing\n\u2022 Best for: Professional educators, enterprise-grade projects\n\u2022 Outcome: Optimized learning ecosystem with maximum effectiveness\n\nWhich path best matches your timeline and quality goals?",
29
- "agentRole": "You are a learning materials consultant specializing in helping users choose the right approach for their constraints and goals. Guide users toward the path that best fits their needs. Set the thoroughnessLevel context variable based on their selection.",
30
- "guidance": [
31
- "Help users make realistic choices based on their actual time availability",
32
- "Explain the trade-offs between speed and comprehensiveness",
33
- "Encourage users to start with a simpler path if uncertain"
34
- ],
35
- "requireConfirmation": true
60
+ "type": "contains",
61
+ "value": "learning objective",
62
+ "message": "Must identify core learning objectives"
36
63
  },
37
64
  {
38
- "id": "analyze-learning-plan-quick",
39
- "runCondition": {
40
- "var": "thoroughnessLevel",
41
- "equals": "Quick"
42
- },
43
- "title": "Phase 1: Essential Learning Plan Analysis (Quick Start)",
44
- "prompt": "Extract the core elements from your learning plan for rapid materials creation:\n\n**STEP 1: Core Objectives**\n\u2022 Identify your 3-5 most important learning objectives\n\u2022 Note success criteria for each objective\n\u2022 Skip complex prerequisite analysis\n\n**STEP 2: Essential Materials Map**\n\u2022 For each objective, identify if you need: study guide, basic exercises, or both\n\u2022 Focus on immediate learning needs, not comprehensive coverage\n\u2022 Note existing resources that can supplement your materials\n\n**STEP 3: Quick Resource Assessment**\n\u2022 List available source materials (books, courses, notes)\n\u2022 Identify 2-3 key resources for each objective\n\u2022 Note time constraints and creation priorities\n\nGoal: Practical roadmap for essential materials creation in minimal time.",
45
- "agentRole": "You are an efficient learning analyst focused on rapid materials development. Help users identify core needs quickly without over-analysis. Emphasize practical, immediately actionable insights.",
46
- "guidance": [
47
- "Keep analysis focused and action-oriented",
48
- "Avoid perfectionism - good enough is good enough",
49
- "Focus on high-impact materials that provide immediate value"
50
- ],
51
- "validationCriteria": [
52
- {
53
- "type": "contains",
54
- "value": "learning objective",
55
- "message": "Must identify core learning objectives"
56
- },
57
- {
58
- "type": "contains",
59
- "value": "study guide",
60
- "message": "Must specify study guide requirements"
61
- },
62
- {
63
- "type": "length",
64
- "min": 200,
65
- "max": 800,
66
- "message": "Analysis should be concise but actionable (200-800 characters)"
67
- }
68
- ],
69
- "hasValidation": true
65
+ "type": "contains",
66
+ "value": "study guide",
67
+ "message": "Must specify study guide requirements"
70
68
  },
71
69
  {
72
- "id": "analyze-learning-plan-balanced",
73
- "runCondition": {
74
- "var": "thoroughnessLevel",
75
- "equals": "Balanced"
76
- },
77
- "title": "Phase 1: Comprehensive Learning Plan Analysis (Balanced)",
78
- "prompt": "Analyze your learning plan to guide professional-quality materials creation:\n\n**STEP 1: Objective Architecture**\n\u2022 Extract all learning objectives with success criteria\n\u2022 Identify prerequisite relationships between objectives\n\u2022 Note assessment strategies for each objective\n\u2022 Map objectives to modules and time allocations\n\n**STEP 2: Materials Requirements Matrix**\n\u2022 For each objective, determine needed materials: study guides, exercises, assessments\n\u2022 Identify concepts requiring multiple reinforcement approaches\n\u2022 Note which objectives need spaced repetition support\n\u2022 Flag areas requiring practical application or hands-on practice\n\n**STEP 3: Resource Integration Plan**\n\u2022 Evaluate existing resources for quality and coverage\n\u2022 Identify gaps where custom materials are essential\n\u2022 Plan integration between created materials and external resources\n\u2022 Design quality standards for materials consistency\n\nGoal: Strategic foundation for professional learning materials system.",
79
- "agentRole": "You are a professional instructional designer specializing in systematic materials development. Help users create comprehensive yet practical plans that balance quality with efficiency. Focus on proven instructional design principles.",
80
- "guidance": [
81
- "Apply instructional design best practices systematically",
82
- "Balance thoroughness with practical time constraints",
83
- "Focus on materials that work together as a cohesive system"
84
- ],
85
- "validationCriteria": [
86
- {
87
- "type": "contains",
88
- "value": "assessment",
89
- "message": "Must include assessment strategy planning"
90
- },
91
- {
92
- "type": "length",
93
- "min": 400,
94
- "max": 1200,
95
- "message": "Analysis should be comprehensive (400-1200 characters)"
96
- }
97
- ],
98
- "hasValidation": true
70
+ "type": "length",
71
+ "min": 200,
72
+ "max": 800,
73
+ "message": "Analysis should be concise but actionable (200-800 characters)"
74
+ }
75
+ ],
76
+ "hasValidation": true
77
+ },
78
+ {
79
+ "id": "analyze-learning-plan-balanced",
80
+ "runCondition": {
81
+ "var": "thoroughnessLevel",
82
+ "equals": "Balanced"
83
+ },
84
+ "title": "Phase 1: Comprehensive Learning Plan Analysis (Balanced)",
85
+ "prompt": "Analyze your learning plan to guide professional-quality materials creation:\n\n**STEP 1: Objective Architecture**\n• Extract all learning objectives with success criteria\n• Identify prerequisite relationships between objectives\n• Note assessment strategies for each objective\n• Map objectives to modules and time allocations\n\n**STEP 2: Materials Requirements Matrix**\n• For each objective, determine needed materials: study guides, exercises, assessments\n• Identify concepts requiring multiple reinforcement approaches\n• Note which objectives need spaced repetition support\n• Flag areas requiring practical application or hands-on practice\n\n**STEP 3: Resource Integration Plan**\n• Evaluate existing resources for quality and coverage\n• Identify gaps where custom materials are essential\n• Plan integration between created materials and external resources\n• Design quality standards for materials consistency\n\nGoal: Strategic foundation for professional learning materials system.",
86
+ "agentRole": "You are a professional instructional designer specializing in systematic materials development. Help users create comprehensive yet practical plans that balance quality with efficiency. Focus on proven instructional design principles.",
87
+ "guidance": [
88
+ "Apply instructional design best practices systematically",
89
+ "Balance thoroughness with practical time constraints",
90
+ "Focus on materials that work together as a cohesive system"
91
+ ],
92
+ "validationCriteria": [
93
+ {
94
+ "type": "contains",
95
+ "value": "assessment",
96
+ "message": "Must include assessment strategy planning"
97
+ },
98
+ {
99
+ "type": "length",
100
+ "min": 400,
101
+ "max": 1200,
102
+ "message": "Analysis should be comprehensive (400-1200 characters)"
103
+ }
104
+ ],
105
+ "hasValidation": true
106
+ },
107
+ {
108
+ "id": "analyze-learning-plan-comprehensive",
109
+ "runCondition": {
110
+ "var": "thoroughnessLevel",
111
+ "equals": "Comprehensive"
112
+ },
113
+ "title": "Phase 1: Expert Learning Plan Analysis (Comprehensive)",
114
+ "prompt": "Conduct thorough analysis of learning architecture for enterprise-grade materials:\n\n**STEP 1: Learning System Architecture**\n• Map complete learning objective hierarchy with dependencies\n• Analyze cognitive load and complexity progression\n• Identify multiple learning pathways and individual differences\n• Design assessment strategy aligned with learning taxonomies\n\n**STEP 2: Advanced Materials Strategy**\n• Determine optimal material types for each learning objective\n• Plan multi-modal approach for different learning styles\n• Design integration points for spaced repetition and active recall\n• Identify opportunities for interactive and adaptive elements\n\n**STEP 3: Quality & Effectiveness Framework**\n• Establish criteria for materials effectiveness measurement\n• Plan user testing and feedback integration\n• Design continuous improvement and iteration protocols\n• Create scalability and maintenance considerations\n\nGoal: Strategic foundation for optimized, enterprise-grade learning ecosystem.",
115
+ "agentRole": "You are an expert learning systems architect with deep expertise in advanced instructional design and learning optimization. Guide users in creating sophisticated materials that maximize learning effectiveness through evidence-based approaches.",
116
+ "guidance": [
117
+ "Apply advanced learning science principles and research",
118
+ "Focus on long-term effectiveness and optimization",
119
+ "Design for scalability and continuous improvement"
120
+ ],
121
+ "validationCriteria": [
122
+ {
123
+ "type": "contains",
124
+ "value": "effectiveness",
125
+ "message": "Must include effectiveness measurement planning"
99
126
  },
100
127
  {
101
- "id": "analyze-learning-plan-comprehensive",
102
- "runCondition": {
103
- "var": "thoroughnessLevel",
104
- "equals": "Comprehensive"
105
- },
106
- "title": "Phase 1: Expert Learning Plan Analysis (Comprehensive)",
107
- "prompt": "Conduct thorough analysis of learning architecture for enterprise-grade materials:\n\n**STEP 1: Learning System Architecture**\n\u2022 Map complete learning objective hierarchy with dependencies\n\u2022 Analyze cognitive load and complexity progression\n\u2022 Identify multiple learning pathways and individual differences\n\u2022 Design assessment strategy aligned with learning taxonomies\n\n**STEP 2: Advanced Materials Strategy**\n\u2022 Determine optimal material types for each learning objective\n\u2022 Plan multi-modal approach for different learning styles\n\u2022 Design integration points for spaced repetition and active recall\n\u2022 Identify opportunities for interactive and adaptive elements\n\n**STEP 3: Quality & Effectiveness Framework**\n\u2022 Establish criteria for materials effectiveness measurement\n\u2022 Plan user testing and feedback integration\n\u2022 Design continuous improvement and iteration protocols\n\u2022 Create scalability and maintenance considerations\n\nGoal: Strategic foundation for optimized, enterprise-grade learning ecosystem.",
108
- "agentRole": "You are an expert learning systems architect with deep expertise in advanced instructional design and learning optimization. Guide users in creating sophisticated materials that maximize learning effectiveness through evidence-based approaches.",
109
- "guidance": [
110
- "Apply advanced learning science principles and research",
111
- "Focus on long-term effectiveness and optimization",
112
- "Design for scalability and continuous improvement"
113
- ],
114
- "validationCriteria": [
115
- {
116
- "type": "contains",
117
- "value": "effectiveness",
118
- "message": "Must include effectiveness measurement planning"
119
- },
120
- {
121
- "type": "length",
122
- "min": 600,
123
- "max": 1500,
124
- "message": "Analysis should be sophisticated and comprehensive (600-1500 characters)"
125
- }
126
- ],
127
- "hasValidation": true
128
+ "type": "length",
129
+ "min": 600,
130
+ "max": 1500,
131
+ "message": "Analysis should be sophisticated and comprehensive (600-1500 characters)"
132
+ }
133
+ ],
134
+ "hasValidation": true
135
+ },
136
+ {
137
+ "id": "develop-materials-strategy-quick",
138
+ "runCondition": {
139
+ "var": "thoroughnessLevel",
140
+ "equals": "Quick"
141
+ },
142
+ "title": "Phase 2: Efficient Materials Strategy (Quick Start)",
143
+ "prompt": "Create a focused strategy for essential materials creation:\n\n**STEP 1: Format Selection**\n• Choose 1-2 primary formats based on your learning style\n• Prioritize formats you can create quickly (text-based, simple templates)\n• Plan minimal but consistent formatting approach\n• Focus on immediate usability over visual polish\n\n**STEP 2: Creation Workflow**\n• Design simple templates for study guides and exercises\n• Plan batch creation approach to maximize efficiency\n• Set realistic quality standards (functional over perfect)\n• Create basic organization system for easy access\n\n**STEP 3: Quality Framework**\n• Establish minimum viable product standards\n• Plan quick self-review process\n• Design simple feedback collection for future improvement\n• Focus on completion over perfection\n\nGoal: Practical strategy for rapid materials creation without sacrificing core functionality.",
144
+ "agentRole": "You are an efficiency expert specializing in rapid content creation. Help users design streamlined approaches that maximize output while maintaining essential quality. Focus on practical, time-saving strategies.",
145
+ "guidance": [
146
+ "Emphasize efficiency and speed over perfection",
147
+ "Choose simple, proven formats that work reliably",
148
+ "Design for immediate action and quick completion"
149
+ ],
150
+ "validationCriteria": [
151
+ {
152
+ "type": "contains",
153
+ "value": "template",
154
+ "message": "Must include template design for efficiency"
128
155
  },
129
156
  {
130
- "id": "develop-materials-strategy-quick",
131
- "runCondition": {
132
- "var": "thoroughnessLevel",
133
- "equals": "Quick"
134
- },
135
- "title": "Phase 2: Efficient Materials Strategy (Quick Start)",
136
- "prompt": "Create a focused strategy for essential materials creation:\n\n**STEP 1: Format Selection**\n\u2022 Choose 1-2 primary formats based on your learning style\n\u2022 Prioritize formats you can create quickly (text-based, simple templates)\n\u2022 Plan minimal but consistent formatting approach\n\u2022 Focus on immediate usability over visual polish\n\n**STEP 2: Creation Workflow**\n\u2022 Design simple templates for study guides and exercises\n\u2022 Plan batch creation approach to maximize efficiency\n\u2022 Set realistic quality standards (functional over perfect)\n\u2022 Create basic organization system for easy access\n\n**STEP 3: Quality Framework**\n\u2022 Establish minimum viable product standards\n\u2022 Plan quick self-review process\n\u2022 Design simple feedback collection for future improvement\n\u2022 Focus on completion over perfection\n\nGoal: Practical strategy for rapid materials creation without sacrificing core functionality.",
137
- "agentRole": "You are an efficiency expert specializing in rapid content creation. Help users design streamlined approaches that maximize output while maintaining essential quality. Focus on practical, time-saving strategies.",
138
- "guidance": [
139
- "Emphasize efficiency and speed over perfection",
140
- "Choose simple, proven formats that work reliably",
141
- "Design for immediate action and quick completion"
142
- ],
143
- "validationCriteria": [
144
- {
145
- "type": "contains",
146
- "value": "template",
147
- "message": "Must include template design for efficiency"
148
- },
149
- {
150
- "type": "length",
151
- "min": 300,
152
- "max": 900,
153
- "message": "Strategy should be focused and actionable (300-900 characters)"
154
- }
155
- ],
156
- "hasValidation": true
157
+ "type": "length",
158
+ "min": 300,
159
+ "max": 900,
160
+ "message": "Strategy should be focused and actionable (300-900 characters)"
161
+ }
162
+ ],
163
+ "hasValidation": true
164
+ },
165
+ {
166
+ "id": "develop-materials-strategy-comprehensive",
167
+ "runCondition": {
168
+ "var": "thoroughnessLevel",
169
+ "equals": "Comprehensive"
170
+ },
171
+ "title": "Phase 2: Advanced Materials Strategy (Comprehensive)",
172
+ "prompt": "Develop sophisticated strategy for enterprise-grade materials:\n\n**STEP 1: Multi-Modal Format Strategy**\n• Design format variety to engage different learning modes\n• Plan advanced visual elements, interactive components, adaptive features\n• Create sophisticated template system with consistent branding\n• Consider accessibility, mobile optimization, and universal design\n\n**STEP 2: Integration Architecture**\n• Plan seamless connections between all material types\n• Design advanced spaced repetition integration with learning analytics\n• Create sophisticated cross-referencing and linking systems\n• Plan for collaborative features and social learning elements\n\n**STEP 3: Quality Excellence Framework**\n• Establish enterprise-grade quality standards and measurement\n• Design comprehensive user testing and feedback integration\n• Plan continuous optimization based on learning effectiveness data\n• Create scalable maintenance and update protocols\n\nGoal: Strategic foundation for learning materials that optimize effectiveness through sophisticated design.",
173
+ "agentRole": "You are a learning systems architect with expertise in enterprise-grade materials design. Help users create sophisticated strategies that maximize learning effectiveness through advanced features and optimization.",
174
+ "guidance": [
175
+ "Apply advanced instructional design and learning optimization principles",
176
+ "Focus on long-term effectiveness and continuous improvement",
177
+ "Design for scalability and enterprise deployment"
178
+ ],
179
+ "validationCriteria": [
180
+ {
181
+ "type": "contains",
182
+ "value": "effectiveness",
183
+ "message": "Must focus on learning effectiveness measurement"
157
184
  },
158
185
  {
159
- "id": "develop-materials-strategy-comprehensive",
160
- "runCondition": {
161
- "var": "thoroughnessLevel",
162
- "equals": "Comprehensive"
163
- },
164
- "title": "Phase 2: Advanced Materials Strategy (Comprehensive)",
165
- "prompt": "Develop sophisticated strategy for enterprise-grade materials:\n\n**STEP 1: Multi-Modal Format Strategy**\n\u2022 Design format variety to engage different learning modes\n\u2022 Plan advanced visual elements, interactive components, adaptive features\n\u2022 Create sophisticated template system with consistent branding\n\u2022 Consider accessibility, mobile optimization, and universal design\n\n**STEP 2: Integration Architecture**\n\u2022 Plan seamless connections between all material types\n\u2022 Design advanced spaced repetition integration with learning analytics\n\u2022 Create sophisticated cross-referencing and linking systems\n\u2022 Plan for collaborative features and social learning elements\n\n**STEP 3: Quality Excellence Framework**\n\u2022 Establish enterprise-grade quality standards and measurement\n\u2022 Design comprehensive user testing and feedback integration\n\u2022 Plan continuous optimization based on learning effectiveness data\n\u2022 Create scalable maintenance and update protocols\n\nGoal: Strategic foundation for learning materials that optimize effectiveness through sophisticated design.",
166
- "agentRole": "You are a learning systems architect with expertise in enterprise-grade materials design. Help users create sophisticated strategies that maximize learning effectiveness through advanced features and optimization.",
167
- "guidance": [
168
- "Apply advanced instructional design and learning optimization principles",
169
- "Focus on long-term effectiveness and continuous improvement",
170
- "Design for scalability and enterprise deployment"
171
- ],
172
- "validationCriteria": [
173
- {
174
- "type": "contains",
175
- "value": "effectiveness",
176
- "message": "Must focus on learning effectiveness measurement"
177
- },
178
- {
179
- "type": "length",
180
- "min": 600,
181
- "max": 1400,
182
- "message": "Strategy should be sophisticated and comprehensive (600-1400 characters)"
183
- }
184
- ],
185
- "hasValidation": true
186
+ "type": "length",
187
+ "min": 600,
188
+ "max": 1400,
189
+ "message": "Strategy should be sophisticated and comprehensive (600-1400 characters)"
186
190
  }
187
- ]
191
+ ],
192
+ "hasValidation": true
193
+ }
194
+ ]
188
195
  }