@drunkcoding/agents-and-skills 0.0.13 → 0.0.15

package/plugins/team-superpower/scripts/parse-claudemd.sh

@@ -0,0 +1,194 @@
+#!/usr/bin/env bash
+# parse-claudemd.sh — extract the team-superpower YAML block from CLAUDE.md.
+#
+# Usage:
+#   parse-claudemd.sh extract [<path-to-CLAUDE.md>]   prints the YAML block to stdout
+#   parse-claudemd.sh shape   [<path-to-CLAUDE.md>]   prints "full-stack" | "be-only" | "fe-only" | "none"
+#   parse-claudemd.sh get <dotted.key> [<path>]       prints a single scalar value
+#                                                      (limited: top-level group + leaf, e.g. backend.test_command)
+#
+# Exit codes:
+#   0  success
+#   1  CLAUDE.md missing or contains no `team-superpower` fenced block
+#   2  bad arguments
+#   3  key not found (only for `get`)
+#
+# Notes:
+#   - The fenced block is recognised by the literal opener "```team-superpower"
+#     (with no language indent) and the matching "```" closer.
+#   - Comments starting with `#` (after optional whitespace) are stripped before
+#     value extraction. Inline `# comment` tails are also stripped.
+#   - This is a deliberately tiny parser. It does NOT validate the schema.
+#     Schema validation is the lead's job (it halts on bad values per the spec).
+
+set -euo pipefail
+
+usage() {
+  sed -n '2,30p' "$0" | sed 's/^# \{0,1\}//'
+}
+
+CLAUDE_FILE_DEFAULT="${CLAUDE_PROJECT_DIR:-$PWD}/CLAUDE.md"
+
+extract_block() {
+  local file="$1"
+  [ -f "$file" ] || return 1
+  # awk: print lines strictly between the opener and closer fences.
+  awk '
+    /^```team-superpower[[:space:]]*$/ { in_block = 1; next }
+    in_block && /^```[[:space:]]*$/    { in_block = 0; exit }
+    in_block                            { print }
+  ' "$file"
+}
+
+block_has_content() {
+  # Returns 0 if the YAML block extracted to stdin has at least one non-comment,
+  # non-blank line; 1 otherwise.
+  local payload
+  payload="$(cat || true)"
+  printf '%s' "$payload" | grep -vE '^[[:space:]]*(#|$)' | head -n1 | grep -q .
+}
+
+# Strip an inline `# comment` tail (but not `#` inside a quoted string — we
+# tolerate the simple case here, the spec doesn't ship complex YAML values).
+strip_comment() {
+  sed -E 's/[[:space:]]+#[^"\x27]*$//' | sed -E 's/^[[:space:]]*#.*$//'
+}
+
+cmd_extract() {
+  local file="${1:-$CLAUDE_FILE_DEFAULT}"
+  if [ ! -f "$file" ]; then
+    echo "parse-claudemd: $file does not exist" >&2
+    return 1
+  fi
+  local block
+  block="$(extract_block "$file")"
+  if [ -z "$block" ] || ! printf '%s' "$block" | block_has_content; then
+    echo "parse-claudemd: no \`team-superpower\` block found in $file" >&2
+    return 1
+  fi
+  printf '%s\n' "$block"
+}
+
+# Read a top-level scalar like `backend: none` or detect whether a group is
+# explicitly "none".
+group_is_none() {
+  # group_is_none <yaml-block-on-stdin> <group-name>
+  local group="$2"
+  awk -v g="$group" '
+    BEGIN { found = 0 }
+    {
+      sub(/[[:space:]]+#[^"\x27]*$/, "")
+      sub(/^[[:space:]]*#.*$/, "")
+    }
+    $0 ~ "^"g":[[:space:]]+none[[:space:]]*$" { found = 1; exit }
+    END { exit found ? 0 : 1 }
+  ' <<<"$1"
+}
+
+# A group is "present" if there is `group:` followed (on subsequent indented
+# lines) by at least one non-comment, non-blank key/value pair.
+group_is_present() {
+  # group_is_present <yaml-block> <group-name>
+  local group="$2"
+  awk -v g="$group" '
+    BEGIN { state = 0; has_keys = 0 }
+    {
+      line = $0
+      # strip comments
+      sub(/[[:space:]]+#[^"\x27]*$/, "", line)
+      sub(/^[[:space:]]*#.*$/, "", line)
+    }
+    line ~ "^"g":[[:space:]]*$"          { state = 1; next }
+    line ~ "^"g":[[:space:]]+none"       { state = 0; exit }
+    state == 1 && line ~ /^[^[:space:]]/ { state = 0 }
+    state == 1 && line ~ /^[[:space:]]+[A-Za-z_][A-Za-z0-9_]*:/ { has_keys = 1 }
+    END { exit has_keys ? 0 : 1 }
+  ' <<<"$1"
+}
+
+cmd_shape() {
+  local file="${1:-$CLAUDE_FILE_DEFAULT}"
+  local block
+  block="$(cmd_extract "$file")" || return 1
+
+  local be_present=1 fe_present=1
+  group_is_present "$block" backend  || be_present=0
+  group_is_present "$block" frontend || fe_present=0
+
+  if   [ "$be_present" -eq 1 ] && [ "$fe_present" -eq 1 ]; then echo "full-stack"
+  elif [ "$be_present" -eq 1 ];                              then echo "be-only"
+  elif [ "$fe_present" -eq 1 ];                              then echo "fe-only"
+  else                                                            echo "none"
+  fi
+}
+
+cmd_get() {
+  local key="${1:-}"
+  local file="${2:-$CLAUDE_FILE_DEFAULT}"
+  if [ -z "$key" ]; then usage >&2; return 2; fi
+  local block
+  block="$(cmd_extract "$file")" || return 1
+
+  case "$key" in
+    *.*)
+      local group leaf
+      group="${key%%.*}"
+      leaf="${key#*.}"
+      local value
+      value="$(awk -v g="$group" -v k="$leaf" '
+        BEGIN { in_group = 0; pat = "^[[:space:]]+" k "[[:space:]]*:[[:space:]]*" }
+        {
+          line = $0
+          sub(/[[:space:]]+#[^"\x27]*$/, "", line)
+          sub(/^[[:space:]]*#.*$/, "", line)
+        }
+        line ~ "^"g":[[:space:]]*$"           { in_group = 1; next }
+        in_group && line ~ /^[^[:space:]]/    { in_group = 0 }
+        in_group && line ~ pat {
+          v = line
+          sub(pat, "", v)
+          sub(/[[:space:]]+$/, "", v)
+          gsub(/^"|"$/, "", v)
+          gsub(/^\x27|\x27$/, "", v)
+          print v
+          exit
+        }
+      ' <<<"$block")"
+      if [ -z "$value" ]; then return 3; fi
+      printf '%s\n' "$value"
+      ;;
+    *)
+      # Top-level scalar (e.g. "backend" for `backend: none`)
+      local value
+      value="$(awk -v k="$key" '
+        BEGIN { pat = "^" k ":[[:space:]]+" }
+        {
+          line = $0
+          sub(/[[:space:]]+#[^"\x27]*$/, "", line)
+          sub(/^[[:space:]]*#.*$/, "", line)
+        }
+        line ~ pat {
+          v = line; sub(pat, "", v); sub(/[[:space:]]+$/, "", v)
+          print v
+          exit
+        }
+      ' <<<"$block")"
+      if [ -z "$value" ]; then return 3; fi
+      printf '%s\n' "$value"
+      ;;
+  esac
+}
+
+main() {
+  local sub="${1:-}"
+  shift || true
+  case "$sub" in
+    extract) cmd_extract "$@" ;;
+    shape)   cmd_shape   "$@" ;;
+    get)     cmd_get     "$@" ;;
+    -h|--help|"") usage; [ -z "$sub" ] && return 2 || return 0 ;;
+    *) echo "unknown subcommand: $sub" >&2; usage >&2; return 2 ;;
+  esac
+}
+
+main "$@"

package/plugins/tech-graph/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "tech-graph",
-  "version": "0.0.13",
+  "version": "0.0.15",
   "description": "Step-by-step wizard for generating technical diagrams as SVG+PNG.",
   "author": {
     "name": "steven"

package/plugins/tech-graph/agents/tech-graph.md

@@ -9,6 +9,14 @@ model: sonnet
 
 You are a diagram wizard. Walk the user through 6 steps **one at a time**, then render an SVG (and optionally PNG) by delegating to the upstream `fireworks-tech-graph` skill at `plugins/tech-graph/skills/tech-graph/`.
 
+## Workflow
+
+Six-step wizard (purpose → type → style → format → density → confirm), then the render protocol below. Each step asks one multiple-choice question; wizard state is held as JSON in working memory until step 6.
+
+## Output
+
+An SVG (and optionally PNG) written to `<outdir>/<topic-slug>-<type>-<style>.svg`. The absolute path of every file written is reported to the user with a `snip open <path>` suggestion for visual review.
+
 ## Hard Rules
 
 1. **One question per message.** Always multiple-choice. Mark the default with `★`.

package/plugins/team-superpower/agents/implementer.md

@@ -1,46 +0,0 @@
----
-name: implementer
-description: Executes one `impl:` task at a time via Superpowers `subagent-driven-development` with `test-driven-development` (RED-GREEN-REFACTOR). Owns phase 4 of the team-superpower workflow. Cannot modify the plan or touch files outside its assigned task.
-tools: Read, Write, Edit, Bash, Glob, Grep
-model: sonnet
----
-
-# Implementer — Phase 4 (Implementation)
-
-You are an **implementer** teammate. There may be one or more of you running in parallel. Your only job: self-claim `impl:`-prefixed tasks from the shared task list and complete each one through the canonical Superpowers chain.
-
-## Hard rules
-
-1. For every task, run the unmodified Superpowers `subagent-driven-development` skill at `~/.claude/plugins/superpowers/skills/subagent-driven-development/SKILL.md`. It dispatches a fresh subagent for the task and applies the two-stage review (spec compliance, then code quality). Read the SKILL.md before claiming your first task.
-2. Inside that flow, every code change MUST go through the canonical `test-driven-development` skill: RED (failing test first) → GREEN (minimal code to pass) → REFACTOR. **If you ever realise you wrote production code before a failing test existed, delete that code and start the task over.** This is non-negotiable per the TDD skill.
-3. You **may not modify the plan**. If the plan is wrong, halt and escalate to the lead via the §7 template (`docs/superpowers/ESCALATION.md`). The lead will route it to the planner; a plan change requires owner approval.
-4. You **may not edit files assigned to another active implementer task**. Before opening any file, read the shared task list and confirm no `in-progress` task on a peer claims that path. If overlap is unavoidable, post a coordination message to the lead and wait.
-5. Mark a task complete **only** after the two-stage review inside `subagent-driven-development` passes. The `TaskCompleted` hook will reject your completion if `metadata.plan_approved_at` is missing — make sure it's stamped from the lead's plan-approval handoff.
-6. One task at a time. Do not batch.
-
-## Task claiming protocol
-
-1. Read the shared task list. Pick the lowest-numbered `impl:` task whose dependencies are all complete and whose file scope does not overlap an in-progress peer task.
-2. Mark it in-progress with your teammate id.
-3. Run subagent-driven-development.
-4. On completion (two-stage review passed): mark the task complete with the required metadata.
-
-## When the plan is wrong
-
-Escalate. Do NOT silently work around it. Example escalation:
-
-```
-BLOCKED: Task impl:add-user-endpoint specifies POST /users but design doc says PUT /users/{id}. Which is correct?
-Phase: implementation
-Context: Plan task 4 reads "POST /users → 201". Design doc §3 reads "PUT /users/{id} idempotent". I can write either but they are not equivalent and the test I'd write differs.
-Options:
-  A. Follow the plan (POST) and let reviewer flag if wrong.
-  B. Halt; planner amends; owner re-approves the plan delta.
-  C. Owner clarifies design intent directly.
-Recommendation: B — the plan is the source of truth for code, and a plan that contradicts the approved design must be reconciled before more tasks are claimed.
-Need from you: choose A/B/C.
-```
-
-## When you idle
-
-After a task completes, claim the next eligible one. If none are available and you have no unanswered inbound mail, idle. The `TeammateIdle` hook will block idle if peer mail is unanswered.