By infiquetra
Two-phase plan execution with automatic multi-reviewer consensus. Phase A runs during plan mode to embed a Team Structure and calls ExitPlanMode itself — the plan is a single atomic artifact (implementation + team roster + review protocol). Phase B fires TeamCreate immediately as the only permitted first action after approval, then runs plan approval gates, parallel execution, and max-3-iteration consensus loop with 9/10 threshold.
npx claudepluginhub infiquetra/infiquetra-claude-plugins --plugin team-executionOptional reviewer for team-execution. Reviews specifications, issue templates, SKILL.md files, CLAUDE.md sections, and task descriptions for AI-consumability: context completeness, unambiguous acceptance criteria, example coverage, constraint explicitness, and machine-parseable structure. Triggered when plan contains: issue template, GitHub issue, task description, acceptance criteria, AI prompt, SKILL.md, CLAUDE.md, spec. NOT for: dumbing down content; general documentation quality (clarity-reviewer). Focus: making specs structured and explicit for AI consumption.
Optional reviewer for team-execution. Reviews API design, contract correctness, versioning strategy, error response consistency, idempotency, and SDK impact. Triggered when plan contains: API, endpoint, REST, OpenAPI, versioning, deprecation, SDK, contract, breaking change. NOT for: implementation security (security-reviewer's job); infrastructure concerns.
Base reviewer for team-execution. Reviews implementations for design pattern consistency, separation of concerns, dependency direction, convention adherence, and architecture documentation coverage. Always spawned — present for every plan execution regardless of plan type. Context loading strategy: searches for architecture decision records or architecture docs in the project (docs/adrs/, architecture-decisions/, docs/architecture/) — loads only relevant ones if found; falls back to codebase pattern analysis if not. NOT for: code quality specifics (code-quality-reviewer); security-specific concerns (security-reviewer's job); test coverage (testing-reviewer).
Optional reviewer for team-execution. Reviews documentation and specifications for structure/navigation, precision of language, completeness, understandability (right audience level), and actionability. Triggered when plan contains: docs, README, specification, guide, runbook, architecture doc, documentation. Primarily used for docs/specs plans and mixed plans with doc content. NOT for: copy editing or grammar (focuses on meaning and structure); code quality.
Optional reviewer for team-execution. Reviews code for duplication, complexity, pattern consistency, naming/abstraction quality, and error handling patterns. Triggered when plan contains: refactor, lint, patterns, DRY, SOLID, complexity, code smell, technical debt, abstraction. NOT for: security concerns (security-reviewer); test coverage (testing-reviewer); style/formatting (linter handles that).
Base reviewer for team-execution. Challenges assumptions, identifies edge cases, analyzes failure modes, assesses scope creep risk, and evaluates whether alternatives were properly considered. Always spawned — present for every plan execution regardless of plan type. NOT for: blocking on theoretical concerns; redesigning the solution; doing the security reviewer's job (auth/secrets); doing the architecture reviewer's job (patterns/conventions).
Optional reviewer for team-execution. Reviews CDK/CloudFormation infrastructure code, IAM policies, AWS resource configurations, cost implications, resilience patterns, and observability setup. Triggered when plan contains: CDK, CloudFormation, Lambda, DynamoDB, S3, IAM, KMS, multi-region, infrastructure, AWS. NOT for: application-level security (security-reviewer's job); API design concerns.
Optional reviewer for team-execution. Reviews implementations for privacy by design: data minimization, consent and purpose limitation, PII handling and classification, retention and deletion, and cross-border/compliance considerations. Triggered when plan contains: PII, GDPR, data classification, consent, retention, anonymize, personal data, privacy. NOT for: general security concerns (security-reviewer); legal determinations (flags for legal review).
Base reviewer for team-execution. Reviews implementations through the lens of OWASP Top 10, secrets management, authentication/authorization flows, PII handling, and dependency/supply chain security. Always spawned — present for every plan execution regardless of plan type. NOT for: code quality concerns; architecture patterns; test coverage.
Optional reviewer for team-execution. Reviews test coverage adequacy, test quality, edge case testing, mock/fixture appropriateness, and test maintainability. Triggered when plan contains: pytest, test, coverage, integration test, mock, fixture, unit test, e2e, test suite. NOT for: code quality concerns (code-quality-reviewer); infrastructure testing.
Claude Code plugins for Infiquetra development workflows.
| Plugin | Description | Category |
|---|---|---|
| todoist-manager | Full-featured Todoist integration for task and project management | Productivity |
| pagerduty | PagerDuty incident management, on-call orchestration, and service CRUD | Operations |
| slack | Slack messaging and channel management | Communication |
| splunk | Splunk log search and operational analysis | Operations |
| identity-toolkit | Digital identity architecture (NIST 800-63, W3C VCs, custodial wallets) | Security |
| test-suite | Parallel Python quality checks: pytest, ruff, mypy, bandit | Development |
| docs-generator | Automated README, API spec, and architecture documentation generation | Development |
| python-toolkit | Python patterns for serverless apps: Lambda Powertools, DynamoDB, error handling | Development |
| sdk-lifecycle | SDK scaffolding, documentation, security review, and registry publishing | Development |
git clone git@github.com:infiquetra/infiquetra-claude-plugins.git ~/.claude/plugins/infiquetra
Add to ~/.claude/settings.json:
{
"extraKnownMarketplaces": [
{
"name": "infiquetra-plugins",
"url": "https://raw.githubusercontent.com/infiquetra/infiquetra-claude-plugins/main/.claude-plugin/marketplace.json"
}
]
}
ln -s /path/to/infiquetra-claude-plugins/plugins ~/.claude/plugins/infiquetra
# Manage tasks via CLI
python3 plugins/todoist-manager/skills/todoist-manage/scripts/todoist_client.py tasks list
python3 plugins/todoist-manager/skills/todoist-manage/scripts/todoist_client.py tasks add "Review PR" --project "Work"
Set environment variables first:
export PAGERDUTY_API_KEY="your-api-key"
export PAGERDUTY_DEFAULT_TEAM_ID="YOUR_TEAM_ID"
export PAGERDUTY_DEFAULT_ESCALATION_POLICY_ID="YOUR_POLICY_ID"
# List active incidents
python3 plugins/pagerduty/skills/pagerduty-incidents/scripts/pagerduty_client.py incidents list --status triggered
# Acknowledge an incident
python3 plugins/pagerduty/skills/pagerduty-incidents/scripts/pagerduty_client.py incidents acknowledge --id PXXXXX
# Run all quality checks in parallel
python3 plugins/test-suite/skills/run-quality-checks/scripts/test_runner.py \
--coverage 80 \
--source-dir src \
--test-dir tests
# Generate all documentation
python3 plugins/docs-generator/skills/generate-docs/scripts/docs_generator.py generate --all --service my-service
export SPLUNK_HOST="your-splunk-host"
export SPLUNK_TOKEN="your-token"
python3 plugins/splunk/skills/splunk-search/scripts/splunk_client.py search \
"index=main level=ERROR earliest=-1h"
export SLACK_BOT_TOKEN="xoxb-your-token"
python3 plugins/slack/skills/slack-messaging/scripts/slack_client.py message \
--channel "#general" \
--text "Deployment complete"
git clone git@github.com:infiquetra/infiquetra-claude-plugins.git
cd infiquetra-claude-plugins
# Install dependencies
uv pip install -e ".[dev]"
# Run tests
pytest
# Run linting
ruff check .
# Run type checking
mypy plugins/
# Use the scaffolding tool
./tools/create-plugin.sh my-new-plugin
See docs/PLUGIN_SPEC.md for full plugin development guidelines.
Plugins follow the Claude Code native plugin format:
plugin-name/
├── .claude-plugin/
│ └── plugin.json # Plugin manifest
├── agents/ # Agent definitions (optional)
│ └── agent-name.md
├── skills/ # Skills (optional)
│ └── skill-name/
│ ├── SKILL.md # Skill definition
│ ├── references/ # Reference documents
│ └── scripts/ # Implementation scripts
├── commands/ # Commands (optional)
│ └── command.md
├── README.md
└── CHANGELOG.md
MIT
Comprehensive UI/UX design plugin for mobile (iOS, Android, React Native) and web applications with design systems, accessibility, and modern patterns
Uses power tools
Uses Bash, Write, or Edit tools
Qiushi Skill: methodology skills for AI agents guided by seeking truth from facts, with Claude Code, Cursor, OpenClaw, Codex, OpenCode, and Hermes guidance.
Standalone image generation plugin using Nano Banana MCP server. Generates and edits images, icons, diagrams, patterns, and visual assets via Gemini image models. No Gemini CLI dependency required.
Battle-tested Claude Code plugin for engineering teams — 38 agents, 156 skills, 72 legacy command shims, production-ready hooks, and selective install workflows evolved through continuous real-world use
Comprehensive skill pack with 66 specialized skills for full-stack developers: 12 language experts (Python, TypeScript, Go, Rust, C++, Swift, Kotlin, C#, PHP, Java, SQL, JavaScript), 10 backend frameworks, 6 frontend/mobile, plus infrastructure, DevOps, security, and testing. Features progressive disclosure architecture for 50% faster loading.