bigpowers 2.34.1 → 2.34.2

package/.pi/package.json

@@ -1,7 +1,7 @@
 {
   "name": "bigpowers",
-  "version": "2.34.1",
-  "description": "70 skills — 61 agent skills for spec-driven, test-first software development by solo developers",
+  "version": "2.34.2",
+  "description": "70 skills — 70 agent skills for spec-driven, test-first software development by solo developers",
   "keywords": [
     "pi-package"
   ],

package/.pi/prompts/deploy.md

@@ -86,6 +86,53 @@ exit 1
 
 After invoking the deploy command, poll for completion:
 
+See [REFERENCE.md](REFERENCE.md)
+
+Use exponential backoff for retries on transient failures:
+
+See [REFERENCE.md](REFERENCE.md)
+
+### 6. Baseline smoke test
+
+See [REFERENCE.md](REFERENCE.md)
+
+For comprehensive health-checking, chain to the `smoke-test` skill:
+
+```bash
+# After deploy success
+bash scripts/run-smoke.sh "$DEPLOY_URL"
+```
+
+---
+
+# Deploy — Reference
+
+## Configuration
+
+| Variable | Default | Description |
+|----------|---------|-------------|
+| `ARTIFACT_DIR` | `dist` | Build output directory |
+| `DEPLOY_URL` | *(required)* | Live URL for smoke test |
+| `DEPLOY_TIMEOUT` | `300` | Max wait for deploy completion (seconds) |
+| `DEPLOY_POLL_INTERVAL` | `30` | Polling interval (seconds) |
+| `RETRY_MAX` | `3` | Max deploy retry attempts |
+| `BUILD_COMMAND` | *(auto-detect)* | Override build command |
+
+
+---
+
+## Verification
+
+→ verify: `test -f deploy/SKILL.md && grep -q 'name: deploy' deploy/SKILL.md && echo OK`
+→ verify: `grep -qi 'build\|artifact\|deploy\|smoke' deploy/SKILL.md && echo OK`
+→ verify: `grep -ci 'package.json\|Cargo.toml\|Makefile\|manifest' deploy/SKILL.md | awk '{if($1>=1) print "OK"; else print "FAIL"}'`
+→ verify: `grep -ci 'timeout\|poll\|status\|retry\|backoff' deploy/SKILL.md | awk '{if($1>=2) print "OK"; else print "FAIL"}'`
+→ verify: `grep -q 'curl.*DEPLOY_URL\|smoke\|health' deploy/SKILL.md && echo OK`
+
+---
+
+## Reference block 1
+
 ```bash
 DEPLOY_TIMEOUT="${DEPLOY_TIMEOUT:-300}"   # seconds (default 5 minutes)
 DEPLOY_POLL_INTERVAL="${DEPLOY_POLL_INTERVAL:-30}"  # seconds
@@ -108,7 +155,9 @@ while true; do
 done
 ```
 
-Use exponential backoff for retries on transient failures:
+---
+
+## Reference block 2
 
 ```bash
 RETRY_MAX="${RETRY_MAX:-3}"
@@ -125,7 +174,9 @@ for attempt in $(seq 1 "$RETRY_MAX"); do
 done
 ```
 
-### 6. Baseline smoke test
+---
+
+## Reference block 3
 
 ```bash
 DEPLOY_URL="${DEPLOY_URL:?DEPLOY_URL must be set}"
@@ -136,29 +187,3 @@ else
   exit 1
 fi
 ```
-
-For comprehensive health-checking, chain to the `smoke-test` skill:
-
-```bash
-# After deploy success
-bash scripts/run-smoke.sh "$DEPLOY_URL"
-```
-
-## Configuration
-
-| Variable | Default | Description |
-|----------|---------|-------------|
-| `ARTIFACT_DIR` | `dist` | Build output directory |
-| `DEPLOY_URL` | *(required)* | Live URL for smoke test |
-| `DEPLOY_TIMEOUT` | `300` | Max wait for deploy completion (seconds) |
-| `DEPLOY_POLL_INTERVAL` | `30` | Polling interval (seconds) |
-| `RETRY_MAX` | `3` | Max deploy retry attempts |
-| `BUILD_COMMAND` | *(auto-detect)* | Override build command |
-
-## Verification
-
-→ verify: `test -f deploy/SKILL.md && grep -q 'name: deploy' deploy/SKILL.md && echo OK`
-→ verify: `grep -qi 'build\|artifact\|deploy\|smoke' deploy/SKILL.md && echo OK`
-→ verify: `grep -ci 'package.json\|Cargo.toml\|Makefile\|manifest' deploy/SKILL.md | awk '{if($1>=1) print "OK"; else print "FAIL"}'`
-→ verify: `grep -ci 'timeout\|poll\|status\|retry\|backoff' deploy/SKILL.md | awk '{if($1>=2) print "OK"; else print "FAIL"}'`
-→ verify: `grep -q 'curl.*DEPLOY_URL\|smoke\|health' deploy/SKILL.md && echo OK`

package/.pi/prompts/develop-tdd.md

@@ -69,70 +69,15 @@ After all tests pass: extract duplication, deepen modules, apply SOLID principle
 
 After every behavior cycle, run the verify command from the active epic task. Show evidence before declaring the step done.
 
-### 6a. CI dry-run sub-step (when modifying workflows)
-
-If this cycle modified files in `.github/workflows/`, run a CI dry-run before pushing:
-
-```bash
-# 1. Check for workflow file changes
-CHANGED_WORKFLOWS=$(git diff --name-only HEAD | grep '\.github/workflows/' || true)
-if [ -n "$CHANGED_WORKFLOWS" ]; then
-  echo "==> CI dry-run: workflow files changed"
-  echo "    $CHANGED_WORKFLOWS"
-
-  # 2. Validate YAML syntax
-  if command -v yamllint &>/dev/null; then
-    for f in $CHANGED_WORKFLOWS; do
-      yamllint "$f" && echo "  OK: $f passes YAML lint" || echo "  WARN: $f has YAML issues"
-    done
-  else
-    # Fallback: Python YAML parse
-    for f in $CHANGED_WORKFLOWS; do
-      python3 -c "import yaml; yaml.safe_load(open('$f'))" 2>/dev/null && \
-        echo "  OK: $f YAML syntax valid" || \
-        echo "  FAIL: $f has YAML syntax errors"
-    done
-  fi
-
-  # 3. Run actionlint if available
-  if command -v actionlint &>/dev/null; then
-    for f in $CHANGED_WORKFLOWS; do
-      actionlint "$f" && echo "  OK: $f passes actionlint" || echo "  WARN: $f has actionlint issues"
-    done
-  fi
-
-  # 4. Check common pitfalls
-  for f in $CHANGED_WORKFLOWS; do
-    # Missing permissions block
-    if ! grep -q 'permissions:' "$f"; then
-      echo "  WARNING: $f missing permissions block — add one for security"
-    fi
-    # npm publish without NPM_TOKEN
-    if grep -q 'npm publish\|npx semantic-release' "$f" && ! grep -q 'NPM_TOKEN' "$f"; then
-      echo "  WARNING: $f has npm publish/semantic-release but no NPM_TOKEN in secrets"
-    fi
-    # Hardcoded Node versions
-    if grep -q 'node-version: [0-9]' "$f"; then
-      echo "  NOTE: $f has hardcoded Node version — consider node-version-file: .nvmrc"
-    fi
-  done
-
-  # 5. Suggest local dry-run
-  if command -v act &>/dev/null; then
-    echo "  SUGGESTION: Run 'act push --dry-run' to test workflows locally"
-  fi
-fi
-```
-
-Checklist:
-- [ ] YAML syntax validated for all changed workflow files
-- [ ] No missing permissions, secrets, or hardcoded versions flagged
-- [ ] Local dry-run suggested if `act` is available
-
 ### 7. Manual Verification Handover
 
 Once all tests pass: locate the Verification Script in the active epic capsule, present it to the user step-by-step, and wait for confirmation of behavioral correctness.
 
+
+### 6a. CI dry-run sub-step
+
+If this cycle modified files in `.github/workflows/`, run the CI dry-run procedure documented in [REFERENCE.md](REFERENCE.md#ci-dry-run).
+
 ## Checklist Per Cycle
 
 ```
@@ -148,26 +93,6 @@ Once all tests pass: locate the Verification Script in the active epic capsule,
 [ ] verify: command passes
 ```
 
-## --config mode
-
-For pure-config tasks (update package.json, edit YAML, tweak manifest) where there is no test infrastructure to write against. The RED state is "verify command fails"; GREEN is "verify command passes."
-
-**When to use:** task has a runnable `verify:` command and the deliverable is a config file change with no new behavior to unit-test. Invoke as `develop-tdd --config`.
-
-**Cycle:**
-
-```
-RED:    Run verify command → it fails (expected)
-GREEN:  Apply config change → verify passes
-COMMIT: commit: chore(<scope>): <change>
-```
-
-**Rules:**
-- Skips test-writing phase entirely — do NOT write a test file for config tasks.
-- `verify:` command is **required** and must be runnable (no placeholder).
-- Commit message follows Conventional Commits (`chore:` or `feat:` as appropriate).
-- Still runs full `verify-work` after all tasks complete.
-
 ## Handoff
 
 Gate: READY -> next: verify-work