AI Agent Workflow Collection

Conducts quality reviews of non-code artefacts. Use when reviewing or critiquing Skills, agents, workflows, documentation, or written materials, assessing quality against standards, or providing structured feedback.

Writes correct, version-aware Telegram bot code. Use when writing, extending, or debugging a Telegram bot in python-telegram-bot, aiogram, grammY, or Telegraf. Not for Telegram client API (TDLib), languages other than Python and Node.js, or non-Telegram platforms.

Collects research sources with quality evaluation. Use when gathering or finding sources, building a source library, searching for academic papers, or performing RADAR assessment.

Guides written communication — emails, reports, presentations, documents, website copy, newsletters, books. Use when writing or improving writing, adapting to an audience, or shaping document structure. Not for oral delivery or tool-specific formatting (slides, PDFs).

Conducts research. Use when asked to research, investigate, explore, look into a topic, compare options, learn about an unfamiliar domain, or understand current state.

Transforms unstructured requests into clear, actionable briefs. Use when writing a brief, preparing a specification, extracting requirements, or clarifying what a task needs.

Raises an artefact's signal-to-noise ratio by removing text that earns nothing for its reader — filler, repetition, over-explanation, ornamental phrasing — and relocating conditional detail to references. Use to slim a skill, agent, or document, cut bloat, tighten prose, or shrink a file that has grown too long. Tuned for SKILL.md files.

Delegates a task to a local LLM running as a Pi coding-agent session in a herdr pane - the subagent is visible in herdr, can be steered mid-session, and costs no cloud tokens. Use when delegating work to a local model, spawning a Pi subagent, offloading a task to omlx (qwen, gemma), or running agent work offline. Not for Claude Code's own Agent tool or subagents inside Pi.

Creates a design system for software with a UI. Use when a project has a user interface and architecture is confirmed — whether creating from scratch or extracting patterns from existing code.

Designs workflow structure. Use when planning a workflow, choosing which phases to include, or selecting a workflow pattern for a task.

Re-explains concepts at a "knows the basics" level — strips jargon, uses analogies, and assumes broad general knowledge without domain expertise. Use when the user invokes /eli40 to request a simpler explanation of the previous message, or /eli40 to get an accessible explanation of a specific topic. Like ELI5 but calibrated for an adult generalist.

Enriches implementation roadmap chunks with acceptance criteria, pattern references, and contextual notes. Use after decomposing-work has produced the structural roadmap and before planning-software creates the orchestration plan. Does not modify chunk structure or dependencies.

Evaluates software quality from an end user's perspective. Use when emulating a real user to assess a running web app, CLI tool, or API.

Retrieves up-to-date documentation, API references, and code examples for any developer technology.

Generates and explores ideas. Use when capturing fleeting thoughts, brainstorming, exploring a problem space before committing to a direction, or reviewing stored ideas to decide what to pursue.

Extracts product requirements and produces a PRD. Use when a user wants to build software and needs to define what to build before architecture or implementation, when scoping an MVP, or when translating a vague idea into a buildable specification.

Runs software development projects from idea to completion. Use when starting a software project, adding a feature, fixing a bug, or resuming an in-progress build.

Principles for multi-agent workflow execution. Use when coordinating agents, accepting or rejecting agent work, executing producer-critic cycles, or running any multi-phase orchestrated task.

Extracts genuine value from a subject and frames it so the right audience recognises it. Use when producing LinkedIn posts, pitch narratives, cover letters, proposals, case studies, or positioning statements. Not for general writing guidance, negotiation, or copywriting templates.

Transforms an approved enriched roadmap into an orchestration plan. Use when creating an orchestration plan, producing a build plan, or resuming a project from a saved plan. Not for roadmap creation/enrichment or workflow tier selection.

Creates the standard project file structure for a software project. Use when starting a new software project, initialising project files, or setting up a project workspace before architecture and decomposition begin.

Explores solution options when the problem is defined but the approach is unclear. Use when evaluating approaches, comparing alternatives, or choosing between options.

Agent behavioural frame for operating within rageatc. Preloaded by agents — not for orchestrator use; orchestrator context comes from rules.

Clarifies user intent before formalising requirements. Use when requests are vague, incomplete, or solution-focused, or when preparing to write a brief.