buildwithjpegg

Enforces design review gate after brainstorming — bridges superpowers:brainstorming into the tribunal quality pipeline

Layered configuration resolution for tribunal.yaml

Create comprehensive GitHub issues with TDD plans, acceptance criteria, and agent instructions for autonomous PR lifecycle management

Multi-agent brainstorming debate — agents propose solutions, critique each other, and reach consensus before design review

Delegate implementation and review tasks to external AI CLI tools (Codex, Gemini) with cross-model adversarial review

Address PR review feedback systematically — fetch inline comments, review bodies, handle outside-diff-range comments, resolve threads with proper attribution

Migrate from npm-installed tribunal to the marketplace plugin — removes redundant files with safety checks

Interactive project setup — detects your project, configures tribunal, writes project-local files

Use when starting work on any task, when the user mentions tribunal, or when the user wants to begin tracked development work

Diagnostic status report — shows tribunal installation state, project setup, and potential issues

Use when you have a spec or requirements for a multi-step task, before touching code

Use when you have a written implementation plan to execute in a separate session with review checkpoints

Use when executing implementation plans with independent tasks in the current session

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

One-time setup that wires semantic-release into a repository for automated versioning, changelog generation, and GitHub releases from conventional commits. Use when setting up a new repo that will be publicly released.

Use after creating a PR to monitor CI and automatically fix failures before reporting back. Fires automatically after PR creation. Do not report the PR as ready until CI is green.

Use when creating new skills, editing existing skills, or verifying skills work before deployment

Manages draft status for stacked PRs. Use when creating any PR in a stack (mark non-current PRs as draft), and when a base PR merges (promote the next PR to ready). Prevents reviewers from seeing PRs that depend on unmerged work.

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.

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

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

Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions

Maintains .claude/stack.json tracking stacked PR state across sessions. Read at session start when working on a stacked feature. Update after every PR creation, merge, or rebase.

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

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

Use when implementing any feature or bugfix, before writing implementation code