@jenga-ai/agent 1.0.0

package/skills/self-sync/scripts/run.js

@@ -0,0 +1,136 @@
+#!/usr/bin/env node
+/**
+ * skills/self-sync/scripts/run.js — In-repo mirror runner
+ *
+ * Mirrors this repo's root-level framework directories into its own
+ * `.claude/` and `.agents/` sub-trees so edits to `/skills/*`, `/agents/*`,
+ * `/hooks/*`, etc. take effect in the current Claude Code / non-Claude agent
+ * session without a `/distribute` cycle.
+ *
+ * Wraps lib/mirror.js — same helper used by scripts/postinstall.js — but
+ * with `reconcileDeletes: true` so orphans in the mirrors are pruned.
+ *
+ * Flags:
+ *   --dry-run    Print the plan without writing.
+ */
+import fs from 'node:fs';
+import path from 'node:path';
+import { fileURLToPath } from 'node:url';
+
+import { mirror } from '../../../lib/mirror.js';
+
+const __filename = fileURLToPath(import.meta.url);
+const __dirname = path.dirname(__filename);
+
+// Repo root is four levels up: run.js → scripts → self-sync → skills → repo
+const REPO_ROOT = path.resolve(__dirname, '..', '..', '..');
+
+// Explicit copy set — documented in SKILL.md.
+// Aligned with package.json `files`, plus `settings.json` (not shipped in
+// the npm tarball but required in-repo so Claude Code picks it up locally).
+const COPY_SET = [
+  'bin',
+  'lib',
+  'scripts',
+  'agents',
+  'hooks',
+  'mcp',
+  'skills',
+  'templates',
+  'settings.json',
+];
+
+const DEST_ROOTS = ['.claude', '.agents'];
+
+// Basenames to skip anywhere in the walk. These are recursive mirror
+// artifacts, dev caches, or scm dirs that must never propagate into the
+// agent-visible mirror. `.agents` and `.claude` in particular can appear
+// nested inside `agents/` and `skills/` from legacy distribute runs.
+const EXCLUDE = [
+  '.agents',
+  '.claude',
+  '.git',
+  '.tmp',
+  '.training',
+  'node_modules',
+  '.DS_Store',
+];
+
+function parseArgs(argv) {
+  const dryRun = argv.includes('--dry-run');
+  return { dryRun };
+}
+
+function short(p) {
+  return path.relative(REPO_ROOT, p) || '.';
+}
+
+function printSection(label, items) {
+  if (items.length === 0) return;
+  console.log(`  ${label} (${items.length}):`);
+  for (const item of items) {
+    console.log(`    - ${short(item)}`);
+  }
+}
+
+function main() {
+  const { dryRun } = parseArgs(process.argv.slice(2));
+
+  console.log('');
+  console.log('╔══════════════════════════════════════════════════════╗');
+  console.log(`║  /self-sync — mirror root → .claude/ + .agents/      ║`);
+  console.log('╚══════════════════════════════════════════════════════╝');
+  console.log(`  Repo root : ${REPO_ROOT}`);
+  console.log(`  Copy set  : ${COPY_SET.join(', ')}`);
+  console.log(`  Dry-run   : ${dryRun ? 'YES (no writes)' : 'no'}`);
+  console.log('');
+
+  const missing = COPY_SET.filter(
+    (entry) => !fs.existsSync(path.join(REPO_ROOT, entry))
+  );
+  if (missing.length > 0) {
+    console.log(`  ⚠  Missing from repo root — skipped: ${missing.join(', ')}`);
+    console.log('');
+  }
+
+  const totals = { added: 0, overwritten: 0, deleted: 0, skipped: 0 };
+
+  for (const targetRoot of DEST_ROOTS) {
+    const destRoot = path.join(REPO_ROOT, targetRoot);
+    console.log(`→ ${targetRoot}/`);
+
+    const result = mirror({
+      sourceRoot: REPO_ROOT,
+      destRoot,
+      copySet: COPY_SET,
+      dryRun,
+      reconcileDeletes: true,
+      exclude: EXCLUDE,
+    });
+
+    printSection('added', result.added);
+    printSection('overwritten', result.overwritten);
+    printSection('deleted', result.deleted);
+    console.log(
+      `  summary: +${result.added.length} ~${result.overwritten.length} -${result.deleted.length} =${result.skipped.length}`
+    );
+    console.log('');
+
+    totals.added += result.added.length;
+    totals.overwritten += result.overwritten.length;
+    totals.deleted += result.deleted.length;
+    totals.skipped += result.skipped.length;
+  }
+
+  console.log('──────────────────────────────────────────────────────');
+  console.log(
+    `  Total: +${totals.added} added  ~${totals.overwritten} overwritten  -${totals.deleted} deleted  =${totals.skipped} unchanged`
+  );
+  if (dryRun) {
+    console.log('  (dry-run — nothing was written)');
+  }
+  console.log('──────────────────────────────────────────────────────');
+  console.log('');
+}
+
+main();

