transparent-pegasus/herdrpowers
Skill Claude CodeCodex
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
transparent-pegasus/herdrpowers
Skill Claude CodeCodex
Use when you have a written implementation plan to execute in a separate session with review checkpoints.
transparent-pegasus/herdrpowers
Skill Claude CodeCodex
Use when implementation is complete, all tests pass, and the user needs to decide how to integrate the work - presents the integration candidates (merge locally, push and open a PR, push only, keep) and executes only the chosen one; never merges on its own.
transparent-pegasus/herdrpowers
Skill Claude CodeCodex
Control Herdr, a terminal multiplexer for coding agents. Use only when the user explicitly mentions Herdr or asks to use Herdr to inspect or control panes, tabs, workspaces, commands, or another agent. Do not use merely because a task could benefit from a background terminal, delegation, or parallel work. Requires…
transparent-pegasus/herdrpowers
Skill Claude CodeCodex
Route every task received directly from the user through the pane that received it (the orchestrator) in herdr unless the user explicitly denies orchestration. Does NOT apply to tasks delegated from another pane — execute those yourself, never re-delegate. Routing comes from the repository's .herdrpowers/config.yaml…
transparent-pegasus/herdrpowers
Skill Claude CodeCodex
Use when executing implementation plans with independent tasks by delegating each task to a fresh herdr sibling pane.
transparent-pegasus/herdrpowers
Skill Claude CodeCodex
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation.
transparent-pegasus/herdrpowers
Skill Claude CodeCodex
Use when completing tasks, implementing major features, or before merging to verify work meets requirements.
transparent-pegasus/herdrpowers
Skill Claude CodeCodex
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
transparent-pegasus/herdrpowers
Skill Claude CodeCodex
Use when implementing any feature or bugfix, before writing implementation code.
transparent-pegasus/herdrpowers
Skill Claude CodeCodex
Use when code, config, prompt, schema, or task changes require updating Markdown files directly under docs/, such as architecture, structure, config-sync, theories, adopted-theories, or todo documents.
transparent-pegasus/herdrpowers
Skill Claude CodeCodex
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback.
transparent-pegasus/herdrpowers
Skill Claude CodeCodex
Use when inside herdr (HERDRENV=1), the current pane is acting as the orchestrator for the task, and idle sibling agent panes can take delegated work — operational repo tasks standalone, or any routed task as the delegation transport for the orchestration skill.
transparent-pegasus/herdrpowers
Skill Claude CodeCodex
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always.
transparent-pegasus/herdrpowers
Skill Claude CodeCodex
Use when you have a spec or requirements for a multi-step task, before touching code.
transparent-pegasus/herdrpowers
Skill Claude CodeCodex
Use when creating new skills, editing existing skills, or verifying skills work before deployment.