superpowers
claudecodexCore skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques
15 skills · hooks
A full software team for Claude Code (PM, BA, Team Lead, Developers, Reviewer, QA, DevOps, Reporter) coordinated through a GitHub Projects board.
Plugin squad from marketplace agile-squad in congdang-agilityio/agile-squad. Commands read from the repo's manifest — 14 days 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.
baTurn a product idea or requirement sources (files, links, a chat description) into signed-off requirements and small user stories in the Backlog: analyze, ask clarifying questions until the BA declares them clear, get requirement sign-off (GATE 1), draft PRD and stories, get story approval (GATE 2),
deployDevOps procedure, with the Railway CLI under the stakeholder's own login (no tokens): release a milestone (deploy gate, release notes, deploy and smoke-test staging, request GATE 3 on GitHub; after approval deploy production, publish, mark items Released); change the platform for an infra task (data
devDeveloper procedure: implement exactly one task issue with TDD in its own git worktree, keep the change within the task's size, and open a small PR; or rework a PR after review/QA feedback; or rebase a PR labeled needs-rebase. Use when a task in Todo is dispatched to a developer slot, when review or
doctorDiagnose why squad cannot run in this repository: tools, gh login and token scopes, .squad/config.yml and its board ids, board fields and Status columns, items missing from GitHub's item listing, labels, conflicting project workflows, merge settings, branch protection, release-gate workflow, the pro
fixQuick lane for one small change: a bug against existing behavior, a text or style tweak, a small refactor or a dependency bump. Skips the BA, GATE 1/2 and story planning: the Team Lead turns the request into one XS/S task, then a developer, the reviewer, the Team Lead merge and a light QA check run
planTeam Lead procedure: split approved stories (Backlog), needs-split tasks and QA bugs into small XS/S technical tasks with Files (expected), dependencies and Definition of Done, group them into parallel waves on the board and post the dispatch plan; recompute waves when developer slots are idle (rewa
qaQA procedure: verify a merged task, bug or story in the QA column against every acceptance criterion and DoD item by running the full test suites, e2e and the real app on the latest main; pass it to Done with a test report, or file a bug sub-issue from the bug template and keep the task out of Done.
reportProgress report for the stakeholder: collect delivery metrics from the board and GitHub with metrics.sh (period or milestone), have the reporter draft a report with a 5-line plain-language summary and a metrics table where every number comes from the script, then publish it as a type:report issue an
reviewCode review procedure for one PR in In Review: check size and scope, verify every acceptance criterion and DoD item has a test, review correctness and security against the review checklist, and post the verdict as a review comment (PASS adds review:passed for the Team Lead to merge; CHANGES sends th
runPM orchestrator for squad: repeatedly read the board with next.sh and dispatch the right subagent for the highest-priority action (QA, Team Lead merge, review, rebase, planning, parallel developers by wave, deploy), relay gates and questions to the stakeholder, and stop at a requirements gate, when
setupInitialize squad in the current repository (or `quick`: board, labels and commands only, no deploys, in about two minutes): create or reuse the GitHub Projects board with the squad Status columns and Priority/Size/Wave/Agent/Attempts fields, create the labels, write .squad/config.yml, and configure
ba-analystSquad Business Analyst. Use when the PM needs requirement sources analyzed, clarifying questions written or re-evaluated, or a PRD and user stories drafted for a requirement slug under docs/requirements/.
developerSquad Developer. Use to implement exactly one task issue in its own worktree (modes: implement, rework, rebase) with TDD, then open a small PR. One task per invocation.
devopsSquad DevOps. Uses the Railway CLI (through scripts/railway.sh, under the stakeholder's own railway login, no tokens). Use (mode release) when a milestone meets the deploy gate to draft release notes, deploy and smoke-test staging and request GATE 3; (mode finish) after GATE 3 to deploy production,
qa-testerSquad QA Tester. Use to verify merged items in the QA column (or, with story=true, an open story whose tasks are all Done) against every acceptance criterion by running tests, e2e and the real app; pass them to Done or file bug sub-issues.
reporterSquad Reporter. Use to collect board metrics with scripts/metrics.sh for a period or milestone and draft a stakeholder report in .squad/reports/ (the PM publishes it as an issue).
reviewerSquad Code Reviewer. Use to review exactly one PR in In Review against its acceptance criteria and the review checklist, then post the verdict as a review comment (PASS adds review:passed; otherwise review:changes). Never merges.
team-leadSquad Team Lead. Use (mode plan) when approved stories in Backlog, tasks labeled needs-split, or unplanned QA bugs must be split into small tasks with dependencies and parallel waves; (mode rewave) to recompute waves of unstarted tasks when developer slots are idle; (mode milestone) to put stories t
"${CLAUDE_PLUGIN_ROOT}"/scripts/guard.sh
Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques
15 skills · hooks
Backend API design, GraphQL architecture, workflow orchestration with Temporal, and test-driven backend development
9 skills · 1 command · 8 agents
AI-supervised issue tracker for coding workflows
1 skill · 1 agent · hooks
MiniMax AI skills library for frontend, fullstack, Android, iOS, shader, GIF sticker, document, presentation, spreadsheet, and multimodal media workflows
18 skills
Worktrunk is a CLI for Git worktree management, designed for parallel AI agent workflows. This plugin provides configuration guidance (LLM commit messages, project hooks, worktree paths), automatic activity tracking (🤖/💬 indicators in `wt list` showing active Claude sessions), and a `/wt-diff` pane showing each worktree's changes.
2 skills · hooks
GSD Core is a meta-prompting, context engineering, and spec-driven development system for AI coding agents.
72 skills · 72 commands · 64 agents · hooks
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.