@slamb2k/mad-skills 2.0.14 → 2.0.16

package/skills/prime/references/domains.md

@@ -1,38 +1,35 @@
-# Domain-to-File Mapping
+# Domain Context Resolution
 
-Each domain lists the files/directories to load for that context area.
-Paths are relative to the project root.
+When domain hints are provided, resolve them to files using these strategies
+(in priority order). Stop at the first strategy that produces results.
 
-## security
-- `args/security.yaml`
-- `tools/security/` (list directory)
+## Resolution Strategy
 
-## routing
-- `args/routing.yaml`
-- `tools/agent/model_router/ROUTING_ARCHITECTURE.md`
+1. **Exact directory match** — Look for a directory named `{hint}/` in common
+   locations: `src/`, `lib/`, `app/`, `packages/`, `services/`, project root
+2. **File pattern match** — Glob for `**/*{hint}*.md`, `**/*{hint}*.yaml`,
+   `**/*{hint}*.json` (exclude node_modules, .git, dist, build)
+3. **Config/docs match** — Check `docs/{hint}.md`, `docs/{hint}/`,
+   `config/{hint}.*`, `.{hint}rc`, `{hint}.config.*`
 
-## adhd
-- `context/adhd_design_principles.md`
-- `args/adhd_mode.yaml`
+## Common Domain Hints
 
-## dashboard
-- `args/dashboard.yaml`
-- `tools/dashboard/backend/routes/` (list directory)
-- `tools/dashboard/frontend/app/` (list directory)
+These are examples — any directory or topic name works as a hint:
 
-## office
-- `args/office_integration.yaml`
-- `tools/office/` (list directory)
+| Hint | Likely Locations |
+|------|-----------------|
+| auth | src/auth/, lib/auth/, middleware/auth.* |
+| api | src/api/, routes/, controllers/ |
+| db, database | src/db/, prisma/, migrations/, models/ |
+| infra | infra/, terraform/, bicep/, deploy/ |
+| frontend | src/components/, src/pages/, app/ |
+| backend | src/server/, src/services/, api/ |
+| config | config/, .env.example, settings/ |
+| test | tests/, __tests__/, spec/, cypress/ |
 
-## memory
-- `args/memory.yaml`
-- `args/working_memory.yaml`
-- `tools/memory/` (list directory)
+## Output
 
-## tasks
-- `args/task_engine.yaml`
-- `tools/tasks/` (list directory)
-
-## channels
-- `args/channels.yaml`
-- `tools/channels/` (list directory)
+For each resolved domain, include in PRIME_REPORT:
+- Directory/file paths found
+- 2-3 line summary of what was found
+- Key patterns or conventions observed

package/skills/rig/SKILL.md

@@ -2,7 +2,7 @@
 name: rig
 description: 'Idempotently bootstrap any repository with standard development tools, hooks, and workflows. Use when starting work on a new repo, onboarding to an existing project, or ensuring a repo has proper CI/CD setup. Configures: git hooks (lefthook), commit message templates, PR templates, and GitHub Actions for lint/format/type-check/build. Prompts for user confirmation before changes. Triggers: "bootstrap repo", "setup hooks", "configure CI", "rig", "standardize repo".'
 argument-hint: --skip-system-check (optional)
-allowed-tools: Bash, Read, Write, Edit, Glob, Grep, AskUserQuestion
+allowed-tools: Bash, Read, Write, Edit, Glob, Grep, Agent, AskUserQuestion
 ---
 
 # Rig - Repository Bootstrap
@@ -50,6 +50,7 @@ Before starting, check all dependencies in this table:
 | Dependency | Type | Check | Required | Resolution | Detail |
 |-----------|------|-------|----------|------------|--------|
 | git | cli | `git --version` | yes | stop | Install from https://git-scm.com |
+| sync | skill | `.claude/skills/sync/SKILL.md` | no | fallback | Repo sync; falls back to manual git pull |
 | lefthook | npm | `npx lefthook --help` | yes | install | `npm install -g lefthook` |
 | gh | cli | `gh --version` | yes | url | https://cli.github.com |
 
@@ -66,6 +67,14 @@ For each row, in order:
 
 ---
 
