claude

refinery

AI-powered roadmap refinement: ticket analysis, sprint review, design analysis, documentation search, and team communication

0 on GitHubby aldoreav0.1.0MITupdated 6 months ago
/

Plugin refinery from marketplace workbench-dev in weorbitant/workbench-dev. Commands read from the repo's manifest — 1 month ago.

This plugin runs code on your machine — its hooks fire automatically on events like tool use. The exact commands are listed below; read them before installing.

What it installs

Skills (11)

  • adr

    Use when creating, updating, or compacting Architecture Decision Records. Use when user says 'adr', 'create ADR', 'record decision', 'registrar decisión', 'decision record', or needs to document a technical decision.

  • analyze-data-model

    Use when interrogating the codebase to understand an entity, its fields, relationships, and data flows. Use when user says 'analyze data model', 'analizar modelo', 'understand entity', 'check schema', or asks about a specific entity or database field.

  • analyze-design

    Use when extracting data fields, UI states, actions, and flows from a design. Use when user says 'analyze design', 'analizar diseño', 'review design', 'extract from figma', or shares a design URL.

  • analyze-docs

    Use when searching documentation about a concept across platforms. Use when user says 'search docs', 'buscar documentación', 'analyze docs', 'find documentation', or needs to understand existing documentation about a topic.

  • analyze-feasibility

    Use when evaluating whether a technical approach is feasible against the current codebase. Use when user says 'analyze feasibility', 'is this feasible', 'evaluar factibilidad', 'technical analysis', or asks whether an approach will work.

  • board-to-stories

    Use when extracting user stories from a visual board. Use when user says 'extract stories', 'genera user stories', 'procesa scope', 'board to stories', or shares a board URL.

  • clarify-ticket

    Use when analyzing a ticket for ambiguities, missing information, or unclear acceptance criteria. Use when user says 'clarify ticket', 'review ticket', 'analyze ticket', or passes a ticket key.

  • create-bug

    Use when creating a well-structured bug report with root cause analysis. Use when user says 'create bug', 'report bug', 'log bug', 'new bug', or describes a defect.

  • notify-team

    Use when sending communication to the team. Use when user says 'notify team', 'notifica al equipo', 'send message', 'draft a message', 'enviar mensaje', or needs to communicate with the team.

  • sprint-review

    Use when evaluating a sprint before starting it. Use when user says 'sprint review', 'review sprint', 'evaluar sprint', 'sprint planning review', or mentions checking sprint readiness.

  • ticket-analysis

    Use when performing a comprehensive ticket analysis across design, documentation, data model, and technical feasibility. Use when user says 'analyze ticket', 'ticket analysis', 'análisis de ticket', or needs deep understanding before implementation.

Slash commands (11)

  • /refinery:adr

    Create, update, or compact Architecture Decision Records.

  • /refinery:analyze-data-model

    Understand an entity, its fields, relationships, and data flows.

  • /refinery:analyze-design

    Extract data fields, UI states, actions, and flows from a design.

  • /refinery:analyze-docs

    Search documentation about a concept across platforms.

  • /refinery:analyze-feasibility

    Evaluate whether a technical approach is feasible against the current codebase.

  • /refinery:board-to-stories

    Extract user stories from a visual board.

  • /refinery:clarify-ticket

    Analyze a ticket for ambiguities, missing information, or unclear acceptance criteria.

  • /refinery:create-bug

    Create a well-structured bug report with root cause analysis.

  • /refinery:notify-team

    Send communication to the team via Slack, Teams, or Discord.

  • /refinery:sprint-review

    Evaluate a sprint before starting it.

  • /refinery:ticket-analysis

    Comprehensive ticket analysis across design, documentation, data model, and technical feasibility.

Hooks (1)

  • SessionStart

    ${CLAUDE_PLUGIN_ROOT}/hooks/session-start.sh

View source on GitHub

More from weorbitant/workbench-dev

All 3 plugins →

ops-suite

claude

Technology-agnostic infrastructure operations: service status, logs, deployments, database queries, and message queue management

12 skills · 13 commands · hooks

0

Guide for authoring Claude Code skills following Anthropic best practices

1 skill

0

Maintain refinery?

This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.

claude & codex plugins3 plugins