Skip to content

joshua-noel/workflow-skills

v1.0.0MIT

Workflow skills for coding agents: clarify, plan, build, review, communicate, visualize, maintain.

coordinator

Running a long session that spawns many agents. Use when you coordinate more than a couple of subagents, work overnight or across restarts, share a machine with heavy jobs, must stop at a usage limit, or report status to the user.

demo-bar

Quality bar for UI demos, mocks and prototypes shown to the user. Use before sending or presenting any demo, mock, screenshot set, preview link or recorded walkthrough of an interface.

domain-modeling

Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.

eval-driven

Test-first method for anything where a model or prompt makes decisions. Use before changing a prompt, model, rule set, classifier, judge or agent behaviour, and when the user asks whether a change "made it better".

grilling

Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.

papercuts-maintenance

Review and fix captured Papercuts when the user requests maintenance, asks to clear recurring tooling friction, or the repository cadence reports a periodic review due. Prioritize blockers, major issues, and recurring defects; verify real fixes before resolving entries.

ponytail

Forces the laziest solution that actually works, simplest, shortest, most minimal. Channels a senior dev who has seen everything: question whether the task needs to exist at all (YAGNI), reach for the standard library before custom code, native platform features before dependencies, one line before fifty. Supports intensity levels: lite, full (default), ultra. Use on ANY coding task: writing, adding, refactoring, fixing, reviewing, or designing code, and choosing libraries or dependencies. Also use whenever the user says "ponytail", "be lazy", "lazy mode", "simplest solution", "minimal solution", "yagni", "do less", or "shortest path", or complains about over-engineering, bloat, boilerplate, or unnecessary dependencies. Do NOT use for non-coding requests (general knowledge, prose, translation, summaries, recipes).

prototype

Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.

research

Investigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo. Use when the user wants a topic researched, docs or API facts gathered, or reading legwork delegated to a background agent.

review-gates

Rules for reviewing and merging. Use when a change touches auth, personal data, deletion or migration, money, admin scripts or credentials; before merging any pull request; when starting a review loop; or before approving a spec, audit, design or multi-session plan.

ste-writing

Rewrite or write text at about 80% of ASD-STE100 Simplified Technical English. Use when the user asks for "STE", "ASD-STE100", "simplified technical English", "plain technical English", or asks to make an explanation, doc, README, runbook, or procedure clearer and easier to read. Also used by the visualize-diagram and visualize-webpage skills for their labels and prose.

to-spec

Turn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what you've already discussed.

to-tickets

Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker (edges as text in one file per ticket locally, or native blocking links on a real tracker).

user-run-scripts
visual-edit

Open and collaboratively edit a running local app in Design, with shared fallback previews and source handoff. Use when the user asks to inspect, share, or edit a real local app in Design.

visualize-diagram

Draw an interactive diagram of a codebase, function, project domain, architecture or whole project as one self-contained SVG file. Use when the user asks for a "diagram", to "draw", "visualize" or "map" something, or asks how parts of a system fit together, what calls what, or how data moves. Dark theme unless the user asks for light.

visualize-webpage

Explain a codebase, function, project domain, architecture or whole project as one self-contained interactive HTML page. Use when the user asks for output "in HTML", an "interactive page", a "webpage", an "explorable" explanation, or a walkthrough they can click through. Dark theme unless the user asks for light.

wayfinder

Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.