@a5c-ai/babysitter-cursor 0.1.1-staging.04cc300a

package/skills/observe/SKILL.md

@@ -0,0 +1,13 @@
+---
+name: observe
+description: Launch the babysitter observer dashboard. Installs and runs the real-time observer UI that watches babysitter runs, displaying task progress, journal events, and orchestration state in your browser.
+---
+
+# observe
+
+Run the babysitter observer dashboard:
+
+1. Determine the watch directory — this is usually the project's container directory (the parent of the project dir), or the current working directory if not specified.
+2. Launch the dashboard: `npx -y @a5c-ai/babysitter-observer-dashboard@latest --watch-dir <dir>`
+3. This is a blocking process — it will keep running until stopped.
+4. Open the browser at the URL printed by the dashboard.

package/skills/plan/SKILL.md

@@ -0,0 +1,8 @@
+---
+name: plan
+description: Plan a babysitter run. use this command to plan a complex workflow, without actually running it.
+---
+
+# plan
+
+Invoke the babysitter:babysit skill (using the Skill tool) and follow its instructions (SKILL.md). focus on creating the best process possible, but without creating and running the actual run.

package/skills/resume/SKILL.md

@@ -0,0 +1,9 @@
+---
+name: resume
+description: Resume orchestrating of a babysitter run. use this command to resume babysitting a complex workflow.
+---
+
+# resume
+
+Invoke the babysitter:babysit skill (using the Skill tool) and follow its instructions (SKILL.md). to resume a run.
+if no run was given, discover the runs and suggest which incomplete run to resume based on the run's status, inputs, process , etc.

package/skills/retrospect/SKILL.md

@@ -0,0 +1,56 @@
+---
+name: retrospect
+description: Analysis for a run and its results, process, suggestions for process improvements, process optimizations, fixes, etc. for the next runs.
+---
+
+# retrospect
+
+Invoke the babysitter:babysit skill (using the Skill tool) and follow its instructions (SKILL.md).
+
+create and run a retrospect process:
+
+### Run Selection
+
+- `--all` or "all runs": list all completed/failed runs and analyze collectively
+- Multiple run IDs: analyze each specified run
+- Single run ID or no ID: existing behavior (latest run)
+- In interactive mode with no run specified: ask user whether to analyze latest, select specific runs, or all runs
+
+### Cross-Run Analysis (multi-run mode)
+
+When analyzing multiple runs, the retrospect process should additionally cover:
+- Common failure patterns across runs
+- Velocity trends (tasks/time across runs)
+- Process evolution (how processes changed)
+- Repeated breakpoint patterns
+- Aggregate quality metrics
+
+implementations notes (for the process):
+- The process should analyze the run, the process that was followed, and provide suggestions for improvements, optimizations, and fixes.
+- The process should such have many breakpoints where the user can steer the process, provide feedback, and make decisions about how to proceed with the retrospect.
+- The process should be designed to be flexible and adaptable to different types of runs, projects, and goals, and should be able to provide insights and suggestions that are relevant and actionable for the user. (modification to the process, skills, etc.)
+- The process should be designed to be iterative, allowing the user to go through multiple rounds of analysis and improvement, and should be able to track the changes and improvements made over time.
+- The process should cover:
+    - Analysis of the run and its results, including what went well, what didn't go well, and what could be improved.
+    - Analysis of the process that was followed, including what steps were taken, what tools were used, and how effective they were.
+    - Suggestions for improvements, optimizations, and fixes for both the run and the process.
+    - Implementing the improvements, optimizations, and fixes, and tracking the changes made over time.
+### Cleanup Suggestion
+
+After retrospect analysis, suggest running `/babysitter:cleanup` to clean up old run data and reclaim disk space.
+
+    - Ending by explicitly prompting the user to contribute back -- even just reporting an issue is valuable, they don't need to implement the fix themselves. After analysis, display a clear call-to-action:
+
+      "You've identified [specific insight/improvement]. This could help other babysitter users too. Run `/babysitter:contrib` to share it upstream -- you can either report it as an issue or submit a PR with the fix."
+
+      Route to the specific contrib workflow based on what the user wants to do:
+
+      **Just reporting (no code changes needed):**
+      - Found a bug or weakness in a process -> `/babysitter:contrib bug report: [description of what went wrong]`
+      - Found missing or confusing documentation -> `/babysitter:contrib documentation question: [what was unclear]`
+      - Have an idea for improvement but don't want to implement it -> `/babysitter:contrib feature request: [description]`
+
+      **Contributing code changes:**
+      - Process/skill/agent improvements -> `/babysitter:contrib library contribution: [description]`
+      - Bug fixes in SDK or CLI -> `/babysitter:contrib bugfix: [description]`
+      - Plugin instruction improvements -> `/babysitter:contrib library contribution: improved [plugin-name] [install|configure|uninstall] instructions`

package/skills/user-install/SKILL.md

@@ -0,0 +1,18 @@
+---
+name: user-install
+description: Set up babysitter for yourself. Guides you through onboarding — installs dependencies, interviews you about your specialties and preferences, builds your user profile, and configures the best tools for your workflow.
+---
+
+# user-install
+
+Invoke the babysitter:babysit skill (using the Skill tool) and follow its instructions (SKILL.md).
+
+Before using the process library, resolve the active library root through the SDK CLI. If no binding exists yet, initialize the shared global SDK binding with:
+
+```bash
+babysitter process-library:active --json
+```
+
+Then use the `cradle/user-install` process from the active process library.
+
+When the run completes, end with a friendly message that includes a polite and humorous ask to star the repo on GitHub: https://github.com/a5c-ai/babysitter

package/versions.json

@@ -0,0 +1,3 @@
+{
+  "sdkVersion": "0.0.184-staging.04cc300a"
+}