Skip to content
Back to search

claude-skills

SkillWorks with Claude CodeGitHub

Skills for Claude Code.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/johan-lindahl--claude-skills/badge.svg)](/listings/johan-lindahl--claude-skills)

HTML

<a href="/listings/johan-lindahl--claude-skills"><img src="/api/listings/johan-lindahl--claude-skills/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Copy the skill into your personal skills folder:

git clone https://github.com/johan-lindahl/claude-skills
cp -R claude-skills/skills/build-order ~/.claude/skills/

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 84 lines
  1. # claude-skills
  2. Skills for [Claude Code](https://claude.com/claude-code).
  3. ## build-order
  4. Turns an epic, milestone or sprint in **Azure DevOps, Jira or GitHub** into a live build-order page:
  5. which items can run in parallel, what waits for what, and the chain of work that sets the end date.
  6. The page reads status from your tracker while it's open, so it stays current as work moves.
  7. <picture>
  8. <source media="(prefers-color-scheme: dark)" srcset="docs/build-order-dark.png">
  9. <img alt="Build-order page: a done column, five waves of work cards with dependencies and status, a side lane for a separate team, the critical path and tips for working in parallel" src="docs/build-order-light.png">
  10. </picture>
  11. <sub>Screenshot with example data.</sub>
  12. ### What the page shows
  13. - **Waves.** Each column is a wave. Items in one column don't depend on each other, so you can hand
  14. them to different people or agents at the same time.
  15. - **Status per item**, read live from the tracker: Done, In progress or review, **Ready** (everything
  16. it needs is done), Waiting, On hold.
  17. - **Dependencies** on every card. A need that's already done is struck through, a dashed one is
  18. helpful but not required, and a blocker outside the tracker shows as plain text.
  19. - **Side lanes** for separate tracks: another team, an external blocker, a different stream.
  20. - **The critical path**: the longest open chain, weighted by points.
  21. - **Tips for working in parallel** that you write for the project, such as which items will conflict.
  22. - **New items.** Tickets added to the scope after the page was made show up by themselves, in a
  23. "New since the plan" panel.
  24. ### Find and plan new items
  25. The button in the status bar places new tickets for you. It reads each new ticket's dependency links.
  26. Claude reads its description for "depends on" and "blocks" wording. The page then proposes a wave, with
  27. the source of each dependency. Nothing changes until you press **Apply**.
  28. ![Proposed placement: SHOP-130 goes to Wave 3, needs SHOP-108 (from the description) and blocks SHOP-111 (from a tracker link)](docs/build-order-plan-new-items.png)
  29. ### How you use it
  30. Ask Claude Code in a project that uses one of the trackers, for example:
  31. > In what order should we build the stories under epic 1234? Which ones can run in parallel?
  32. > Make a build-order page for the "Checkout v2" milestone.
  33. Claude then:
  34. 1. **Finds the tracker and the scope** from the repo and the tools you have connected.
  35. 2. **Builds the dependency graph.** Tracker links come first, then "Depends on" / "Blocked by" text.
  36. 3. **Shows you the plan in chat to confirm.** A wrong dependency makes the page confidently wrong.
  37. 4. **Publishes the page** as a private artifact and keeps its working files in
  38. `~/.claude/build-order/<project>/`, so a later session updates the same page.
  39. ### Install
  40. Copy the skill into your personal skills folder:
  41. ```sh
  42. git clone https://github.com/johan-lindahl/claude-skills
  43. cp -R claude-skills/skills/build-order ~/.claude/skills/
  44. ```
  45. ### Requirements
  46. - **Claude Code**, with permission to publish artifacts.
  47. - **For the first plan**, read access to the tracker: the `az`, `jira` or `gh` CLI, or an MCP server
  48. for it.
  49. - **For live status and planning on the page**, a connection the page can call:
  50. - a claude.ai connector for the tracker, which works in any browser; or
  51. - a local MCP server added to the Claude desktop app, which works only in the desktop app.
  52. Without a connection the page still works, as a snapshot from when it was published.
  53. ### Files
  54. | Path | What it does |
  55. |---|---|
  56. | `skills/build-order/SKILL.md` | The workflow Claude follows |
  57. | `skills/build-order/scripts/plan.py` | Waves, lanes and critical path from an items file. Stops on a dependency cycle |
  58. | `skills/build-order/scripts/render.py` | Fills the page template with the plan and settings |
  59. | `skills/build-order/assets/template.html` | The page, including live status and planning |
  60. | `skills/build-order/references/` | How to read items, links and states from ADO, Jira and GitHub |

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.