package/skills/skillify/SKILL.md

@@ -0,0 +1,68 @@
+---
+name: skillify
+description: Refactor one or more existing skills into a cleaner, more maintainable structure — extracting hardcoded content into asset files, offloading deterministic steps into scripts, and reorganizing the skill body to reflect the leaner result. Use this whenever the user wants to clean up, improve, or restructure an existing skill, mentions that a skill has hardcoded content that could be templated, or asks to "skillify", "refactor", or "tidy up" a skill. Trigger even if the user just pastes a skill and says something like "can we make this better?".
+---
+
+# Skillify — Refactor a Skill into a Cleaner Structure
+
+## What this skill does
+
+Takes one or more existing skills and refactors them by:
+- Extracting hardcoded file content (JSON, Markdown, config, etc.) into `assets/` templates
+- Extracting hardcoded directory lists into `assets/` reference files
+- Moving deterministic multi-step sequences into `scripts/` bash scripts
+- Rewriting the skill body to delegate to those scripts and assets, keeping instructions lean
+
+See `assets/init-old/SKILL.md` and `assets/init-new/SKILL.md` for a concrete before/after example.
+
+---
+
+## Instructions
+
+### 1. Read the skill(s)
+
+Read every SKILL.md the user references. If they also reference scripts or assets already in the skill, read those too.
+
+### 2. Identify refactor opportunities
+
+For each skill, look for:
+
+| Pattern | Refactor to |
+|---|---|
+| Hardcoded file content written inline (heredoc, echo, cat) | `assets/<name>_template.<ext>` copied via `cp` |
+| Hardcoded list of directories or paths | `assets/<name>.txt` read via a `while read` loop |
+| Sequential deterministic steps (create files, run commands) | `scripts/<name>.sh` executed by the skill |
+| `SCRIPT_DIR` defined repeatedly across steps | Define once at top of script |
+
+### 3. Confirm the plan with the user
+
+Before making changes, summarise what you found and what you propose to extract. List:
+- Which files will move to `assets/`
+- Which steps will move to `scripts/`
+- What the updated skill body will look like
+
+Get a thumbs-up before proceeding.
+
+### 4. Produce the outputs
+
+For each change:
+- Write the extracted asset files with their content
+- Write or update the bash script(s), following the structure in `assets/init-new/SKILL.md`
+- Rewrite the skill body so each offloaded step becomes a single `cp` or script call with a short explanation
+
+### 5. Update the skill body
+
+The rewritten SKILL.md should:
+- Keep narrative and conversational steps in the skill body (things Claude decides or explains)
+- Delegate all deterministic file/directory operations to scripts
+- Reference asset files by name so it's clear what exists where
+- Stay concise — if a step is now just "run the script", say so in one line
+
+---
+
+## Reference files
+
+- `assets/init-old/SKILL.md` — The init skill before refactoring (hardcoded heredocs, inline JSON, hardcoded directory list)
+- `assets/init-new/SKILL.md` — The init skill after refactoring (all content in assets, steps delegated to `init.sh`)
+
+Read these when you need a concrete example of the before/after pattern.

package/skills/skillify/assets/init-new/SKILL.md

