By mariuswilsch
Team onboarding plugin with clarity workflow commands, worktree skill, and commit guards
npx claudepluginhub mariuswilsch/claude-code-team-marketplace[2026-01-03] [Stage 3] Execute AC verification in separate session from implementation
[2026-01-17] [Stage 3] Define testable success criteria with layer and sanity check identification
[2025-12-13] [Stage 2] Capture Claude Code improvement opportunities as GitHub issues
[2025-12-01] [Stage 2] Resolve implementation ambiguities before execution
[2025-12-17] [Stage 2] Fix Claude Code instruction artifacts from improvement backlog
[2025-12-12] [Stage 2] Post standardized GitHub issue comments
[2025-12-20] [Stage 2] Safe PR merge workflow with verification
[2026-01-02] [Stage 3.0] Alan Kay Disambiguation Specialist onboarding with consolidated Python bootstraps
[2026-01-17] [Stage 3] Verify AI's requirement understanding before implementation
[2026-02-03] [Stage 3] Thinking partner for externalization of thought
Define acceptance criteria using Given-When-Then format (discovery: rubber-duck). MUST load when user says 'acceptance criteria', 'ACs', 'Given-When-Then', 'how do we verify', or 'let's define AC'. Contains the methodology - do not reason about ACs from scratch. Provides DoD dependency analysis, AC scoping, enumeration method, path prioritization, and format best practices.
Extract and read Claude conversation JSONL files with composable filters (discovery: rubber-duck). Evaluate at rubber-duck or at any point in the sesssion when task requires reading conversation history, verifying tool outputs, or auditing session behavior. Use instead of raw Read/grep on ~/.claude/projects/*.jsonl files.
Create GitHub Issues for client deliverables in DaveX2001/deliverable-tracking repo (discovery: rubber-duck). Evaluate at requirements-clarity when user mentions tracking, deliverables, commitments, or 'create deliverable'. Extracts What/Why/Done from conversation context, prompts for missing info via AskUserQuestion, applies dynamic client labels.
Create isolated git worktrees for ALL coding tasks with issue linking (discovery: implementation-clarity). Evaluate at implementation-clarity when task modifies code files. YOU MUST use for feature development, bug fixes, refactoring - no exceptions. Coding without worktree = no audit trail, no issue linking, no auto-close.
Git and PR workflows with code review, onboarding, and PR enhancement
Executes bash commands
Hook triggers when Bash tool is used
Share bugs, ideas, or general feedback.
Interactive setup wizard for configuring any repository with Claude Code best practices, based on Boris Cherny's workflow
Commands for team workflows, PR reviews, and collaboration
Development environment setup: git worktrees, terminal optimization
AI-supervised issue tracker for coding workflows. Manage tasks, discover work, and maintain context with simple CLI commands.
Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques