← all publishers

mblauberg

@mblauberg source repo

25 published skills

  1. Tdd · mblauberg bundle
    Use for writing the first right-reason failing test for new or changed observable behaviour, then red-green-refactor. Not for behaviour-preserving structure, diagnosis-only, or delivery; use refactor, diagnose, or implement.
    0
    installs
  2. Scope · mblauberg bundle
    Use when unsettled requirements or decisions need a spec, options, acceptance criteria, authority bounds, or decision record. Not for implementing approved scope or writing files during read-only advice; use implement.
    0
    installs
  3. Caveman · mblauberg bundle
    Use when the user invokes Caveman or requests aggressively compressed chat. Full and ultra remain user-explicit. Not for generic brevity, a governing terse default, or artifact condensation.
    0
    installs
  4. Deliver · mblauberg bundle
    Use for taking an approved research, analysis, document, or agent-product outcome through evidence, review, and user acceptance. For a software change, unsettled scope, or release, use implement, scope, or release.
    0
    installs
  5. Release · mblauberg bundle
    Use for user-authorised promotion of an accepted artifact: deploy, publish, send, roll out, or observe. Not for implementation or drafting; use implement or the domain owner.
    0
    installs
  6. Session · mblauberg bundle
    Use for start, checkpoint, handoff, compaction, or end-of-session continuity on substantial work. Not for a multi-session route map; use work-map for effort state.
    0
    installs
  7. Diagnose · mblauberg bundle
    Use to reproduce and find the root cause of broken behaviour, crashes, test failures, flakes, or performance regressions. Not for a known-cause repair or change review; use implement or code-review.
    0
    installs
  8. Evaluate · mblauberg bundle
    Use for repeatable quality or safety evaluation of stochastic or judgement-bearing systems, prompts, agents, rankings, or artifacts. Not for deterministic tests or ordinary code review; use tdd or code-review.
    0
    installs
  9. Grill Me · mblauberg bundle
    Use when the user asks to be grilled or wants one-question-at-a-time stress testing of a plan or design. Not for writing the final spec or implementing it; use scope or implement.
    0
    installs
  10. Refactor · mblauberg bundle
    Use for authorised, behaviour-preserving structural simplification backed by characterisation and equivalence evidence. Not for new behaviour, read-only review, or unknown root cause; use tdd, code-review, or diagnose.
    0
    installs
  11. Work Map · mblauberg bundle
    Use when a multi-session effort needs one durable, curated route linking its specification and work items. Not for live status, ownership, dependencies, user gates or session handoffs; use the project's work tracker and session.
    0
    installs
  12. Autopilot · mblauberg bundle
    Use for a large, open-ended mission that must survive sessions/crashes and run user-out-of-loop until STOP; delegates lifecycle work to other skills. Not for pre-scoped delivery that stops at a PR gate; use orchestrate's autonomous mode or deliver.
    0
    installs
  13. Implement · mblauberg bundle
    Use for an approved software change through verified implementation, independent review, bounded repair, and user acceptance. Not for unsettled scope, diagnosis-only, read-only review, or release.
    0
    installs
  14. Prototype · mblauberg bundle
    Use for an authorised, timeboxed throwaway build that answers one feasibility question. Not for production code, settled requirements, or debugging known breakage; use implement, scope, or diagnose.
    0
    installs
  15. Retrospect · mblauberg bundle
    Use after delivery, release, incident, evaluation, or a long run to derive evidence-backed process improvements and regression gates. Not for session cleanup, one skill audit, or an active defect; use session, skill-craft, or implement.
    0
    installs
  16. Setup Repo · mblauberg bundle
    Use when asked to set up or scaffold a repository's process, labels, tracker, branch ruleset, issue forms, docs layout, work-item runbook, or board. Not for this repo's own day-to-day GitHub mechanics; use its runbook.
    0
    installs
  17. Code Review · mblauberg bundle
    Use for source-read-only review of a PR, diff, commit, migration, refactor, or implementation through its dependency cone. Not for root-cause diagnosis, authorised fixes, or browser/UX review; use diagnose, implement, or ui-ux-design.
    0
    installs
  18. D2 Diagrams · mblauberg bundle
    Use for creating, validating, rendering, or exporting D2 source, including fixed-layout and vector-PDF publication figures. Not for Mermaid, Graphviz, or PlantUML requirements diagrams; use engineering-docs or uml-diagrams.
    0
    installs
  19. Orchestrate · mblauberg bundle
    Use when bounded fan-out, multi-agent research, cross-family review, parallel audits, Herdr control, or autonomous ready-issue implementation helps. Not for tiny work, coupled debugging, or run-until-STOP jobs; use diagnose or autopilot.
    0
    installs
  20. Skill Craft · mblauberg bundle
    Use to create, revise, or audit Agent Skills: SKILL.md, triggers, progressive disclosure, fixtures, overlap, token cost. Defaults to read-only audit; edits need authority. Not for plugin packaging (use plugin-creator) or delivery (use implement).
    0
    installs
  21. UI UX Design · mblauberg bundle
    Use for UI/UX: read-only review by default (visual, accessibility, responsive, interaction), or design, redesign, design systems, and live iteration. Pair changes with implement. Source-diff review: code-review.
    0
    installs
  22. Legal Writing · mblauberg bundle
    Use for drafting, reviewing, condensing, or source-checking Australian legal documents (forms, affidavits, submissions and orders), legal decision overviews, or correspondence. Not for academic, engineering, or general prose; use its specialist.
    0
    installs
  23. Natural Writing · mblauberg bundle
    Use for making general, mixed, academic, or correspondence prose natural and direct while preserving facts, citations, numbers, and intent. Covers thesis and paper prose. Not for engineering or Australian legal prose; use its specialist.
    0
    installs
  24. Engineering Docs · mblauberg bundle
    Use for creating, placing, indexing, updating, or archiving engineering docs and docs structures. Not for prose-only rewriting or session continuity; use engineering-writing or session.
    0
    installs
  25. Engineering Writing · mblauberg bundle
    Use for drafting or condensing software-engineering artefacts such as requirements/specs, READMEs, commits, PRs, runbooks, errors, design notes, and thesis or paper LaTeX invariants. Not for general, academic-prose, or Australian legal writing; use natural-writing or legal-writing.
    0
    installs