@@ -0,0 +1,35 @@
+---
+name: init
+description: Initialize a new project with the standard directory structure, PROJECT_SUMMARY.md, workflow.json, git repo, and gitignore. Follows a defined ordered onboarding sequence. Use when setting up a new or empty project.
+---
+
+# Init — Project Setup
+
+## Instructions
+
+Follow these steps in order. Do not skip steps — the sequence matters.
+
+### 1–9. Run the scaffold script
+
+Execute the init script from the project root:
+
+```bash
+chmod +x ./scripts/init.sh && ./scripts/init.sh
+```
+
+This script handles all scaffolding in one step:
+1. Initializes the git repository
+2. Creates `.gitignore`
+3. Creates the full directory structure under `project/`
+4. Creates `project/PROJECT_SUMMARY.md` with placeholder content
+5. Creates `project/configs/workflow.json` with shared constants
+6. Creates `project/configs/test-config.json` stub
+7. Creates `project/data/baselines.json`
+8. Creates `project/logs/events.json`
+9. Stages and commits all files with the message `init: scaffold project structure and workflow config`
+
+If the script fails, check that you are in the project root and that git is available.
+
+### 10. Prompt next step
+
+Inform the user that setup is complete and suggest running `/pi-plan` to define project goals and epics.

package/skills/skillify/assets/init-new/assets/.gitignore_template

@@ -0,0 +1,15 @@
+# macOS & Windows system files
+.DS_Store
+Thumbs.db
+Desktop.ini
+
+# Environment files
+.env
+.env.*
+*.local
+
+# Dependency directories
+node_modules/
+vendor/
+.venv/
+EOF

package/skills/skillify/assets/init-new/assets/PROJECT_SUMMARY_template.md

@@ -0,0 +1,13 @@
+# Project Summary
+
+## Overview
+_To be completed._
+
+## Architecture & Structure
+_To be completed._
+
+## Epics
+_To be completed via /pi-plan._
+
+## Conventions
+_To be completed._

package/skills/skillify/assets/init-new/assets/directory_structure.txt

@@ -0,0 +1,10 @@
+project/board/epics
+project/board/stories
+project/board/tasks
+project/configs
+project/data
+project/queue
+project/rapports/problems
+project/rapports/analysis
+project/logs
+documentation

package/skills/skillify/assets/init-new/assets/test-config_template.json

@@ -0,0 +1,4 @@
+{
+  "_note": "Run the tester agent to configure tools for this project.",
+  "tools": []
+}

package/skills/skillify/assets/init-new/assets/workflow_template.json

@@ -0,0 +1,17 @@
+{
+  "statuses": ["Pending", "In Progress", "Passed", "Passed with remarks", "Failed", "Rejected", "Blocked"],
+  "rapport_types": ["conflict", "implementation_blocker", "security_concern", "test_failure", "analysis"],
+  "paths": {
+    "board": "project/board",
+    "epics": "project/board/epics",
+    "stories": "project/board/stories",
+    "tasks": "project/board/tasks",
+    "rapports_problems": "project/rapports/problems",
+    "rapports_analysis": "project/rapports/analysis",
+    "queue": "project/queue",
+    "logs": "project/logs",
+    "data": "project/data",
+    "configs": "project/configs"
+  },
+  "agents": ["developer", "tester", "scrum-master"]
+}

package/skills/skillify/assets/init-new/scripts/init.sh