+## Phase 0: Sync
+
+Invoke `/sync` to ensure the working tree is up to date with origin/main before
+bootstrapping. If /sync is unavailable, run `git pull` manually. This prevents
+rigging against stale repo state.
+
+---
+
 ## Phase 1: System Requirements Check
 
 Launch **Bash subagent** (haiku — simple checks):

package/skills/ship/SKILL.md

@@ -2,7 +2,7 @@
 name: ship
 description: "Ship changes through the full PR lifecycle. Use after completing feature work to commit, push, create PR, wait for checks, and merge. Handles the entire workflow: syncs with main, creates feature branch if needed, groups commits logically with semantic messages, creates detailed PR, monitors CI, fixes issues, squash merges, and cleans up. Invoke when work is ready to ship."
 argument-hint: --pr-only, --no-squash, --keep-branch (optional flags)
-allowed-tools: Bash, Read, Glob, Grep, Skill
+allowed-tools: Bash, Read, Glob, Grep, Agent, Skill
 ---
 
 # Ship - Full PR Lifecycle

package/skills/ship/references/stage-prompts.md

@@ -294,20 +294,12 @@ BRANCH_FLAGS: {--delete-branch (default) | omit if --keep-branch}
          --delete-source-branch $DELETE_BRANCH
      fi
 
-2. **Sync local {DEFAULT_BRANCH}**
-   git checkout {DEFAULT_BRANCH}
-   git pull {REMOTE} {DEFAULT_BRANCH}
+2. **Sync local repository**
+   Invoke `/sync` to checkout {DEFAULT_BRANCH}, pull latest changes, restore
+   any stashed work, and clean up merged branches. This replaces manual git
+   checkout/pull/fetch/prune — /sync handles all of it including stash restore.
 
-3. **Restore working state** (if there were stashed changes)
-   git stash pop (only if stash exists from Stage 1)
-
-4. **Cleanup stale branches**
-   git fetch --prune
-   for branch in $(git branch -vv | grep ': gone]' | awk '{print $1}'); do
-     git branch -d "$branch" 2>/dev/null
-   done
-
-5. **Report**
+3. **Report**
    MERGE_COMMIT=$(git rev-parse --short HEAD)
 
 ## Output Format

package/skills/speccy/SKILL.md

@@ -2,7 +2,7 @@
 name: speccy
 description: Deep-dive interview skill for creating comprehensive specifications. Reviews existing code and docs, then interviews the user through multiple rounds of targeted questions covering technical implementation, UI/UX, concerns, and tradeoffs. Produces a structured spec via create-specification. Use when starting a new feature, system, or major change that needs a spec.
 argument-hint: Goal, feature, or high-level description to specify
-allowed-tools: Bash, Read, Write, Edit, Glob, Grep, AskUserQuestion
+allowed-tools: Bash, Read, Write, Edit, Glob, Grep, Agent, AskUserQuestion
 ---
 
 # Speccy - Interview-Driven Specification Builder
@@ -47,6 +47,7 @@ Before starting, check all dependencies in this table:
 | Dependency | Type | Check | Required | Resolution | Detail |
 |-----------|------|-------|----------|------------|--------|
 | create-specification | skill | `~/.claude/skills/create-specification/SKILL.md` or `~/.agents/skills/create-specification/SKILL.md` | yes | ask | This skill is needed to format the final spec. Install with: `npx skills add slamb2k/mad-skills --skill create-specification` |
+| prime | skill | `.claude/skills/prime/SKILL.md` | no | fallback | Context loading; falls back to manual project scan |
 
 For each row, in order:
 1. Test file existence (check both paths for symlinked skills)
@@ -63,7 +64,10 @@ For each row, in order:
 Before asking any questions, build a thorough understanding of the project:
 
 1. **Capture GOAL** — the user's argument describing what needs to be specified
-2. **Scan the project**:
+2. **Load project context** — invoke `/prime` to load domain-specific context
+   (CLAUDE.md, goals, specs, memory). If /prime is unavailable, fall back to
+   the manual scan below.
+3. **Scan the project** (skip items already loaded by /prime):
    - Read `CLAUDE.md` if present (project conventions, structure, domain)
    - Read goal/spec manifests: `goals/manifest.md`, `spec/` directory
    - Scan existing specs and design docs for context