From 2f21c03d87d39018eb93aeee844b326f4c71a813 Mon Sep 17 00:00:00 2001 From: Shayan Rais Date: Wed, 29 Apr 2026 00:13:38 +0500 Subject: [PATCH] update /workflows:development-workflows to populate new Workflow column and research 11 repos MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Bumps repo count from 10 to 11 (adds mattpocock/skills to Agent 1's batch), replaces "Uniqueness tags" research item with "Workflow" canonical pipeline, and documents the shields.io badge encoding rules (/ → %2F, - → --, _ → __, dots/colons verbatim) so the orchestrator encodes plain-text agent output into ddf4ff badges consistently. Adds mandatory Rule 11 forbidding synthesized pipelines — agents must trace each repo's documented happy path. Co-Authored-By: Claude --- .../workflows/development-workflows.md | 73 +++++++++++++------ 1 file changed, 49 insertions(+), 24 deletions(-) diff --git a/.claude/commands/workflows/development-workflows.md b/.claude/commands/workflows/development-workflows.md index fee0558..83d64a8 100644 --- a/.claude/commands/workflows/development-workflows.md +++ b/.claude/commands/workflows/development-workflows.md @@ -1,14 +1,14 @@ --- -description: Update the DEVELOPMENT WORKFLOWS table by researching all 10 workflow repos in parallel +description: Update the DEVELOPMENT WORKFLOWS table by researching all 11 workflow repos in parallel --- # Workflow — Development Workflows -Update the DEVELOPMENT WORKFLOWS table in `README.md` by researching 10 repos in parallel. Launch agents, merge results, present changes, update table if approved. +Update the DEVELOPMENT WORKFLOWS table in `README.md` by researching 11 repos in parallel. Launch agents, merge results, present changes, update table if approved. --- -## The 10 Repos +## The 11 Repos | # | Repo | Owner | |---|------|-------| @@ -22,6 +22,7 @@ Update the DEVELOPMENT WORKFLOWS table in `README.md` by researching 10 repos in | 8 | `bmad-code-org/BMAD-METHOD` | BMAD Code Org | | 9 | `EveryInc/compound-engineering-plugin` | Every.to | | 10 | `Yeachan-Heo/oh-my-claudecode` | Yeachan Heo (@bellman_ych) | +| 11 | `mattpocock/skills` | Matt Pocock | --- @@ -30,14 +31,35 @@ Update the DEVELOPMENT WORKFLOWS table in `README.md` by researching 10 repos in The README table has these columns: ```markdown -| Name | ★ | Uniqueness | Plan | | | | +| Name | ★ | Plan | | | | Workflow | ``` - **Name**: `[Short Name](github-url)` — use project name, not owner/repo - **★**: Star count rounded to `k` (e.g., 98k, 10k, 4.1k). Under 1000 show exact number -- **Uniqueness**: 2-3 shields.io badge tags using `![tag](https://img.shields.io/badge/TAG-ddf4ff)`. Underscores for spaces, `--` for hyphens, `%2B` for `+`, `%2F` for `/` - **Plan**: Icon + linked name of the Plan implementation. Icon is `` for command, `` for agent, `` for skill. Name links to the actual file in the repo - **Agent/Command/Skill counts**: Just the number (e.g., `25`, `0`, `108+`) +- **Workflow**: The canonical end-to-end pipeline as a sequence of shields.io badges joined by ` → `. Each step is the actual command/skill/agent name from the repo (e.g. `/speckit.plan`, `bmad-create-prd`, `subagent-driven-development`). Use parenthetical sub-steps only when a stage has a critical inner loop (e.g. `(/tdd + feedback loops)`). Trace the README's "how to use" / "workflow" section for the canonical happy path: idea → spec/plan → tasks → implement → review → ship. + +### Workflow badge encoding (shields.io) + +Each step renders as `![label](https://img.shields.io/badge/-ddf4ff)`. Encoding rules: + +| Input character | Encoded as | +|---|---| +| `/` (leading slash) | `%2F` | +| `-` (literal dash) | `--` | +| `_` (literal underscore) | `__` | +| ` ` (space) | `_` | +| `+` | `%2B` | +| `.` and `:` | unchanged | + +Examples: +- `/grill-me` → `%2Fgrill--me` +- `/speckit.plan` → `%2Fspeckit.plan` +- `/opsx:propose` → `%2Fopsx:propose` +- `bmad-create-epics-and-stories` → `bmad--create--epics--and--stories` + +Join steps with the literal arrow character ` → ` (space-arrow-space) outside the badge markdown. For sub-loops, wrap in parentheses inside the cell, e.g. `![/team](...) (![team-plan](...) → ![team-fix](...) loop) → ![/ralph](...)`. **Sort order**: Sorted by stars descending (highest first). Do NOT group by Plan type. @@ -56,22 +78,23 @@ Read these files: **Immediately** spawn both agents in a **single message** (parallel). Each uses `subagent_type: "development-workflows-research-agent"`. -### Agent 1 (3 repos) +### Agent 1 (4 repos) -> Research these 3 Claude Code workflow repositories: +> Research these 4 Claude Code workflow repositories: > > **Repo 1: github/spec-kit** (https://github.com/github/spec-kit) > **Repo 2: affaan-m/everything-claude-code** (https://github.com/affaan-m/everything-claude-code) > **Repo 3: obra/superpowers** (https://github.com/obra/superpowers) +> **Repo 4: mattpocock/skills** (https://github.com/mattpocock/skills) > > For EACH repo, return: > > 1. **Stars** — use GitHub API `https://api.github.com/repos/{owner}/{repo}`, read `stargazers_count`. Round to `k`. -> 2. **Agent count** — count `.md` files in `agents/` or `.claude/agents/`. For obra, also count implicit sub-agents dispatched by skills. -> 3. **Skill count** — count folders in `skills/` or `.claude/skills/`. -> 4. **Command count** — count `.md` files in `commands/` or `.claude/commands/`. For spec-kit, count files in `templates/commands/`. -> 5. **Plan implementation** — find the Plan/planning agent, skill, or command. Return its name, type (agent/skill/command), and file path. -> 6. **Uniqueness tags** — 2-3 short tags (2-3 words each) capturing what makes this workflow unique. +> 2. **Agent count** — count `.md` files in `agents/` or `.claude/agents/`. For obra, also count implicit sub-agents dispatched by skills. For mattpocock, count is 0 (skills-only repo). +> 3. **Skill count** — count folders in `skills/` or `.claude/skills/`. For mattpocock, count folders in `skills/` at repo root. +> 4. **Command count** — count `.md` files in `commands/` or `.claude/commands/`. For spec-kit, count files in `templates/commands/`. For mattpocock, count is 0 (skills serve as slash commands). +> 5. **Plan implementation** — find the Plan/planning agent, skill, or command. Return its name, type (agent/skill/command), and file path. For mattpocock, the Plan-artifact-producing skill is `to-prd` (the alignment skill `grill-me` is the upstream entry point but not the Plan column). +> 6. **Workflow** — the canonical end-to-end pipeline as a sequence of step names joined by ` → `. Trace the README's "how to use" / "workflow" section for the happy path: idea → spec/plan → tasks → implement → review → ship. Use the actual command/skill/agent names from the repo. Wrap critical inner loops in parentheses, e.g. `subagent-driven-development (test-driven-development + requesting-code-review)`. Output as plain text — the orchestrator will encode each step into a shields.io badge. > 7. **Notable changes** — any significant recent changes? New agents/skills/commands, major versions? > > Return structured report per repo: @@ -82,7 +105,7 @@ Read these files: > COMMANDS: > SKILLS: > PLAN: () — -> TAGS: , , +> WORKFLOW: → → ... → > CHANGES: > ``` @@ -105,7 +128,7 @@ Read these files: > 3. **Skill count** — count folders in `skills/` or `.claude/skills/`. For gstack, skills are root-level directories with SKILL.md. For BMAD, count all skills in `src/bmm-skills/` and `src/core-skills/`. For compound-engineering-plugin, count folders in `plugins/compound-engineering/skills/` plus `plugins/coding-tutor/skills/`. For oh-my-claudecode, count folders in `skills/` at repo root. > 4. **Command count** — count `.md` files in `commands/` or `.claude/commands/`. For GSD, count in `commands/gsd/`. For OpenSpec, count `/opsx:*` commands. For BMAD, count is 0 (commands generated at install time). For compound-engineering-plugin, count `.md` files in `.claude/commands/` plus `plugins/coding-tutor/commands/`. For oh-my-claudecode, count is 0 (skills serve as slash commands). > 5. **Plan implementation** — find the Plan/planning agent, skill, or command. Return its name, type (agent/skill/command), and file path. -> 6. **Uniqueness tags** — 2-3 short tags (2-3 words each) capturing what makes this workflow unique. +> 6. **Workflow** — the canonical end-to-end pipeline as a sequence of step names joined by ` → `. Trace the README's "how to use" / "workflow" section for the happy path: idea → spec/plan → tasks → implement → review → ship. Use the actual command/skill/agent names from the repo. Wrap critical inner loops in parentheses, e.g. `/team (team-plan → team-fix loop) → /ralph`. Output as plain text — the orchestrator will encode each step into a shields.io badge. > 7. **Notable changes** — any significant recent changes? New agents/skills/commands, major versions? > > Return structured report per repo: @@ -116,7 +139,7 @@ Read these files: > COMMANDS: > SKILLS: > PLAN: () — -> TAGS: , , +> WORKFLOW: → → ... → > CHANGES: > ``` @@ -132,7 +155,7 @@ Development Workflows — Update Report Changes Found: : ★ k → k | agents → | commands → | skills → - : tags updated: → + : workflow updated: → : Plan link changed: → ... @@ -141,12 +164,12 @@ No Changes: ... Action Items: -# | Type | Action | Status -1 | Star | Update ★ from Xk to Yk | NEW/RECURRING -2 | Count | Update agents from X to Y | NEW/RECURRING -3 | Tags | Update tags | NEW/RECURRING -4 | Plan | Update Plan link | NEW/RECURRING -5 | Sort | Move (Plan type changed) | NEW/RECURRING +# | Type | Action | Status +1 | Star | Update ★ from Xk to Yk | NEW/RECURRING +2 | Count | Update agents from X to Y | NEW/RECURRING +3 | Workflow | Update workflow pipeline | NEW/RECURRING +4 | Plan | Update Plan link | NEW/RECURRING +5 | Sort | Move (Plan type changed) | NEW/RECURRING ``` Compare with previous changelog entries and mark items as `NEW`, `RECURRING`, or `RESOLVED`. @@ -189,9 +212,10 @@ Update the badge on line 4 of `README.md`. Get time via `TZ=Asia/Karachi date "+ Ask user: **(1) Execute all** | **(2) Execute specific** | **(3) Skip** When executing, edit the `## ⚙️ DEVELOPMENT WORKFLOWS` table in `README.md`: -- Update stars, tags, Plan links, counts per row +- Update stars, Plan links, counts, **and the Workflow column** per row - Maintain sort order: stars descending (highest first). Do NOT group by Plan type - Match existing format exactly (icons, badge URLs, link style) +- For the Workflow column, encode each plain-text step the agent returned into a `ddf4ff` shields.io badge per the encoding rules in the Table Format section, then join with ` → ` --- @@ -202,8 +226,9 @@ When executing, edit the `## ⚙️ DEVELOPMENT WORKFLOWS` table in `README.md`: 3. **Don't auto-execute** — present report first, wait for approval 4. **ALWAYS append changelog** and **ALWAYS update badge** — mandatory 5. **Sort by stars descending** — highest stars first, do NOT group by Plan type -6. **Tags use shields.io** — `![tag](https://img.shields.io/badge/TAG-ddf4ff)` with `_` for spaces, `--` for hyphens +6. **Workflow badges use shields.io** — `![step](https://img.shields.io/badge/-ddf4ff)` with `_` for spaces, `--` for hyphens, `__` for underscores, `%2F` for `/`, `%2B` for `+`. Dots and colons survive verbatim. Join steps with ` → `. Always update the Workflow column when any step name in the upstream repo changes. 7. **Plan links must point to actual files** — not repo root 8. **Agents, commands, skills are different** — count from their respective directories, don't conflate 9. **Round stars consistently** — `k` suffix (98k, 10k, 4.1k). Under 1000 show exact 10. **Compare with previous changelog** — mark items NEW, RECURRING, or RESOLVED +11. **Workflow column is mandatory** — every row must have a Workflow cell. Trace the README's "how to use" / canonical happy path; do not synthesize a fictional pipeline. Wrap critical inner loops in parentheses (e.g. `(/tdd + feedback loops)`).