@@ -0,0 +1,48 @@
+#!/usr/bin/env bash
+set -euo pipefail
+
+SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+ASSETS_DIR="$SCRIPT_DIR/../assets"
+
+# ─── 1. Initialize git repository ────────────────────────────────────────────
+echo "→ Initializing git repository..."
+git init
+
+# ─── 2. Create .gitignore ─────────────────────────────────────────────────────
+echo "→ Copying .gitignore from template..."
+cp "$ASSETS_DIR/.gitignore_template" .gitignore
+
+# ─── 3. Scaffold directory structure ──────────────────────────────────────────
+echo "→ Scaffolding directory structure..."
+while IFS= read -r dir || [[ -n "$dir" ]]; do
+  [[ -z "$dir" || "$dir" == \#* ]] && continue
+  mkdir -p "$dir"
+done < "$ASSETS_DIR/directory_structure.txt"
+
+# ─── 4. Create project/PROJECT_SUMMARY.md ────────────────────────────────────
+echo "→ Copying PROJECT_SUMMARY.md from template..."
+cp "$ASSETS_DIR/PROJECT_SUMMARY_template.md" project/PROJECT_SUMMARY.md
+
+# ─── 5. Create project/configs/workflow.json ─────────────────────────────────
+echo "→ Copying workflow.json from template..."
+cp "$ASSETS_DIR/workflow_template.json" project/configs/workflow.json
+
+# ─── 6. Create project/configs/test-config.json stub ─────────────────────────
+echo "→ Copying test-config.json from template..."
+cp "$ASSETS_DIR/test-config_template.json" project/configs/test-config.json
+
+# ─── 7. Create project/data/baselines.json ───────────────────────────────────
+echo "→ Creating baselines.json..."
+echo '{}' > project/data/baselines.json
+
+# ─── 8. Create project/logs/events.json ──────────────────────────────────────
+echo "→ Creating events.json..."
+echo '[]' > project/logs/events.json
+
+# ─── 9. Initial commit ───────────────────────────────────────────────────────
+echo "→ Staging and committing scaffolded files..."
+git add -A
+git commit -m "init: scaffold project structure and workflow config"
+
+echo ""
+echo "✓ Project scaffold complete."

package/skills/skillify/assets/init-old/SKILL.md

@@ -0,0 +1,124 @@
+---
+name: init
+description: Initialize a new project with the standard directory structure, PROJECT_SUMMARY.md, workflow.json, git repo, and gitignore. Follows a defined ordered onboarding sequence. Use when setting up a new or empty project.
+---
+
+# Init — Project Setup
+
+## Instructions
+
+Follow these steps in order. Do not skip steps — the sequence matters.
+
+### 1. Initialize git repository
+Run `git init` in the project root. Do **not** set up any remote origin.
+
+### 2. Create `.gitignore`
+Ignore the following at minimum:
+- macOS and Windows system files: `.DS_Store`, `Thumbs.db`, `Desktop.ini`
+- Environment files: `.env`, `.env.*`, `*.local`
+- Dependency directories: `node_modules/`, `vendor/`, `.venv/`
+
+### 3. Scaffold directory structure
+
+Create the following directories:
+
+```
+project/
+  board/
+    epics/
+    stories/
+    tasks/
+  configs/
+  data/
+  queue/
+  rapports/
+    problems/
+    analysis/
+  logs/
+  documentation/
+    plans/
+    summaries/
+```
+
+### 4. Create `project/PROJECT_SUMMARY.md`
+
+Create the file with the following placeholder structure. The scrum master will populate it during the `/pi-plan` flow.
+
+```markdown
+# Project Summary
+
+## Overview
+_To be completed._
+
+## Architecture & Structure
+_To be completed._
+
+## Epics
+_To be completed via /pi-plan._
+
+## Conventions
+_To be completed._
+```
+
+### 5. Create `project/configs/workflow.json`
+
+Write the shared constants file:
+
+```json
+{
+  "statuses": ["Pending", "In Progress", "Passed", "Passed with remarks", "Failed", "Rejected", "Blocked"],
+  "rapport_types": ["conflict", "implementation_blocker", "security_concern", "test_failure", "analysis"],
+  "paths": {
+    "board": "project/board",
+    "epics": "project/board/epics",
+    "stories": "project/board/stories",
+    "tasks": "project/board/tasks",
+    "rapports_problems": "project/rapports/problems",
+    "rapports_analysis": "project/rapports/analysis",
+    "queue": "project/queue",
+    "logs": "project/logs",
+    "data": "project/data",
+    "configs": "project/configs"
+  },
+  "agents": ["developer", "tester", "scrum-master"]
+}
+```
+
+### 6. Create `project/configs/test-config.json` stub
+
+Write a minimal stub so the tester agent knows to configure it:
+
+```json
+{
+  "_note": "Run the tester agent to configure tools for this project.",
+  "tools": []
+}
+```
+
+### 7. Create `project/data/baselines.json`
+
+Write an empty baselines file:
+
+```json
+{}
+```
+
+### 8. Create `project/logs/events.json`
+
+Initialize the event log:
+
+```json
+[]
+```
+
+### 9. Initial commit
+
+Stage and commit all scaffolded files:
+
+```
+init: scaffold project structure and workflow config
+```
+
+### 10. Prompt next step
+
+Inform the user that setup is complete and suggest running `/pi-plan` to define project goals and epics.

package/skills/spinoff/SKILL.md

@@ -0,0 +1,48 @@
+---
+name: spinoff
+description: Capture a diverging topic mid-conversation. Collects context, optionally runs /brainstorm for prerequisites, saves a /todo entry, and returns focus to the primary thread.
+keywords:
+  - spinoff
+  - diverge
+  - side topic
+  - capture topic
+  - new thread
+examples:
+  - "let's spinoff this idea"
+  - "capture this as a separate thread"
+metadata:
+  prefered_agent: scrum-master
+---
+
+# Spinoff — Capture a Diverging Topic
+
+## Instructions
+
+1. **Identify the diverging topic** — Ask the user to confirm or briefly describe the diverging topic.
+   - Pre-fill the prompt with a one-sentence summary of what the agent detected as the diverging subject (if known).
+   - Example: *"It looks like we started discussing [detected topic]. Is that the diverging thread you'd like to capture, or would you like to describe it differently?"*
+
+2. **Collect context** — Summarise the relevant context gathered so far in the current conversation that relates to the diverging topic. This summary will pre-fill the `/todo` description so no context is lost.
+
+3. **Check prerequisites** — Ask the user:
+   > "Are the requirements for **[diverging topic]** clear enough to act on, or would you like to run `/brainstorm` first to flesh them out?"
+
+   Offer these choices:
+   - **"Requirements are clear — save the todo now"** → go to step 5
+   - **"Run /brainstorm first"** → go to step 4
+
+4. **Run /brainstorm (if chosen)** — Invoke the `/brainstorm` skill, passing the diverging topic and collected context as the opening prompt. After `/brainstorm` completes, use the refined output as the todo description.
+
+5. **Save the /todo** — Populate `skills/todo/assets/todo_handoff_template.md` with the context collected so far:
+   - **Mission title**: the diverging topic name (as confirmed in step 1)
+   - **Goal / objective**: what the diverging topic aims to achieve
+   - **Affected files or scope**: any files or modules identified during the conversation
+   - **Intended approach**: the context/approach collected in step 2 (or the refined output from step 4)
+   - **Epic/Story linkage**: include a reference if a relevant Epic or Story was identified, otherwise `None`
+
+   Then invoke the `/todo` skill with the populated template. Since the template fields are pre-filled, `/todo` will skip any questions already answered.
+
+6. **Return focus** — Inform the user:
+   > "✅ Diverging topic saved as a todo. Returning focus to **[primary topic]**."
+
+   Then resume the primary conversation thread exactly where it was paused.

package/skills/status/SKILL.md

@@ -0,0 +1,33 @@
+---
+name: status
+description: Print a human-readable summary of the entire scrum board — all epics, stories, and tasks with their statuses — plus any open rapports and unprocessed queue triggers. Use when you want a quick overview of project state without reading raw files.
+keywords:
+  - status
+  - board summary
+  - overview
+  - project state
+  - what's done
+examples:
+  - "show me the project status"
+  - "what's the state of the board?"
+---
+
+# Status — Board Overview
+
+## Instructions
+
+1. **Read `project/configs/workflow.json`** to confirm board paths. Fall back to `project/board/` if the file does not exist.
+
+2. **Scan epics** — Read all files in `project/board/epics/`. For each epic, extract: `id`, `title`, `status`, `date_started`, `date_completed`, and the `stories` list.
+
+3. **Scan stories** — For each story referenced in the epics list, read its file from `project/board/stories/`. Extract: `id`, `title`, `status`, `tasks` list.
+
+4. **Scan tasks** — For each task referenced in each story, read its file from `project/board/tasks/`. Extract: `id`, `title`, `status`, `assigned_to`.
+
+5. **Scan open rapports** — List all `.md` files in `project/rapports/problems/` that do **not** end in `.IGNORE.md`. List all `.md` files in `project/rapports/analysis/`.
+
+6. **Check the queue** — If `project/queue/scrum_triggers.jsonl` is non-empty, note the number of pending triggers awaiting the scrum master.
+
+7. **Print the summary** following the layout and icon conventions in `assets/output_format.md`.
+
+8. If no epics exist, print: `No board items found. Run /pi-plan to define epics or /todo to add items.`

package/skills/status/assets/output_format.md

@@ -0,0 +1,41 @@
+## Output Format
+
+```
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+ PROJECT STATUS
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+📦 E01 · <Epic Title>  [<Status>]
+   📖 E01_S01 · <Story Title>  [<Status>]
+      ✅ E01_S01_T01 · <Task Title>  [Passed]
+      🔄 E01_S01_T02 · <Task Title>  [In Progress]
+      ⏳ E01_S01_T03 · <Task Title>  [Pending]
+   📖 E01_S02 · <Story Title>  [<Status>]
+      ...
+
+📦 E02 · <Epic Title>  [<Status>]
+   ...
+
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+ OPEN RAPPORTS  (2)
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+⚠️  problems/E01_S02-auth-conflict.md
+📊  analysis/E01-performance-baseline.md
+
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+ QUEUE  (1 pending trigger for scrum master)
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+```
+
+## Status Icons
+
+| Icon | Status |
+|------|--------|
+| ✅ | Passed / Passed with remarks |
+| ❌ | Failed / Rejected |
+| 🔄 | In Progress |
+| ⏳ | Pending |
+| 🚫 | Blocked |
+| 📦 | Epic |
+| 📖 | Story |
+| 🔧 | Task |

package/skills/todo/SKILL.md

@@ -0,0 +1,46 @@
+---
+name: todo
+description: Add missions to the project todo list (project/todo.md), optionally linking them to epics and stories. Loops until the user is done, then optionally executes the list.
+keywords:
+  - todo
+  - add task
+  - queue work
+  - backlog
+  - add to list
+examples:
+  - "add this to the todo list"
+  - "queue this as a task"
+metadata: 
+  prefered_agent: scrum-master
+---
+
+# Todo — Add Missions to the Todo List
+
+## Instructions
+
+1. **Ensure `project/todo.md` exists** — If it doesn't exist, it will be auto-created by `todo_manager.sh` — no manual action needed.
+
+2. **Ask the user about the mission:**
+   - Where do you want to do this?
+   - What would you like to do?
+   - What is the goal?
+
+3. **Classify the mission** — Check if it fits into:
+   - An existing story
+   - A new story inside an existing Epic
+   - A new story inside a new Epic
+   - None of the above
+
+4. **Update project documentation** — Add the mission to the appropriate files under `project/board/epics/` and `project/board/stories/` if applicable.
+
+5. **Add to `project/todo.md`** by running:
+   ```
+   bash scripts/todo_manager.sh add '<mission title>: <Epic no.>_<Story no.>'
+   ```
+   The epic and story reference is only required if the mission is assigned to one.
+
+6. **Ask the user**: "Add another todo" or "Done"?
+   - If **add another** — go back to step 2.
+   - If **done** — ask if they want to execute the todo list.
+     - If **yes** — invoke the `/do` skill.
+     - If **no** — exit.

package/skills/todo/assets/todo_handoff_template.md

@@ -0,0 +1,22 @@
+# Todo Handoff
+
+<!-- PREAMBLE (for /todo): This template was pre-filled by a caller (e.g. /redo, /spinoff).
+     Skip any questions whose answers are already provided below. Only prompt the user
+     for fields that remain empty or marked as a placeholder. -->
+
+<!-- Format: <mission title>: <E##_S##> (epic/story ref optional) -->
+
+## Mission Title
+<!-- PLACEHOLDER: short name for this todo item, e.g. "Refactor auth middleware" -->
+
+## Goal / Objective
+<!-- PLACEHOLDER: what this todo is trying to achieve -->
+
+## Affected Files or Scope
+<!-- PLACEHOLDER: which files, modules, or areas are involved, e.g. src/auth/, skills/todo/ -->
+
+## Intended Approach
+<!-- PLACEHOLDER: step-by-step or high-level approach to the work -->
+
+## Epic / Story Linkage
+<!-- PLACEHOLDER: known Epic or Story ID this links to, e.g. E02_S03 — or "None" if not linked -->