← all publishers

adelrioj

@adelrioj source repo

13 published skills

  1. Ship It · adelrioj
    Use when a thumbs-upped design spec is ready and you want the whole spec-to-PR pipeline to run autonomously — hardens the spec, writes the plan, executes it via dex, opens a PR, runs PR review, and closes with an architect completeness review — in one invocation. Triggers on: ship it, ship-it, run the pipeline, spec to PR, autonomous feature pipeline, conductor.
    0 installs
  2. To Linear · adelrioj bundle
    Create a properly-templated Linear issue or epic-project (bug, story, epic) from the current conversation, on whichever team this repo files to. Use this WHENEVER the user wants to write, file, log, or create a ticket/story/bug/epic. Triggers on: write a bug ticket, file this as a bug, log a defect, create a user story, file tech debt, turn this into an epic, file a ticket, to linear, to-linear.
    0 installs
  3. Blind Spot · adelrioj
    Use BEFORE starting work on a task to surface the unknown-unknowns you're about to walk into but can't see. Dispatches a fresh-context Claude subagent that hunts what you don't know you don't know about the codebase, the domain, and the decisions ahead, calibrated to your stated experience, then reports ranked, evidence-backed findings and fixes nothing. Triggers on: blind spot pass, blindspot, unknown unknowns, what don't I know, what am I missing, help me prompt better, I know nothing about, teach me my unknowns, before I start, de-risk this task, surface my blind spots.
    0 installs
  4. Plan To Dex · adelrioj bundle
    Use when running an already-hardened Superpowers implementation plan through the dex orchestrator (codex backend). Triggers on: convert plan to dex, plan to dex, dex from plan, run plan with dex, plan-to-dex.
    0 installs
  5. Claude Md Slim · adelrioj
    Use when CLAUDE.md has grown bloated and is taxing every session's context — the inverse of claude-md-improver. Triages each block into session-invariant rules (stay always-on) vs feature/subsystem detail (page out to docs/ behind a plain-path pointer), moving — never deleting — the detail so nothing is lost and the always-on token bill drops. Triggers on: slim claude.md, minimal claude.md, claude.md is bloated, shrink claude.md, split claude.md, make claude.md minimal, page out claude.md, claude.md too long, reduce project memory, point claude.md to docs, trim claude md.
    0 installs
  6. Review Codebase · adelrioj bundle
    Use to run a whole-system adversarial audit of the current repo across three lenses at once — codebase (defects, incoherences, affordance gaps), docs (drift, structure, coverage), and process (end-to-end workflow dead ends). Dispatches three fresh Claude subagents in parallel, each writing a ranked findings report to docs/audits/, then offers an optional fix pass on CRITICAL findings. Triggers on: review codebase, audit codebase, audit this repo, adversarial audit, codebase audit, docs audit, process audit, fable audit, three reviews, full audit, whole-system review, find everything wrong.
    0 installs
  7. Spec To Symphony · adelrioj
    Use when a groomed Linear ticket already carries its design spec and the build must be handed to a Symphony autonomous pipeline — puts the spec on the remote under the filename that deployment actually reads, then arms the existing ticket so the poller dispatches it. The ticket must already exist; this skill never creates one. Triggers on: hand off to symphony, hand the build to symphony, arm the pipeline, arm the ticket, spec to symphony, spec-to-symphony.
    0 installs
  8. Spec Review Codex · adelrioj bundle
    Use when a brainstorming design spec has been written and needs adversarial review before implementation planning, using OpenAI Codex as the independent reviewer. Requires the codex CLI. Triggers on: spec review codex, codex spec review, review spec with codex, codex review, review spec, spec review.
    0 installs
  9. Spec Review Local · adelrioj bundle
    Use when a brainstorming design spec has been written and needs adversarial review before implementation planning, using a local model served by LMStudio (via the pi CLI) as the independent reviewer. Works offline — no hosted API needed. Triggers on: spec review local, local spec review, review spec locally, lmstudio review, review spec, spec review.
    0 installs
  10. Linear Spec Ticket · adelrioj
    Use when a Linear ticket has been groomed and now needs a design spec written onto it so work can start — drafts the spec from the ticket and the codebase and uploads it to the ticket as a file attachment. Also refreshes that attachment after /spec-review-codex hardens the spec. Never changes the ticket state. Triggers on: add a spec to this ticket, write the spec for NBS-123, deja el ticket listo para trabajar, añade spec al ticket, adjunta la spec al ticket, prepare this ticket for work, spec this ticket, refresh the spec attachment, re-upload the hardened spec, linear-spec-ticket.
    0 installs
  11. Architect Review Pr · adelrioj
    Use after a feature is built — e.g. the final step of a ship-it run, right after review-pr — to check it is actually complete and wired, not just line-correct. Dispatches a fresh-context Claude subagent that traces the whole repo to hunt completeness and integration gaps in the branch's changes, reports ranked, evidence-backed findings, then fixes the CRITICAL ones and verifies with a fresh re-review (capped at 3 passes; pass report-only to skip fixing). Triggers on: architect review, architecture review, completeness review, wiring review, is this wired, did we finish this, find the gaps, incomplete feature, created but not wired, dead code check, deep pass on what we built.
    0 installs
  12. Linear Groom Ticket · adelrioj bundle
    Use when a Linear ticket needs to be made ready to work on, or judged not worth working on. Analyses one ticket across four dimensions — whether its claims hold in the code, whether it is complete against the team template, whether it duplicates another ticket, and whether it is implementable — then proposes a corrected description and applies it to Linear only after you approve. Triggers on: groom this ticket, prepare NBS-123, is this ticket ready, revisa este ticket, ¿este ticket está listo?, deja el ticket listo para trabajar, candidato a borrar, dedupe this ticket.
    0 installs
  13. Linear Triage Ticket · adelrioj
    Use when a Linear ticket needs a priority, a complexity rating and an effort estimate backed by evidence from the code — reads the repo the ticket is about, runs two read-only codex analysts, and after your explicit approval writes the priority, the estimate (when provable) and one living rationale comment to Linear. Triggers on: triage this ticket, size NBS-123, prioritize this ticket, estimate this ticket, how big is this ticket, how urgent is this, triaje este ticket, prioriza el ticket, estima el esfuerzo, linear-triage-ticket.
    0 installs