mandate HTML img with align="middle" and flat chains for Workflow column
Updates the /workflows:development-workflows command to require HTML <img align="middle"> badges (so arrows align with badge centers) and to forbid parenthetical sub-loops or English qualifiers in the Workflow chain. Inner loop steps must be listed as flat siblings. Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
Shayan Rais
@@ -36,12 +36,20 @@ The README table has these columns:
|
||||
|
||||
- **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
|
||||
- **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**: The canonical end-to-end pipeline as a flat left-to-right 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`). **Flat only** — no parentheticals, no English qualifiers ("loop", "per story", "parallel waves"), no `+` connectors. If a step has internal sub-steps that matter, list them as siblings in the main chain instead of nesting them. Trace the README's "how to use" / "workflow" section for the canonical happy path: idea → spec/plan → tasks → implement → review → ship.
|
||||
- **Agent/Command/Skill counts**: Just the number (e.g., `25`, `0`, `108+`)
|
||||
|
||||
### Workflow badge encoding (shields.io)
|
||||
|
||||
Each step renders as ``. Encoding rules:
|
||||
Each step renders as an **HTML `<img>` tag with `align="middle"`** (not markdown image syntax) so the arrow stays vertically centered with the badges:
|
||||
|
||||
```html
|
||||
<img src="https://img.shields.io/badge/<ENCODED>-ddf4ff" alt="<plain-label>" align="middle">
|
||||
```
|
||||
|
||||
The `align="middle"` puts the badge's vertical center at the text baseline, so the ` → ` arrow ends up centered on each badge instead of sitting at badge-bottom. Without it the arrow visibly drops below the badges in GitHub's rendering.
|
||||
|
||||
Encoding rules for the `<ENCODED>` portion of the URL:
|
||||
|
||||
| Input character | Encoded as |
|
||||
|---|---|
|
||||
@@ -58,7 +66,9 @@ Examples:
|
||||
- `/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. ` ( →  loop) → `.
|
||||
Join steps with the literal arrow ` → ` (space-arrow-space) **between** the closing `>` of one img tag and the opening `<` of the next.
|
||||
|
||||
**Do not** wrap sub-steps in parentheses or annotate them with English ("loop", "per story", "+", "parallel waves"). If a step has an internal loop, just list the inner step names as siblings in the flat chain.
|
||||
|
||||
**Sort order**: Sorted by stars descending (highest first).
|
||||
|
||||
@@ -92,7 +102,7 @@ Read these files:
|
||||
> 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. **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.
|
||||
> 5. **Workflow** — the canonical end-to-end pipeline as a flat left-to-right 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. **Flat only** — no parentheses, no English qualifiers ("loop", "per story", "parallel waves"), no `+` connectors. If a step has internal sub-steps, list them as siblings in the main chain. Output as plain text — the orchestrator will encode each step into a shields.io HTML img badge.
|
||||
> 6. **Notable changes** — any significant recent changes? New agents/skills/commands, major versions?
|
||||
>
|
||||
> Return structured report per repo:
|
||||
@@ -124,7 +134,7 @@ Read these files:
|
||||
> 2. **Agent count** — count `.md` files in `agents/` or `.claude/agents/`. For BMAD, count agent-persona skills in `src/bmm-skills/`. For compound-engineering-plugin, count `.md` files across all subdirectories of `plugins/compound-engineering/agents/`. For oh-my-claudecode, count `.md` files in `agents/` at repo root.
|
||||
> 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. **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.
|
||||
> 5. **Workflow** — the canonical end-to-end pipeline as a flat left-to-right 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. **Flat only** — no parentheses, no English qualifiers ("loop", "per story", "parallel waves"), no `+` connectors. If a step has internal sub-steps, list them as siblings in the main chain. Output as plain text — the orchestrator will encode each step into a shields.io HTML img badge.
|
||||
> 6. **Notable changes** — any significant recent changes? New agents/skills/commands, major versions?
|
||||
>
|
||||
> Return structured report per repo:
|
||||
@@ -219,8 +229,8 @@ 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
|
||||
6. **Workflow badges use shields.io** — `` 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.
|
||||
6. **Workflow badges use HTML img with align="middle"** — `<img src="https://img.shields.io/badge/<ENCODED>-ddf4ff" alt="<plain-label>" align="middle">`. The `align="middle"` is required so the ` → ` arrow stays vertically centered with the badges. Encoding: `_` 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. **Agents, commands, skills are different** — count from their respective directories, don't conflate
|
||||
8. **Round stars consistently** — `k` suffix (98k, 10k, 4.1k). Under 1000 show exact
|
||||
9. **Compare with previous changelog** — mark items NEW, RECURRING, or RESOLVED
|
||||
10. **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)`).
|
||||
10. **Workflow column is mandatory and flat** — every row must have a Workflow cell. Trace the README's "how to use" / canonical happy path; do not synthesize a fictional pipeline. **No parentheses, no English qualifiers, no `+` connectors** — if a step has internal sub-steps, list them as siblings in the flat chain.
|
||||
|
||||
Reference in New Issue
Block a user