procedure-cli 1.7.1 → 1.9.0

package/templates/skills/b3awesome-procedure-setup/SKILL.md

@@ -0,0 +1,132 @@
+---
+name: b3awesome-procedure-setup
+description: Post-setup procedure guardian — on a fresh Procedure CLI install it runs a tech-stack verification wizard; on a working folder it back-fills missing procedure sections into the agent .md files. Pass --verify to force the wizard anywhere.
+---
+
+# b3awesome Procedure Setup
+
+One skill, two paths, chosen by detection. Every interaction follows the
+**Visual Confirmation rule** (see bottom).
+
+## Invocation
+
+```
+/b3awesome-procedure-setup            # auto-detect: fresh → wizard, working → back-fill
+/b3awesome-procedure-setup --verify   # force the tech-stack verification wizard
+```
+
+## Detection — fresh install or working folder?
+
+```
+/b3awesome-procedure-setup [--verify]
+          │
+          ▼
+┌─────────────────────────────┐  "--verify" passed
+│ Was --verify passed?        ├────────────────────► WIZARD (skip detection)
+└──────────────┬──────────────┘
+               │ no
+               ▼
+┌─────────────────────────────────────────────┐
+│ SIGNAL 1 — review logs still virgin?        │
+│ CODE-REVIEW.md has no CR- entries AND       │
+│ CODE-FIXED.md has no CF- entries            │
+└──────────────┬──────────────────────────────┘
+               │ any entry → WORKING FOLDER
+               ▼ virgin
+┌─────────────────────────────────────────────┐
+│ SIGNAL 2 — git history pristine?            │
+│ exactly 1 commit, message contains          │
+│ "scaffolded by Procedure CLI"               │
+│ (no git repo → skip this signal)            │
+└──────────────┬──────────────────────────────┘
+               │ >1 commit / other message → WORKING FOLDER
+               ▼ pristine
+┌─────────────────────────────────────────────┐
+│ SIGNAL 3 — marker file                      │
+│ .claude/procedure-cli.json                  │
+│ { version, generatedAt } written at         │
+│ generation. Older repos lack it → rely on   │
+│ signals 1+2 only                            │
+└──────────────┬──────────────────────────────┘
+               ▼
+      ┌────────┴────────┐
+ FRESH INSTALL      WORKING FOLDER
+ → WIZARD           (ambiguous defaults here — safe: the wizard
+                     never auto-runs; --verify is the override)
+```
+
+## Path: FRESH INSTALL — Tech-Stack Verification Wizard
+
+```
+① READ generated docs: docs/PRD.md, docs/USER-STORIES.md,
+  CLAUDE.md, AGENTS.md
+          ▼
+② CONVERSATIONAL WIZARD — one question at a time:
+  • Requirements ↔ Language        • Framework ↔ Product type
+  • DB / Infra ↔ Scale             • Team skill ↔ Learning cost
+  anything unclear → ask to clarify before moving on
+          ▼
+③ PROPOSE changes (if any) with rationale + trade-offs,
+  presented WITH ASCII diagrams (Visual Confirmation rule)
+          ▼
+④ WAIT FOR APPROVAL — until approved, change NOTHING
+  (no doc edits, no stack changes)
+```
+
+This is a conversation in the chat session — not a code/TUI wizard.
+
+## Path: WORKING FOLDER — Back-fill agent docs
+
+```
+  repo's agent .md files            canonical procedure sections
+  (CLAUDE.md, AGENTS.md,            (list below — this SKILL.md is
+   other agent .md if present)       the canon, updated via
+          │                          procedure-cli-skills-copy.sh)
+          └──────────────┬──────────────────┘
+                         ▼
+          ┌───────────────────────────────────┐
+          │ DIFF by SECTION:                  │
+          │ • Code Review & Fix Logging       │
+          │ • Companion Skills note (MP set)  │
+          │ • Tech-Stack Verification rule    │
+          │ • Visual Confirmation rule        │
+          └──────────────┬────────────────────┘
+                         ▼
+          ┌───────────────────────────────────┐
+          │ APPEND missing sections only.     │
+          │ NEVER edit or delete existing     │
+          │ sections — even when they look    │
+          │ older than the canon. Lessons and │
+          │ customizations stay intact.       │
+          └──────────────┬────────────────────┘
+                         ▼
+          Report: gaps filled + gaps SKIPPED (section present
+          but stale) → the user decides about manual upgrades.
+          Then STOP. Tell the user: run
+          /b3awesome-procedure-setup --verify for the wizard.
+```
+
+### Canonical sections to check
+
+1. **Code Review & Fix Logging** — CR-/CF- append-only log procedure. If missing, derive the section from the `/b3awesome-code-review` and `/b3awesome-code-fix` skills installed in this repo.
+2. **Companion Skills note** — the review/fix skills invoke Matt Pocock companion skills (`code-review`, `codebase-design`, `diagnosing-bugs`, `tdd`) installed globally by Procedure CLI, never carried inside the project.
+3. **Tech-Stack Verification** — after Procedure CLI setup, verify the chosen stack against requirements via `/b3awesome-procedure-setup --verify`: read generated docs, wizard one question at a time, clarify, propose, wait for approval.
+4. **Visual Confirmation** — see below; copy the rule text verbatim.
+
+## Rules
+
+- Never modify or delete existing sections in any agent .md file — append only.
+- Never touch `CODE-REVIEW.md` / `CODE-FIXED.md` history.
+- Never change tech stack or docs without explicit approval (wizard step ④).
+- If both paths have nothing to do (all sections present, not fresh), say so and stop.
+
+## Visual Confirmation rule (applies to every interaction)
+
+Whenever the user must review, clarify, confirm, or approve anything, present
+it WITH a fitting ASCII visual:
+
+- **Wireframe** — UI or layout decisions
+- **Screen flow** — navigation and user journeys
+- **Diagram** — architecture, data flow, sequences, relationships
+
+Plain-prose proposals without a visual are not acceptable for approval requests.