@slamb2k/mad-skills 2.0.16 → 2.0.18

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "mad-skills",
   "description": "AI-assisted planning, development and governance tools",
-  "version": "2.0.16",
+  "version": "2.0.18",
   "author": {
     "name": "slamb2k",
     "url": "https://github.com/slamb2k"

package/README.md

@@ -412,29 +412,36 @@ Three methods are available. The table below shows what each delivers:
 
 ### Plugin (recommended)
 
+Installs skills, agents, and session hooks from the GitHub repo into
+`~/.claude/plugins/`. Updates automatically. Claude Code only.
+
+**Step 1 — Register the marketplace (one-time):**
+
+From the CLI:
+```bash
+claude plugin marketplace add slamb2k/mad-skills
 ```
-/plugin install mad-skills@slamb2k
+
+Or add manually to `~/.claude/settings.json`:
+```json
+"extraKnownMarketplaces": {
+  "slamb2k": {
+    "source": { "source": "github", "repo": "slamb2k/mad-skills" }
+  }
+}
+```
+
+**Step 2 — Install the plugin:**
+
+From the CLI:
+```bash
+claude plugin install mad-skills@slamb2k
 ```
 
-Installs skills, agents, and session hooks from the GitHub repo into `~/.claude/plugins/`. Updates automatically. Claude Code only.
-
-> **First time setup — add the marketplace (one-time):**
->
-> **Option A** — CLI (outside Claude Code):
-> ```bash
-> claude plugin marketplace add slamb2k/mad-skills
-> ```
->
-> **Option B** — Manual (add to `~/.claude/settings.json`):
-> ```json
-> "extraKnownMarketplaces": {
->   "slamb2k": {
->     "source": { "source": "github", "repo": "slamb2k/mad-skills" }
->   }
-> }
-> ```
->
-> Then install the plugin inside Claude Code with `/plugin install mad-skills@slamb2k`, or from the CLI with `claude plugin install mad-skills@slamb2k`.
+Or inside Claude Code:
+```
+/plugin install mad-skills@slamb2k
+```
 
 ### npx skills
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@slamb2k/mad-skills",
-  "version": "2.0.16",
+  "version": "2.0.18",
   "description": "Claude Code skills collection — planning, development and governance tools",
   "type": "module",
   "repository": {

package/skills/brace/SKILL.md

@@ -23,14 +23,39 @@ CRITICAL: Reproduce the banner EXACTLY character-for-character. The first line o
 ```
 
 Taglines:
-- Bracing the structure...
-- Reinforcing before load!
-- Locking in the framework!
-- Preparing for heavy lifting!
-- Cross-bracing the foundation!
-- Tightening the load path!
-- Structural integrity confirmed!
-- Brace for impact!
+- 🏗️ Bracing the structure...
+- 💪 Reinforcing before load!
+- 🔒 Locking in the framework!
+- 🏋️ Preparing for heavy lifting!
+- 🧱 Cross-bracing the foundation!
+- 🔧 Tightening the load path!
+- ✅ Structural integrity confirmed!
+- 💥 Brace for impact!
+
+---
+
+## Output Formatting
+
+After the banner, display parsed input:
+```
+┌─ Input ────────────────────────────────────────
+│  {Field}:  {value}
+│  Flags:    {parsed flags or "none"}
+└────────────────────────────────────────────────
+```
+
+Pre-flight results:
+```
+── Pre-flight ───────────────────────────────────
+  ✅ {dep}           {version or "found"}
+  ⚠️ {dep}           not found → {fallback detail}
+  ❌ {dep}           missing → stopping
+──────────────────────────────────────────────────
+```
+
+Stage/phase headers: `━━ {N} · {Name} ━━━━━━━━━━━━━━━━━━━━━━━━━`
+
+Status icons: ✅ done · ❌ failed · ⚠️ degraded · ⏳ working · ⏭️ skipped
 
 ---
 

package/skills/brace/references/report-template.md

@@ -5,38 +5,42 @@ Present this summary after verification completes.
 ---
 
 ```
-Brace Complete!
-
-  Project:   {project_name}
-  Directory: {cwd}
-
-  Structure:
-    {status} goals/         Goals layer
-    {status} tools/         Tools layer
-    {status} context/       Context layer
-    {status} hardprompts/   Hard prompts layer
-    {status} args/          Args layer
-    {status} .tmp/          Temp directory
-
-  Files:
-    {status} CLAUDE.md
-    {status} .gitignore
-    {status} goals/manifest.md
-    {status} goals/build_app.md
-    {status} tools/manifest.md
-
-  Removed: (only if legacy memory was cleaned up)
-    {status} tools/memory/     Legacy memory scripts
-    {status} memory/           Legacy memory directory
-
-  Notes:
-    {any warnings or skipped items}
-
-  Next steps:
-    1. Review CLAUDE.md and customise for your project
-    2. Add domain knowledge to context/
-    3. Define your first goal in goals/
-    4. Start building with the BRACE methodology
+┌─ Brace · Report ───────────────────────────────
+│
+│  ✅ Brace complete
+│
+│  📂 Project:   {project_name}
+│  📍 Directory: {cwd}
+│
+│  📝 Structure
+│     {✅|⏭️} goals/         Goals layer
+│     {✅|⏭️} tools/         Tools layer
+│     {✅|⏭️} context/       Context layer
+│     {✅|⏭️} hardprompts/   Hard prompts layer
+│     {✅|⏭️} args/          Args layer
+│     {✅|⏭️} .tmp/          Temp directory
+│
+│  📄 Files
+│     {✅|⏭️} CLAUDE.md
+│     {✅|⏭️} .gitignore
+│     {✅|⏭️} goals/manifest.md
+│     {✅|⏭️} goals/build_app.md
+│     {✅|⏭️} tools/manifest.md
+│
+│  🗑️ Removed (only if legacy memory was cleaned up)
+│     {✅} tools/memory/     Legacy memory scripts
+│     {✅} memory/           Legacy memory directory
+│
+│  ⚠️ Notes
+│     {any warnings or skipped items}
+│
+│  ⚡ Next steps
+│     1. Review CLAUDE.md and customise for your project
+│     2. Add domain knowledge to context/
+│     3. Define your first goal in goals/
+│     4. Start building with the BRACE methodology
+│
+└─────────────────────────────────────────────────
 ```
 
-Status indicators: [created] [exists] [merged] [upgraded] [removed] [skipped] [failed]
+Status indicators: ✅ created/exists · ⏭️ skipped · ⚠️ merged/upgraded · ❌ failed

package/skills/build/SKILL.md

@@ -34,6 +34,31 @@ Taglines:
 
 ---
 
+## Output Formatting
+
+After the banner, display parsed input:
+```
+┌─ Input ────────────────────────────────────────
+│  {Field}:  {value}
+│  Flags:    {parsed flags or "none"}
+└────────────────────────────────────────────────
+```
+
+Pre-flight results:
+```
+── Pre-flight ───────────────────────────────────
+  ✅ {dep}           {version or "found"}
+  ⚠️ {dep}           not found → {fallback detail}
+  ❌ {dep}           missing → stopping
+──────────────────────────────────────────────────
+```
+
+Stage/phase headers: `━━ {N} · {Name} ━━━━━━━━━━━━━━━━━━━━━━━━━`
+
+Status icons: ✅ done · ❌ failed · ⚠️ degraded · ⏳ working · ⏭️ skipped
+
+---
+
 Execute a detailed design/plan through the full feature-dev lifecycle with
 maximum context isolation. Every heavy stage runs in a subagent so the primary
 conversation only accumulates structured reports.
@@ -295,27 +320,33 @@ Invoke the `/ship` skill:
 ## Final Report
 
 ```
-Build complete
-
-  Plan:     {first line of PLAN}
-  Approach: {approach_summary}
-
-  Files modified: {count}
-  Files created:  {count}
-  Tests:          {passed}/{total}
-
-  Docs updated: {count or "none"}
-
-  PR: {pr_url} (merged at {merge_commit})
-
-  Key decisions:
-  - {decision 1}
-  - {decision 2}
-
-  Review findings addressed: {count fixed} / {count found}
-
-  Debrief: {count resolved} / {count surfaced} items addressed
-    {list of items created as goals or tasks, if any}
+┌─ Build · Report ───────────────────────────────
+│
+│  ✅ Build complete
+│
+│  📋 Plan:      {first line of plan}
+│  🏗️ Approach:  {approach_summary}
+│
+│  📝 Changes
+│     Files modified:  {count}
+│     Files created:   {count}
+│     Tests:           {passed}/{total} ✅
+│     Docs updated:    {count or "none"}
+│
+│  🔍 Review
+│     Findings addressed: {count fixed} / {count found}
+│
+│  📊 Debrief: {count resolved} / {count surfaced}
+│     {list of created goals/tasks}
+│
+│  🔗 Links
+│     PR:  {pr_url}
+│     CI:  {merge_commit}
+│
+│  ⚡ Next steps
+│     {debrief items or "none — all clear"}
+│
+└─────────────────────────────────────────────────
 ```
 
 If any stage failed, report the failure point and what was accomplished.

package/skills/distil/SKILL.md

@@ -23,14 +23,39 @@ CRITICAL: Reproduce the banner EXACTLY character-for-character. The first line o
 ```
 
 Taglines:
-- Heating up the column...
-- Fractioning the design space!
-- Condensing pure creativity!
-- Separating signal from noise!
-- Extracting the essence!
-- Refining through iteration!
-- Distilling N variations of brilliance!
-- From crude concept to pure design!
+- 🔥 Heating up the column...
+- 🧪 Fractioning the design space!
+- 💎 Condensing pure creativity!
+- 🔬 Separating signal from noise!
+- ⚗️ Extracting the essence!
+- 🔄 Refining through iteration!
+- ✨ Distilling N variations of brilliance!
+- 🎨 From crude concept to pure design!
+
+---
+
+## Output Formatting
+
+After the banner, display parsed input:
+```
+┌─ Input ────────────────────────────────────────
+│  {Field}:  {value}
+│  Flags:    {parsed flags or "none"}
+└────────────────────────────────────────────────
+```
+
+Pre-flight results:
+```
+── Pre-flight ───────────────────────────────────
+  ✅ {dep}           {version or "found"}
+  ⚠️ {dep}           not found → {fallback detail}
+  ❌ {dep}           missing → stopping
+──────────────────────────────────────────────────
+```
+
+Stage/phase headers: `━━ {N} · {Name} ━━━━━━━━━━━━━━━━━━━━━━━━━`
+
+Status icons: ✅ done · ❌ failed · ⚠️ degraded · ⏳ working · ⏭️ skipped
 
 ---
 
@@ -260,12 +285,29 @@ automatically — skip this step.
 
 ## Step 6: Present Designs
 
-Inform the user:
-- Dev server is running at `http://localhost:{PORT}`
-- Each design is available at `/1`, `/2`, `/3`, etc.
-- Briefly describe each design's unique approach (from DESIGN_REPORT)
-- Note which designs are new vs existing (if appending)
-- Remind they can iterate with `--favorites` to refine preferred designs
+Present the final summary:
+
+```
+┌─ Distil · Report ──────────────────────────────
+│
+│  ✅ Distil complete — {N} designs generated
+│
+│  🌐 Server: http://localhost:{PORT}
+│
+│  🎨 Designs
+│     /1  {style name} — {key visual traits}
+│     /2  {style name} — {key visual traits}
+│     /3  {style name} — {key visual traits}
+│     {mark new vs existing}
+│
+│  📊 Total: {total designs} ({new} new + {existing} existing)
+│
+│  ⚡ Next steps
+│     1. Browse designs at http://localhost:{PORT}/1
+│     2. Use --favorites 1,3 to iterate on selected designs
+│
+└─────────────────────────────────────────────────
+```
 
 ## Context Protection Summary
 

package/skills/dock/SKILL.md

@@ -56,6 +56,31 @@ Parse optional flags from the request:
 
 ---
 
+## Output Formatting
+
+After the banner, display parsed input:
+```
+┌─ Input ────────────────────────────────────────
+│  {Field}:  {value}
+│  Flags:    {parsed flags or "none"}
+└────────────────────────────────────────────────
+```
+
+Pre-flight results:
+```
+── Pre-flight ───────────────────────────────────
+  ✅ {dep}           {version or "found"}
+  ⚠️ {dep}           not found → {fallback detail}
+  ❌ {dep}           missing → stopping
+──────────────────────────────────────────────────
+```
+
+Stage/phase headers: `━━ {N} · {Name} ━━━━━━━━━━━━━━━━━━━━━━━━━`
+
+Status icons: ✅ done · ❌ failed · ⚠️ degraded · ⏳ working · ⏭️ skipped
+
+---
+
 ## Pre-flight
 
 Before starting, check dependencies:
@@ -315,24 +340,35 @@ Present the user with a summary of all generated files before writing.
 After all files are generated and verified, present:
 
 ```
-Dock complete
-
-  Stack:     {language} / {framework}
-  Registry:  {registry}
-  Stages:    {env1} → {env2} → {env3}
-
-  Generated files:
-    {file list with brief descriptions}
-
-  Pipeline flow:
-    PR → build + test → [push to registry]
-    Merge → build + test → push → deploy dev → smoke tests
-    Tag  → retag (no rebuild) → deploy staging → e2e → deploy prod → smoke
-
-  Next steps:
-    1. Review generated files
-    2. Configure secrets: {list of required secrets}
-    3. Push to trigger first pipeline run
+┌─ Dock · Report ────────────────────────────────
+│
+│  ✅ Dock complete
+│
+│  🔧 Stack:      {language} / {framework}
+│  📦 Registry:   {registry}
+│  🌍 Stages:     {env1} → {env2} → {env3}
+│
+│  📝 Generated files
+│     • {file} — {brief description}
+│     • {file} — {brief description}
+│     • ...
+│
+│  📊 Pipeline flow
+│     PR    → build + test
+│     Merge → build + test → push → deploy dev → smoke
+│     Tag   → retag (no rebuild) → staging → e2e → prod
+│
+│  🔗 Links
+│     Dockerfile:  {path}
+│     Workflow:    {path}
+│     Compose:     {path}
+│
+│  ⚡ Next steps
+│     1. Review generated files
+│     2. Configure secrets: {list}
+│     3. Push to trigger first pipeline run
+│
+└─────────────────────────────────────────────────
 ```
 
 ---

package/skills/keel/SKILL.md

@@ -61,6 +61,13 @@ Parse optional flags from the request:
 
 ---
 
+## Output Formatting
+
+Input display: `┌─ Input │ {fields} └─`. Pre-flight: `── Pre-flight ── ✅/⚠️/❌ ──`.
+Stage headers: `━━ {N} · {Name} ━━━━━━━━━━━━━`. Icons: ✅ done · ❌ fail · ⚠️ warn · ⏳ work · ⏭️ skip.
+
+---
+
 ## Pre-flight
 
 Before starting, check dependencies:
@@ -446,35 +453,27 @@ Present the user with a summary of all generated files before writing.
 After all files are generated and verified, present:
 
 ```
-Keel complete
-
-  Provider:  {cloud_provider}
-  IaC Tool:  {tool}
-  Envs:      {env1} → {env2} → {env3}
-  State:     {state_backend}
-
-  Components provisioned:
-    {checklist of selected components}
-
-  Generated files:
-    {file list with brief descriptions}
-
-  Pipeline flow:
-    PR  → terraform plan → comment on PR
-    Merge → terraform apply (dev) → sync outputs
-    Tag   → terraform apply (staging) → terraform apply (prod)
-
-  /dock integration:
-    Registry URL:  output from infra/outputs.tf
-    Compute:       {platform} provisioned per environment
-    Secrets:       synced via infra/sync-outputs.sh
-
-  Next steps:
-    1. Run bootstrap script: ./infra/bootstrap.sh
-    2. Review generated IaC files
-    3. Configure CI/CD secrets: {list}
-    4. Push to trigger first plan
-    5. After apply succeeds, run /dock to set up deployment pipelines
+┌─ Keel · Report ────────────────────────────────
+│
+│  ✅ Keel complete
+│
+│  ☁️ Provider:  {cloud_provider}
+│  🔧 IaC Tool:  {tool}
+│  🌍 Envs:      {env1} → {env2} → {env3}
+│  💾 State:     {state_backend}
+│
+│  📝 Components: {checklist of selected}
+│
+│  📊 Pipeline: PR → plan → Merge → apply dev → Tag → apply prod
+│
+│  🔗 Links
+│     Infra:     {infra/ path}
+│     Pipeline:  {workflow path}
+│     Bootstrap: ./infra/bootstrap.sh
+│
+│  ⚡ Next: 1. Run bootstrap  2. Configure secrets  3. Push  4. /dock
+│
+└─────────────────────────────────────────────────
 ```
 
 ---
@@ -492,7 +491,5 @@ If /keel detects it has been run before (existing `infra/` directory):
 
 ## Integration Points
 
-- **/dock**: /keel provisions what /dock deploys to. /dock pipelines consume
-  the outputs (registry URL, compute endpoints) as deployment targets.
-- **/rig**: Detects `infra/` and wires IaC pipeline into CI workflow.
-- **/ship**: Merge triggers IaC apply → /dock deploy chain.
+- **/dock**: /keel provisions what /dock deploys to. /dock consumes outputs (registry URL, compute endpoints).
+- **/rig**: Detects `infra/` and wires IaC pipeline into CI. **/ship**: Merge triggers IaC apply → /dock deploy.

package/skills/manifest.json

@@ -1,12 +1,12 @@
 {
-  "generated": "2026-03-09T17:01:26.694Z",
+  "generated": "2026-03-09T17:23:53.026Z",
   "count": 10,
   "skills": [
     {
       "name": "brace",
       "directory": "brace",
       "description": "'Initialize any project directory with the GOTCHA/BRACE framework for agentic AI systems. Creates the 6-layer structure (Goals, Orchestration, Tools, Context, Hard prompts, Args), BRACE build methodology, and a project CLAUDE.md. Recommends claude-mem for persistent memory. Idempotent — safe to run on existing projects. Triggers: \"init gotcha\", \"setup brace\", \"brace\", \"initialize framework\", \"bootstrap gotcha\".'",
-      "lines": 278,
+      "lines": 303,
       "hasScripts": false,
       "hasReferences": true,
       "hasAssets": true,
@@ -16,7 +16,7 @@
       "name": "build",
       "directory": "build",
       "description": "Context-isolated feature development pipeline. Takes a detailed design/plan as argument and executes the full feature-dev lifecycle (explore, question, architect, implement, review, ship) inside subagents so the primary conversation stays compact. Use when you have a well-defined plan and want autonomous execution with minimal context window consumption.",
-      "lines": 332,
+      "lines": 363,
       "hasScripts": false,
       "hasReferences": true,
       "hasAssets": false,
@@ -26,7 +26,7 @@
       "name": "distil",
       "directory": "distil",
       "description": "Generate multiple unique web design variations for any website or web application. Accepts site specifications from a file (--spec path) or pasted text block. Creates a Vite + React + TypeScript + Tailwind project with Bun and produces N different creative designs accessible at /1, /2, /3, etc. Use when prototyping or exploring design directions for any web interface.",
-      "lines": 290,
+      "lines": 332,
       "hasScripts": false,
       "hasReferences": true,
       "hasAssets": true,
@@ -36,7 +36,7 @@
       "name": "dock",
       "directory": "dock",
       "description": ">- Generate container-based release pipelines that build once and promote immutable artifacts through environments (dev → staging → prod). Detects your stack, interviews for infrastructure choices, then outputs deterministic CI/CD files (Dockerfile, workflows, deployment manifests) that run without an LLM. Use when setting up deployment pipelines, containerizing an app, creating release workflows, or connecting CI to container-friendly infrastructure (Azure Container Apps, AWS Fargate, Google Cloud Run, Kubernetes, Dokku, Coolify, CapRover, etc.).",
-      "lines": 358,
+      "lines": 394,
       "hasScripts": false,
       "hasReferences": true,
       "hasAssets": false,
@@ -46,7 +46,7 @@
       "name": "keel",
       "directory": "keel",
       "description": ">- Generate Infrastructure as Code (IaC) pipelines that provision the cloud and container infrastructure your app deploys to. Interview-driven: detects your stack and cloud provider, then outputs deterministic IaC files (Terraform, Bicep, Pulumi, or CDK) plus CI/CD pipelines that plan on PR and apply on merge. Use when setting up cloud infrastructure, provisioning container registries, databases, networking, DNS, or any infrastructure that containers deploy onto. Designed to run before /dock — /keel lays the infrastructure, /dock deploys to it.",
-      "lines": 499,
+      "lines": 496,
       "hasScripts": false,
       "hasReferences": true,
       "hasAssets": false,
@@ -56,7 +56,7 @@
       "name": "prime",
       "directory": "prime",
       "description": "\"Load project context before implementing features or making architectural decisions. Invoke proactively at the start of significant work on any project. Scans CLAUDE.md, README, goals/, specs/, docs/, and source structure to build a context summary. Supports optional domain hints to focus on specific areas of the codebase. Use when you need project conventions, architecture understanding, or domain context before coding.\"",
-      "lines": 113,
+      "lines": 148,
       "hasScripts": false,
       "hasReferences": true,
       "hasAssets": false,
@@ -66,7 +66,7 @@
       "name": "rig",
       "directory": "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\".'",
-      "lines": 206,
+      "lines": 231,
       "hasScripts": false,
       "hasReferences": true,
       "hasAssets": true,
@@ -76,7 +76,7 @@
       "name": "ship",
       "directory": "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.\"",
-      "lines": 227,
+      "lines": 262,
       "hasScripts": false,
       "hasReferences": true,
       "hasAssets": false,
@@ -86,7 +86,7 @@
       "name": "speccy",
       "directory": "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.",
-      "lines": 170,
+      "lines": 210,
       "hasScripts": false,
       "hasReferences": true,
       "hasAssets": false,
@@ -96,7 +96,7 @@
       "name": "sync",
       "directory": "sync",
       "description": "Sync local repository with origin/main. Use before starting new work, after completing a PR, or when needing latest upstream changes. Safely stashes uncommitted changes, fetches and pulls origin/main, restores stash, and cleans up stale local branches (merged or with deleted remotes). Invoke when switching contexts or preparing for new feature work.",
-      "lines": 213,
+      "lines": 244,
       "hasScripts": false,
       "hasReferences": false,
       "hasAssets": false,

package/skills/prime/SKILL.md

@@ -34,6 +34,31 @@ Taglines:
 
 ---
 
+## Output Formatting
+
+After the banner, display parsed input:
+```
+┌─ Input ────────────────────────────────────────
+│  {Field}:  {value}
+│  Flags:    {parsed flags or "none"}
+└────────────────────────────────────────────────
+```
+
+Pre-flight results:
+```
+── Pre-flight ───────────────────────────────────
+  ✅ {dep}           {version or "found"}
+  ⚠️ {dep}           not found → {fallback detail}
+  ❌ {dep}           missing → stopping
+──────────────────────────────────────────────────
+```
+
+Stage/phase headers: `━━ {N} · {Name} ━━━━━━━━━━━━━━━━━━━━━━━━━`
+
+Status icons: ✅ done · ❌ failed · ⚠️ degraded · ⏳ working · ⏭️ skipped
+
+---
+
 Load project context to inform agent decisions. Raw file contents stay in a
 subagent — the primary thread only sees a structured PRIME_REPORT.
 
@@ -100,12 +125,22 @@ PRIME_REPORT:
 Parse PRIME_REPORT and present a clean summary to the user:
 
 ```
-Context loaded:
-- Core: {status from core_files_loaded}
-- {Domain}: {summary from per_domain_summary}
-
-Current branch: {branch}
-Ready to assist with: {ready_for}
+┌─ Prime · Report ───────────────────────────────
+│
+│  ✅ Context loaded
+│
+│  📚 Core:   {count}/{total} files loaded
+│  🌐 Branch: {branch}
+│
+│  📝 Domains
+│     {domain}: {2-3 line summary}
+│     {domain}: {2-3 line summary}
+│
+│  ⚠️ Missing: {list or "none"}
+│
+│  🎯 Ready to assist with: {ready_for}
+│
+└─────────────────────────────────────────────────
 ```
 
 If CLAUDE.md was missing, warn the user and note that only domain context

package/skills/rig/SKILL.md

@@ -23,14 +23,39 @@ CRITICAL: Reproduce the banner EXACTLY character-for-character. The first line o
 ```
 
 Taglines:
-- Rigging up the production line...
-- Bolting down the framework!
-- Assembling the scaffolding!
-- Hoisting the infrastructure!
-- Locking in the safety harness!
-- Wiring up the control panel!
-- Setting up the drill floor!
-- From blueprint to build-ready!
+- 🏗️ Rigging up the production line...
+- 🔩 Bolting down the framework!
+- 🪜 Assembling the scaffolding!
+- 🏗️ Hoisting the infrastructure!
+- 🦺 Locking in the safety harness!
+- ⚡ Wiring up the control panel!
+- 🛠️ Setting up the drill floor!
+- 📐 From blueprint to build-ready!
+
+---
+
+## Output Formatting
+
+After the banner, display parsed input:
+```
+┌─ Input ────────────────────────────────────────
+│  {Field}:  {value}
+│  Flags:    {parsed flags or "none"}
+└────────────────────────────────────────────────
+```
+
+Pre-flight results:
+```
+── Pre-flight ───────────────────────────────────
+  ✅ {dep}           {version or "found"}
+  ⚠️ {dep}           not found → {fallback detail}
+  ❌ {dep}           missing → stopping
+──────────────────────────────────────────────────
+```
+
+Stage/phase headers: `━━ {N} · {Name} ━━━━━━━━━━━━━━━━━━━━━━━━━`
+
+Status icons: ✅ done · ❌ failed · ⚠️ degraded · ⏳ working · ⏭️ skipped
 
 ---
 

package/skills/rig/references/report-template.md

@@ -3,26 +3,29 @@
 Present this summary after all configuration is complete:
 
 ```
-Rig Complete!
-
-Repository: {repo_name}
-Branch: {branch}
-
-Configured:
-  {status} Lefthook installed and configured
-  {status} Pre-commit hooks: {list of hooks}
-  {status} Pre-push hooks: {list of hooks}
-  {status} Commit template: .gitmessage
-  {status} PR template: {.github/pull_request_template.md | .azuredevops/pull_request_template.md}
-  {status} CI workflow: {.github/workflows/ci.yml | azure-pipelines.yml}
-  {if azdo and pipelines registered:}
-  {status} Azure Pipelines registered: {list of pipeline names}
-
-Notes:
-  {any warnings, e.g., "Branch is 'master', consider renaming to 'main'"}
-
-Next steps:
-  1. Review generated files and commit them
-  2. Push to remote to activate CI
-  3. Test hooks with: lefthook run pre-commit
+┌─ Rig · Report ─────────────────────────────────
+│
+│  ✅ Rig complete
+│
+│  📂 Repository: {repo_name}
+│  🌐 Branch:     {branch}
+│
+│  📝 Configured
+│     {✅|⏭️} Lefthook installed and configured
+│     {✅|⏭️} Pre-commit hooks: {list}
+│     {✅|⏭️} Pre-push hooks: {list}
+│     {✅|⏭️} Commit template: .gitmessage
+│     {✅|⏭️} PR template: {path}
+│     {✅|⏭️} CI workflow: {path}
+│     {✅|⏭️} Azure Pipelines: {list} (if applicable)
+│
+│  ⚠️ Notes
+│     {any warnings}
+│
+│  ⚡ Next steps
+│     1. Review generated files and commit them
+│     2. Push to remote to activate CI
+│     3. Test hooks: lefthook run pre-commit
+│
+└─────────────────────────────────────────────────
 ```

package/skills/ship/SKILL.md

@@ -34,6 +34,31 @@ Taglines:
 
 ---
 
+## Output Formatting
+
+After the banner, display parsed input:
+```
+┌─ Input ────────────────────────────────────────
+│  {Field}:  {value}
+│  Flags:    {parsed flags or "none"}
+└────────────────────────────────────────────────
+```
+
+Pre-flight results:
+```
+── Pre-flight ───────────────────────────────────
+  ✅ {dep}           {version or "found"}
+  ⚠️ {dep}           not found → {fallback detail}
+  ❌ {dep}           missing → stopping
+──────────────────────────────────────────────────
+```
+
+Stage/phase headers: `━━ {N} · {Name} ━━━━━━━━━━━━━━━━━━━━━━━━━`
+
+Status icons: ✅ done · ❌ failed · ⚠️ degraded · ⏳ working · ⏭️ skipped
+
+---
+
 Ship changes through the complete PR lifecycle. Every stage runs in a subagent
 to isolate context from the primary conversation. Prompts for each stage are
 in `references/stage-prompts.md`.
@@ -211,16 +236,26 @@ Parse LAND_REPORT.
 Compile all stage reports into a summary:
 
 ```
-Ship complete
-
-  Branch:  {branch}
-  PR:      {pr_url}
-  Merged:  {merge_commit} ({merge_type})
-
-  Commits:
-  {list of commit messages, indented}
-
-  Files:   {count} files changed ({diff_summary})
+┌─ Ship · Report ────────────────────────────────
+│
+│  ✅ Ship complete
+│
+│  🌿 Branch:  {branch}
+│  🔗 PR:      {pr_url}
+│  🔀 Merged:  {merge_commit} ({merge_type})
+│
+│  📝 Commits
+│     • {commit message 1}
+│     • {commit message 2}
+│
+│  📊 {count} files changed ({diff_summary})
+│
+└─────────────────────────────────────────────────
 ```
 
-If any stage failed, report the failure point and suggested resolution.
+If any stage failed, add:
+```
+│  ❌ Failed at: {stage name}
+│     {error description}
+│     {suggested resolution}
+```

package/skills/speccy/SKILL.md

@@ -34,6 +34,31 @@ Taglines:
 
 ---
 
+## Output Formatting
+
+After the banner, display parsed input:
+```
+┌─ Input ────────────────────────────────────────
+│  {Field}:  {value}
+│  Flags:    {parsed flags or "none"}
+└────────────────────────────────────────────────
+```
+
+Pre-flight results:
+```
+── Pre-flight ───────────────────────────────────
+  ✅ {dep}           {version or "found"}
+  ⚠️ {dep}           not found → {fallback detail}
+  ❌ {dep}           missing → stopping
+──────────────────────────────────────────────────
+```
+
+Stage/phase headers: `━━ {N} · {Name} ━━━━━━━━━━━━━━━━━━━━━━━━━`
+
+Status icons: ✅ done · ❌ failed · ⚠️ degraded · ⏳ working · ⏭️ skipped
+
+---
+
 Interview the user through multiple rounds of targeted questions to build
 a comprehensive specification. Then hand off to the `create-specification`
 skill to produce the final structured spec document.
@@ -159,11 +184,26 @@ Once the interview is complete and decisions are confirmed:
 After the spec is created, report to the user:
 
 ```
-Spec complete!
-
-  File:       {spec file path}
-  Sections:   {count of sections written}
-  Decisions:  {count of interview decisions captured}
-  Rounds:     {count of interview rounds conducted}
-  Questions:  {total questions asked}
+┌─ Speccy · Report ──────────────────────────────
+│
+│  ✅ Spec complete
+│
+│  📄 File:       {spec file path}
+│  📋 Sections:   {count}
+│  💬 Rounds:     {interview rounds conducted}
+│  ❓ Questions:  {total questions asked}
+│
+│  📝 Key decisions
+│     • {decision 1}
+│     • {decision 2}
+│     • {decision 3}
+│
+│  🔗 Links
+│     Spec: {spec file path}
+│
+│  ⚡ Next steps
+│     1. Review the spec: {path}
+│     2. Run /build {spec path} to implement
+│
+└─────────────────────────────────────────────────
 ```

package/skills/sync/SKILL.md

@@ -34,6 +34,31 @@ Taglines:
 
 ---
 
+## Output Formatting
+
+After the banner, display parsed input:
+```
+┌─ Input ────────────────────────────────────────
+│  {Field}:  {value}
+│  Flags:    {parsed flags or "none"}
+└────────────────────────────────────────────────
+```
+
+Pre-flight results:
+```
+── Pre-flight ───────────────────────────────────
+  ✅ {dep}           {version or "found"}
+  ⚠️ {dep}           not found → {fallback detail}
+  ❌ {dep}           missing → stopping
+──────────────────────────────────────────────────
+```
+
+Stage/phase headers: `━━ {N} · {Name} ━━━━━━━━━━━━━━━━━━━━━━━━━`
+
+Status icons: ✅ done · ❌ failed · ⚠️ degraded · ⏳ working · ⏭️ skipped
+
+---
+
 Synchronize local repository with the remote default branch using a single
 Bash subagent to isolate all git operations from the primary conversation.
 
@@ -199,14 +224,20 @@ SYNC_REPORT:
 Parse the subagent's SYNC_REPORT and present a clean summary:
 
 ```
-Sync complete
-  Main:    {commit} - {message}
-  Branch:  {current_branch}
-  Stash:   {status}
-  Cleaned: {branches or "none"}
+┌─ Sync · Report ────────────────────────────────
+│
+│  ✅ Sync complete
+│
+│  🌿 Main:     {commit} — {message}
+│  🔀 Branch:   {current_branch}
+│  📦 Stash:    {restored|none|conflict}
+│  🧹 Cleaned:  {branches or "none"}
+│
+└─────────────────────────────────────────────────
 ```
 
-If errors occurred, report them clearly with suggested resolution:
-- Detached HEAD → suggest `git checkout <branch>`
-- Rebase conflict → suggest `git rebase {DEFAULT_BRANCH}` manually and resolve
-- Stash conflict → suggest `git stash show` and `git stash pop` manually
+If errors occurred:
+```
+│  ❌ {error description}
+│     {suggested resolution}
+```